On 08/16/2011 01:21 PM, David C. Rankin wrote:
On 08/15/2011 03:43 PM, James D. Parra wrote:
Hello,
I generated an ssh key on a Linux server and pushed the public key to the remote server's authorized_keys files with the following command;
ssh-copy-id -i ~/.ssh/linux_server.pub freebsd-server
...however a password is still being requested when logging in to the remote bsd server. Once on the remote server I can see the key for the linux server in the authorized_keys file.
Any suggestions to resolve the password request?
Thank you in advance.
James
James,
I have always done the following and it works fine:
Local Box (client):
(1) create the keys you need with 'ssh-keygen -t dsa'. (just hit return for empty passwords) That will create id_dsa and id_dsa.pub in ~/.ssh by default. Give the id_dsa.pub key a usable name used when you copy it over to the remote box: (i.e. cp id_dsa.pub id_dsa.pub.$HOSTNAME)
(2) rsync your key with the usable name to the remote box:
rsync -uav ~/.ssh/id_dsa.pub.$HOSTNAME) remote.host.tld:~/.ssh
Remote Box:
(3) ssh into the remote box and append the new usable key to ~/.ssh/authorized_keys i.e.:
cat ~/.ssh/id_dsa.pub.$HOSTNAME) >> ~/.ssh/authorized_keys
** you could just do this step from the Local Box with:
ssh remote.host 'cat ~/.ssh/id_dsa.pub.$HOSTNAME) >> ~/.ssh/authorized_keys'
Don't forget to use the '>>' instead of a '>' much cussing...
You should be able to then log in from Local to Remote without a password.
Dunno why that wouldn't work for freebsd??
It seems I'm often bit by the tendency of ssh-keygen to write the private key with permissions that make it unusable. It often did this in the past and you had to change permissions to 600. Perhaps this has been fixed in later releases. -- Explain again the part about rm -rf / -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org