Permission denied (publickey). about tmate HOT 12 CLOSED

@kauser-cse-buet He wrote that he solved it: 'My client did not have a ssh key.' so we can imagine he used ssh-keygen :)

from tmate.

Yesterday, I have found what was causing the issue. My client did not have a ssh key.

Oups

from tmate.

nevermind the patching. libssh works just fine.

ssh clients work like that:

• the client tries the "none" auth method
• if auth is required, server must reply with the possible other auth methods "pubkey, password, etc"
• the client tries the next possible available auth method. (but not "none").

the problem if I allow no authentication is that I will never have the chance to grab a public key (which will be very useful in the future when html5 comes in the mix), and also I might increase noise due to ssh bruteforcing bots.

from tmate.

@annacruz use ssh -i ~/.ssh/your_key ... and it will ask for a key password. Also if you're using ssh-agent, you can ssh-add ~/.ssh/your_key upfront, enter password and ssh-agent daemon will remember your key decrypted in memory and then ssh will be able to use it w/o prompting for a password

from tmate.

Hum... I don't really understand why this would happen :(

from tmate.

Okay great :)

from tmate.

Having to run ssh-keygen is annoying. It would be better if tmate accepted both pubkey and password auth, accepting any key and any password.

from tmate.

I could make the authentication optional by patching libssh, this might be better

from tmate.

Same problem for me and my friend.

from tmate.

Same problem as well... It is a little annoying that the other party needs to run ssh-keygen...
But doesn't matter...I guess...

from tmate.

Hi, @martinos ,

How you solved the problem. Can you share please?

from tmate.

I'm having this issue with a key with passphrase could someone help me?

from tmate.