In both the boxes, I have sudo access to access some file.
From uni115.net , I need to login to uni116.net through script And while running my main script , it wont ask the password for login to another machine. How can we do this. I used the ssh concept inside the shell script. But i dono how to add the password detail while logging to other server. Pls help on this.
Thanks
Chells.
Last edited by zaxxon; 10-20-2011 at 09:17 AM..
Reason: code tags
Hi all,
I have developed a script to list out the servers that is not able to connect to the remote host.
The problem with this script is it, if the remote server ask for a password it gets struck there. It works only if the server name is invalid
Ex: Lets say ssh -q test@test "exit" <... (5 Replies)
Hi All,
i have problem with ssh
i have three server(linux box) like below
server A
server B
server C
i did ssh(Private key & Public key) for passwordls ..
i did for server A to Server B connection without any issue
now i am able to connect server A to server B without... (6 Replies)
Hi everyone,
I'm trying to write a korne shell script that takes the IP address of a remote server as an argument and logs into that server if RSA key has been setup properly, otherwise exits if RSA key is not set for that server.
I don't want the script to get stuck with Password prompt... (1 Reply)
Hi Team,
Hope you will be able to help me out with this problem.
Our sun solaris 9 system receives Idoc files from another xxx system through RCP. But before RCP they establish an SSH connection. Since today morning they are not able to establish connection and is getting an error as pasted below... (0 Replies)
Hi
I have two machines Mac1 and Mac2 logging in with same user id and same private key.
can anyone let me know how to connect these two machine using ssh .
or SCP files to other machine
:wall: (1 Reply)
Hi
Can any one please help identify the issue in scenario 2:
Connectivity Diagram:
1) Distribution Switch----Int_Switch----LabSwitch(Fa1/0)----Terminal Ser
2) Distribution Swtich----Int_Swtich----LabSwitch(Fa2/0)----3640 Router
---all links are access links
Distribution Switch... (0 Replies)
Hi i have two servers name as ser1 ser2 with sudo user name "test"
I want to ssh to the ser2 without using apassword
am login with normal ssh method likes
ssh test@ser2
i got the id_rsa.pub from ser1 and pasted int authorized_keys in ser2. and while connecting got one RSA key fingerprint .... (3 Replies)
I am trying to setup a password less connection from a Linux server to Window server and will be using a script to scp a file without using password.
Linux Server (source)
servername : testlinux
id : testbatch
Windows Server (Target)
servername : testwin
id : testwinlogin
I copied... (5 Replies)
can any one help me in SFTP connectivity?
I am supposed to add Keys in my server(service Id).
We are using ssh RSA authentication. But I m provided with DSA SSH2 2048 keys. Even after sharing, it didnt work.
Please help. (3 Replies)
Discussion started by: dhilipans1988
3 Replies
LEARN ABOUT SUSE
apt_auth.conf
APT_AUTH.CONF(5) APT APT_AUTH.CONF(5)NAME
apt_auth.conf - Login configuration file for APT sources and proxies
DESCRIPTION
APT configuration files like sources.list(5) or apt.conf(5) need to be accessible for everyone using apt tools on the system to have access
to all package-related information like the available packages in a repository. Login information needed to connect to a proxy or to
download data from a repository on the other hand shouldn't always be accessible by everyone and can hence not be placed in a file with
world-readable file permissions.
The APT auth.conf file /etc/apt/auth.conf can be used to store login information in a netrc-like format with restrictive file permissions.
NETRC-LIKE FORMAT
The format defined here is similar to the format of the ~/.netrc file used by ftp(1) and similar programs interacting with servers. It is a
simple token-based format with the following tokens being recognized; Unknown tokens will be ignored. Tokens may be separated by spaces,
tabs or newlines.
machine hostname[:port][/path]
Entries are looked up by searching for the machine token matching the hostname of the URI apt needs login information for. Extending
the netrc-format a portnumber can be specified. If no port is given the token matches for all ports. Similar the path is optional and
only needed and useful if multiple repositories with different login information reside on the same server. A machine token with a path
matches if the path in the URI starts with the path given in the token. Once a match is made, the subsequent tokens are processed,
stopping when the end of file is reached or another machine token is encountered.
login name
The username to be used.
password string
The password to be used.
EXAMPLE
Supplying login information for a user named apt with the password debian for the sources.list(5) entry
deb http://example.org/debian stretch main
could be done in the entry directly:
deb http://apt:debian@example.org/debian stretch main
Alternatively an entry like the following in the auth.conf file could be used:
machine example.org
login apt
password debian
Or alternatively within a single line:
machine example.org login apt password debian
If you need to be more specific all of these lines will also apply to the example entry:
machine example.org/deb login apt password debian
machine example.org/debian login apt password debian
machine example.org/debian/ login apt password debian
On the other hand neither of the following lines apply:
machine example.org:80 login apt password debian
machine example.org/deb/ login apt password debian
machine example.org/ubuntu login apt password debian
machine example.orga login apt password debian
machine example.net login apt password debian
NOTES
Basic support for this feature is present since version 0.7.25, but was undocumented for years. The documentation was added in version 1.5
changing also the implementation slightly. For maximum backward compatibility you should avoid multiple machine tokens with the same
hostname, but if you need multiple they should all have a path specified in the machine token.
FILES
/etc/apt/auth.conf
Login information for APT sources and proxies in a netrc-like format. Configuration Item: Dir::Etc::netrc.
SEE ALSO apt.conf(5)sources.list(5)BUGS
APT bug page[1]. If you wish to report a bug in APT, please see /usr/share/doc/debian/bug-reporting.txt or the reportbug(1) command.
AUTHOR
APT team
NOTES
1. APT bug page
http://bugs.debian.org/src:apt
APT 1.6.3ubuntu0.1 17 August 2017 APT_AUTH.CONF(5)