Am So, den 11.09.2005 schrieb Bob Hartung um 5:41: > I am trying to set up ssh on an internal network for training purposes. > > The setup: > Client: FC3 running openssh-3.p1-8.0.1 > username[not real] someone > > > Server: FC4 running openssh-4.1p1-3.1 > username[not real] someone > > On the client I: > 1. ran 'ssh-keygen -t dsa' > 2. copied ~/.ssh/id_dsa.pub to the server > 3. appended id_dsa.pub contents on to server's > /home/someone/.ssh/authorized_keys2 file with 'cat id_dsa.pub > >> /home/someone/.ssh/authorized_keys2' That should be ~/.ssh/authorized_keys. Be sure about the permissions: chmod 700 ~/.ssh - both on server and client side. chmod 600 ~/.ssh/<keyfile> - both on server and client. > Now when I 'ssh [server]' from the client machine I still am prompted > for the password after about 20 second delay. Login then procedes normally. > Bob Hartung Fedora Extras has the tool keychain for easier ssh key / ssh-agent handling. Alexander -- Alexander Dalloz | Enger, Germany | GPG http://pgp.mit.edu 0xB366A773 legal statement: http://www.uni-x.org/legal.html Fedora Core 2 GNU/Linux on Athlon with kernel 2.6.11-1.35_FC2smp Serendipity 13:53:15 up 20 days, 10:36, load average: 0.16, 0.14, 0.09
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
