UNIX for Beginners Questions & Answers

The SSH protocol tools are designed not to accept plaintext passwords because of the insecurity of storing a short plaintext password (in a script or reference file etc.)

To automate the procedure, you should generate SSH keys. This will give you a secure connection which you can automate far easier than trying to force in credentials, similar to the 4-line loop shown above.

How far do you get with the ssh-keygen command and sharing the public key?




Robin

hi rbatte1

I have done ssh key gen.
but still it is not allowing me to do it.

below is the command which I am giving

Code:

cat id_rsa.pub | ssh root@10.192.85.95 'cat >> .ssh/authorized_keys;exit;'

it ask for the password but when I give it is not accepting.

Does it accept the password when logging in interactively?

yes it accept intractively

my restrictions is
i can not use sshpass or expect or keygen

is there any alternative to login with root user
even i don't mind giving password in script.

scriptor

Connect with sftp and then put the file instead:-

Code:

$ cd ~/.ssh

$ sftp root@ip.add.re.ss
root@10.4.202.99's password: 
sftp> mkdir .ssh
sftp> cd .ssh
sftp> put id_rsa.pub scriptor.pub
sftp> quit

$ ssh root@ip.add.re.ss
root@ip.add.re.ss's password: 
# cd .ssh
# cat scriptor.pub >> authorized_keys
# chmod 600 authorized_keys
# chmod 700 .
# exit

$ ssh root@ip.add.re.ss  "date ; hostname ; uname -a ; echo 'Hello scriptor' "

If the directory creation fails, that's okay if it has already have been created. The appending of your public key to the authorized_keys file makes sure you do not destroy any existing keys in place.

The permissions settings need to be tight or ssh will refuse to use them.



I hope that this helps,
Robin

hi

I have already done it but not working. although the same procedure is working for other node.


I am ok in writing the password in the script.

is there any way through which I can write a script ?

By design, ssh is written to prevent forcing in the password from a script. What messages do you get to screen or to the system logs on the target server? You might need to look in /etc/syslog.conf or /etc/rsyslog.conf to see where the logs are written.

If we can work out where it is failing, we should be able to get it fixed in the correct way rather than a brute-force way in a script.



Robin