Re: [tlug] Dealing with a second SSH key

[Christian Horn <chorn@example.com>]

On Fri, Oct 10, 2008 at 10:19:37PM +0900, Charles Muller wrote:
> Christian Horn wrote:
> >
> >Log onto the remote box as root, execute
> >  /usr/sbin/sshd -p 2222 -ddd
> 
> I don't have root privileges on the remote box. Maybe this is part of 
> the problem?

No, just makes debugging a bit harder.

Check those requirements are met on the rsync-box:
- modes of your homedir should be 755 or stricter
- modes of your home/.ssh dir should be 700 or stricter
- your homedir, home/.ssh and all its contents should be owned by 
your user
- modes of home/.ssh/authorized_keys (containing your pubkey) should
be 600 or stricter


> >and from your other box use
> >  ssh -p 2222 -i /home/dir/.ssh/id_dsa_keyfile user@example.com

ssh -vv -i /home/dir/.ssh/id_dsa_keyfile user@example.com
could then be used to get a bit output from your client.


>    chuck@example.com:~$ ssh -p 2222 -i /home/dir/.ssh/id_dsa_keyfile
>    acmuller@example.com
> 
>    Warning: Identity file /home/dir/.ssh/id_dsa_keyfile not accessible:
>    No such file or directory.

Use the complete path and filename to the file your ssh-keygen generated,
the one without .pub in its name.


Christian