This web mail archive is frozen.
This page is part of a frozen web archive of this mailing list.
You can still navigate around this archive, but know that no new mails
have been added to it since July of 2016.
Click here to be taken to the new web archives of this list; it includes all the mails that are in this frozen archive plus all new mails that have been sent to the list since it was migrated to the new archives.
> 1. Run the following command on the client
> * -> ssh-keygen -t dsa
> 2. File id_dsa and id_dsa.pub will be created inside $HOME/.ssh
> 3. Copy id_dsa.pub to the server's .ssh directory
> * -> scp $HOME/.ssh/id_dsa.pub user_at_server:/home/user/.ssh
> 4. Change to /root/.ssh and create file authorized_keys containing
> id_dsa content
> * -> cd /home/user/.ssh
> * -> cat id_dsa >> authorized_keys
> 5. You can try ssh to the server from the client and no password
> will be needed
> * -> ssh user_at_server
That prescription is a little messed up. You need to create id_dsa and
id_dsa.pub on the client, as above.
But it is the client's id_dsa.pub that needs to go
into /home/user/.ssh/authorized_keys on the server, which seems to be
not what the above recipe does.
If that doesn't help, try adding -v or even -v -v to the ssh command to
see what the connection is trying to do w.r.t. your keys.