4 ms·
Didn't work for me. Here's what I got. I cleaned out .ssh/knownhosts after connecting. +-----------------------------------------------------------------
by acomjean 11y ago
Didn't work for me. Here's what I got.
I cleaned out .ssh/knownhosts after connecting.
+---------------------------------------------------------------------+
| |
| _o/ Hello! |
| |
| |
| Did you know that ssh sends all your public keys to any server |
| it tries to authenticate to? You can see yours echoed below. |
| |
| We tried to use that to find your GitHub username, but we |
| couldn't :( maybe you don't even have GitHub ssh keys, do you? |
| |
| By the way, did you know that GitHub publishes all users' |
| ssh public keys and Ben (benjojo.co.uk) grabbed them all? |
| |
| That's pretty handy at times :) But not this time :( |
| |
| |
| P.S. This whole thingy is Open Source! (And written in Go!) |
| https://github.com/FiloSottile/whosthere |
| |
| -- @FiloSottile (https://twitter.com/FiloSottile) |
| |
+---------------------------------------------------------------------+
Connection to whoami.filippo.io closed.
Arams-MacBook-Pro:~ acomjean$ emacs .ssh/known_hosts
- joeblau 11y agoDidn't work for me either. It seems like it fails more than it succeeds based on the results posted in this thread.
- riffraff 11y agopresumably, those for which it worked are less likely to post? FWIW, it worked for me.
- joeblau 11y agoThat is true! I didn't think about that.
- simoncion 11y agoThat's a very good thing to keep in mind when reading any complaints on the Internet and using them to gauge sentiment about a thing. Folks who are happy with a thing are far less likely to take the time to write up their experience than those who are unhappy.
- igravious 11y agoand it worked for me too, just thought i'd chime in here. nice educational and simple project.
- bmelton 11y agoIt's probably most apt to working when the local username is the same as the username in your SSH keys. If your local username is something like "johndoe", while your server logins (and keys mapping to them) is "jdoe", it isn't likely to align the one to the other. If your local and remote usernames tend to be the same, and they are also the same as your Github keys, then it's probably pretty likely to be accurate.
- taejo 11y agoIt's based exclusively on the public key. My local username and github login are unrelated, and it worked for me.
- FiloSottile 11y agoHi! 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 agoThis 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 agoWhenever 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 agoI'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 agoI had the same result, and was rather surprised. It's probably because I have a DSA key. Aren't these published by github too?
- rietta 11y agoI got the same.
- reidrac 11y agoJust run "ssh-keygen -R whoami.filippo.io".