20061122

Permission denied (publickey).

00:53:52 ssh myuser@my.domain.net
Permission denied (publickey).


If this happen, set value for ChallengeResponseAuthentication to yes.

ChallengeResponseAuthentication yes

25 comments:

  1. Thanks just was I needed !!!!!

    never can tell who's reading, but I appreciae this input!

    ReplyDelete
  2. Anonymous3:00 PM

    I have to second that, this message started appearing after upgrading OpenSSH. I didn't know what to do, but this worked!

    ReplyDelete
  3. Anonymous7:29 AM

    Saved my ass too!

    ReplyDelete
  4. Anonymous12:52 PM

    This is suposed to be the default but for some reason it isn't working as the default.

    ReplyDelete
  5. Anonymous6:40 PM

    didnt work here :( Im suppose to edit sudo nano /etc/ssh/sshd_config wright ?

    ReplyDelete
  6. man, this worked like a charm... but why?

    ReplyDelete
  7. worked like magic.. thanks man.

    ReplyDelete
  8. While this allowed me to connect, it did so only after I had to enter a password. I'm trying to use key based authentication. Any suggestions?

    ReplyDelete
  9. Michael Bailey3:48 PM

    Almost 2 years after you posted this. I just wanted to let you know that it saved me too. Thanks!

    ReplyDelete
  10. Don't forget you'll have to restart your ssh daemon as well!

    > service sshd restart
    for RedHat, Fedora Core

    ReplyDelete
  11. Thanks a lot guys for the comments and additional steps :-)

    ReplyDelete
  12. Anonymous7:58 AM

    Exactly what i needed!! Works perfect

    ReplyDelete
  13. Anonymous3:18 AM

    Didn't help me at all

    ReplyDelete
  14. Anonymous3:09 PM

    Thank you very much for this piece of advice, save my ass too :)

    ReplyDelete
  15. Anonymous1:59 PM

    Dude you seriously rock the house...thank you so much

    ReplyDelete
  16. This can also be if your sshd_config file has the 'AllowUsers' variable set to specific users, if so you have to comment it out OR better just add the user you want to be able to ssh to the machine.

    ReplyDelete
  17. You saved me hours or useless attempts.
    Thanks for the easy fix.

    ReplyDelete
  18. Anonymous3:32 AM

    No, leave ChallengeResponseAuthentication to no.

    "ChallengeResponseAuthentication no" will enhance your server security, by only allowing people with right public key to get into your server.

    ReplyDelete
  19. For sure this won't work if you got that message after you have configured a client-server pair .
    The "ssh" command will let you go from a regular user account (in a client computer ) to another regular user account ( in a server ) . Of course I am talking about sharing the public keys properly.
    But when you'll try to execute the "scp" command from regular account to regular account ....no way!

    ReplyDelete
  20. Perfect! I've been banging my head against this wall for the last hour.

    ReplyDelete
  21. Anonymous5:29 PM

    Man, you should be richer than Bill Gates! Thanks.

    ReplyDelete
  22. Anonymous10:31 AM

    thank's

    ReplyDelete
  23. Anonymous10:42 PM

    You are the MAN

    ReplyDelete
  24. It lets You connect with password but not with RSA key :/

    ReplyDelete
  25. Anonymous11:17 PM

    Thank you sir, don't know what happened, but now all is well.

    ReplyDelete