still problems to use SSH Authentication
Hello everybody, tying still to conf. my remot to log in without any passwd using the SSH Key Authentication. I generate a key via ssh-keygen. copied the "identity.pub" file into the "remote:/$HOME/.ssh" --> appended the file to the "authorized_keys" file. than I restart the sshd on both machines --> try to log me in to the remote-machine via ssh and the result was that I had to enter the remote passwd again. Is there anybody who can help me, to solve this problems. thanx for your hints, regards Dom ________________________________ Assistent ISB-TeamTechnik Dominik Metzler Plattenstrasse 14 CH-8032 Zuerich
On Aug 30, Dominik Metzler <doeme@dplanet.ch> wrote:
tying still to conf. my remot to log in without any passwd using the SSH Key Authentication. I generate a key via ssh-keygen. copied the "identity.pub" file into the "remote:/$HOME/.ssh" --> appended the file to the "authorized_keys" file. than I restart the sshd on both machines --> try to log me in to the remote-machine via ssh and the result was that I had to enter the remote passwd again. Is there anybody who can help me, to solve this problems. identity.pub sounds like ssh-1. If you use protocol2, you need another key file. Try to do ssh -1 user@remotehost ^use protocol version 1
Markus -- __________________ /"\ Markus Gaugusch \ / ASCII Ribbon Campaign markus@gaugusch.at X Against HTML Mail / \
* Dominik Metzler wrote on Fri, Aug 30, 2002 at 11:20 +0200:
Hello everybody, tying still to conf. my remot to log in without any passwd using the SSH Key Authentication. I generate a key via ssh-keygen. copied the "identity.pub" file
I would suggest to use protocol 2 since it's advanced.
into the "remote:/$HOME/.ssh" --> appended the file to the "authorized_keys" file. than I restart the sshd on both machines
Well, usually there is no need to restart sshd. And as already told, no need to have it run on the client.
--> try to log me in to the remote-machine via ssh and the result was that I had to enter the remote passwd again.
Please try the "-v" option. This generates a lot of debugging output which should help you. ssh-keygen -t dsa and stuff was already described in another mail. Also don't forget to check /var/log/messages (specially on server side). SSH checks the permissions of .ssh and much more. SSH refused functionality if it seems to be an broken setup - but in such cases, this is logged of course. oki, Steffen -- Dieses Schreiben wurde maschinell erstellt, es trägt daher weder Unterschrift noch Siegel.
participants (3)
-
Dominik Metzler -
Markus Gaugusch -
Steffen Dettmer