On Sun, Sep 11, 2005 at 01:56:30PM +0200, Alexander Dalloz wrote: > 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 One more permissions problem that can bite you. The home directory that the .ssh directory is in can nor have too permissive permissions. 755 should work but 777 for example will not. Now ssh-keygen -t dsa produces a key for ssh 2 not ssh 1. As I understand it the file to put the key in might be either authorized_keys or authorized_keys2 depending on the version of OpenSSH installed. But putting the key in authorized_keys is certainly something to try. -- ======================================================================= People humiliating a salami! ------------------------------------------- Aaron Konstam Computer Science Trinity University telephone: (210)-999-7484
