I got everything working fine - like in the past - along a more pedestrian cross copying the authorized keys. Then, slogin put the other machines on known_hosts. Next slogin occurs without password. Also (which is mandatory to run parallel a special computational code) issuing on the server itself
slogin servername places itself on known_hosts. Then, issuing ssh servername date gives the date without requesting the password. That is, this is an ssh to the same machine from which it is commanded and it works because the machine knows itself. I am no system expert, just need to have the machine running the codes; I have not much investigated why I was unable to send the keys. Maybe that above is inelegant. I know that other users solved the issue of getting the date that way with keychain. For me it was easier as above. The permissions on the desktop required changes to get the security status you suggested. regards francesco On Wed, Mar 25, 2009 at 5:21 AM, Ashish Zankar <[email protected]> wrote: > In addition to the above steps follow these steps:- > > 1) check the permission for users home directory it should 755 i.e. group > and others should not have write permission on the users home directory. > 2) check the permission on .ssh directory in the users home directory. > it should like this drwx------ 2 tjx864 scs 4096 Jan 28 14:33 > .ssh/ > 3) check the permission of the authorized keys file in .ssh directory of > the users home directory. > it should be like this -rw------- 1 user_id group 793 Jan 28 14:35 > authorized_keys > and also -rw------- 1 user_id group 1675 Jan 28 > 14:34 id_rsa > Please let me know if the above solution has helped you or not. > Thanks & Regards, > Ashish Zankar > Bangalore. > On Thu, Mar 19, 2009 at 2:52 PM, Francesco Pietra <[email protected]> > wrote: >> >> HI: >> >> I have a computing machine and a desktop ssh passwordless >> interconnected through a Zyxel router (which is dhpc on Internet). I >> have now added a second computing machine. I am unable to get all >> three machines passwordless interconnected at the same time. Just only >> two. If I want to have the third computer passwordless connected to >> one of the other two, I have to exchange id_rsa.pub between the two >> again. Mistake or intrinsic feature of ssh? >> >> What I did: >> >> (1)generating the keys with "ssh-keygen -t rsa" >> >> (2) getting "reserved" the machines on the router >> >> (3)scp id_rsa.pub to the "authorized_keys" >> >> It is also mandatory that asking the "date" to the other computer >> (slogin ... date), the date is given without asking the password. That >> is an issue of a computational code that for its internal >> parallelization needs that (I have not investigated why). >> >> thanks >> >> francesco >> _______________________________________________ >> Beowulf mailing list, [email protected] >> To change your subscription (digest mode or unsubscribe) visit >> http://www.beowulf.org/mailman/listinfo/beowulf > > > > -- > Thanks & Regards, > Ashish Zankar > Bangalore > _______________________________________________ Beowulf mailing list, [email protected] To change your subscription (digest mode or unsubscribe) visit http://www.beowulf.org/mailman/listinfo/beowulf
