Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • Good idea for separate question. I'm looking at my (successful) login's debug output. I see "we did not send a packet, disable method for dsa and we send a publickey packet, wait for reply for rsa. How absolutely certain are you the keys on server and client are correctly paired?? Commented May 27, 2015 at 10:40
  • It indicates that the SSH server cannot access the authorized_keys file... Does your SSH server run under another account than root? Commented May 27, 2015 at 11:40
  • @Otheus I just checked again, the pair matches Commented May 27, 2015 at 12:02
  • @Nasha Yes, login with other users works. For example, login with the same username as the client works fine Commented May 27, 2015 at 12:02
  • 1
    Interesting. I don't see a line such as debug2: key: /home/remi/.ssh/id_rsa (0x7fb7031da7e0). That might have been in the output above the point you posted. Set StrictModes=no on the server and try again. After testing, remove it again. At least it will tell us which direction the problem lies. Commented May 27, 2015 at 13:21