> The oreilly book on the subject is very helpful. But the quick and dirty is > this: > > on the remote machine, make sure the users home directory contains the .ssh > dir > > on the local macine do this: > > user at local $ ssh-keygen -t rsa #you can optionally specify other key types > if you wish > Generating public/private rsa key pair > Enter file in which to save the key (/home/user/.ssh/id_rsa): #default ok > Enter passphrase (empty for no passphrase): #just hit enter > Enter the same passphrase again: #hit enter again > The key fingerprint is: > blah blah blah...... > user at local $ cat /home/user/.ssh/id_rsa.pub | ssh remote-machine 'cat >> > .ssh/authorized_keys' > user at remote-machine's password: #enter the password > user at local $ ssh remote-machine > user at remote-machine $ #No password this time! > > If that dosnt work, check the permissions of the authorized_keys file (should > be 600 or rw-------). This worked perfect for a single connection between my server and IPCop box, but I need to make connections from this same server to a number of other boxes. I have tried to generate keys with different names, but it is not working. Is there a certain protocol to follow to make this work? _______________________________________________ TCLUG Mailing List - Minneapolis/St. Paul, Minnesota http://www.mn-linux.org tclug-list at mn-linux.org https://mailman.real-time.com/mailman/listinfo/tclug-list