4 ms·

Hi! A few reasons it might fail: * You don't have your SSH keys on GitHub * You don't have your GitHub keys on that laptop * Your key is not RSA (because I'm

Hi! A few reasons it might fail: * You don't have your SSH keys on GitHub * You don't have your GitHub keys on that laptop * Your key is not RSA (because I'm LAZY) * Your ssh version uses only recent algorithms not supported by Go's x/crypto/ssh * You actually disabled IdentityKeys Nothing to do with usernames or heuristics, by the way. All it does is first enumerate your client keys, then let you in, then check a huge GitHub keys database, then ask the GitHub API for your name. https://github.com/FiloSottile/whosthere#how-it-works https://github.com/FiloSottile/whosthere#how-it-works

rmetzler 11y ago
- The key might be to new for the dataset.
- lelandbatey 11y ago
  This was the case for me. The keys I'm using now I added this past weekend, and I get the "couldn't find you" message.
noobermin 11y ago
Whenever I push, I login. Apparently this laziness saved my ass this time. Of course, this could be used on any service I ssh into regularly and has a scrappable listing of users, so it's good of you to bring this up.
microcolonel 11y ago
I'm using ed25519 with Github, figured it was just laziness. (also deliberately set it up to send that key because it wouldn't normally).
- deleted 11y ago
  [deleted]
hobarrera 11y ago
I had the same result, and was rather surprised. It's probably because I have a DSA key. Aren't these published by github too?
bonzini 11y ago
It also does not work with keys from a smartcard (yubikey NEO). Here is the ssh log: debug1: Next authentication method: publickey debug1: Offering RSA public key: cardno:000603010929 debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Trying private key: /home/pbonzini/.ssh/id_rsa debug1: Trying private key: /home/pbonzini/.ssh/id_dsa debug1: Trying private key: /home/pbonzini/.ssh/id_ecdsa debug1: Trying private key: /home/pbonzini/.ssh/id_ed25519 debug2: we did not send a packet, disable method debug1: No more authentication methods to try.

rmetzler 11y ago

- The key might be to new for the dataset.

lelandbatey 11y ago
This was the case for me. The keys I'm using now I added this past weekend, and I get the "couldn't find you" message.

noobermin 11y ago

Whenever I push, I login. Apparently this laziness saved my ass this time. Of course, this could be used on any service I ssh into regularly and has a scrappable listing of users, so it's good of you to bring this up.

microcolonel 11y ago

I'm using ed25519 with Github, figured it was just laziness. (also deliberately set it up to send that key because it wouldn't normally).

deleted 11y ago
[deleted]

hobarrera 11y ago

I had the same result, and was rather surprised. It's probably because I have a DSA key. Aren't these published by github too?

bonzini 11y ago

It also does not work with keys from a smartcard (yubikey NEO). Here is the ssh log: debug1: Next authentication method: publickey debug1: Offering RSA public key: cardno:000603010929 debug2: we sent a publickey packet, wait for reply debug1: Authentications that can continue: publickey,keyboard-interactive debug1: Trying private key: /home/pbonzini/.ssh/id_rsa debug1: Trying private key: /home/pbonzini/.ssh/id_dsa debug1: Trying private key: /home/pbonzini/.ssh/id_ecdsa debug1: Trying private key: /home/pbonzini/.ssh/id_ed25519 debug2: we did not send a packet, disable method debug1: No more authentication methods to try.