Hacker News Reader

Comment by koolba | Hacker News Reader

You can have anything you’d like in your ssh config and it will be treated as a server name for auth and auto completion.

So “work-github” can be a Host entry (with a HostName of github.com) and key A. While “play-github” would use key B.

View on HN

You are basically just repeating what he said, but it doesn't answer my question. After all I'm not ssh-ing to GitHub directly, I'd use git, which will use ssh as a transport, and I don't know if git will use the subdomains I provide the way I think it should (my primary concern being to prevent GitHub from displaying 2 public keys for a single account, so that 3rd party cannot tell that it's most probably the same person).

Of course, I can test it myself, but since somebody already does that I assumed I could just ask.

I tested it myself, like `ssh git@rando.github.com` and that didn't work.

That was my interpretation of the original comment. (reading it again, it seems like it was indeed saying what I typed below)

It seems like the reply was saying instead you can do in your .ssh/config file

   Host work.github.com
   HostName github.com
   Host me.github.com
   HostName github.com

(or just leave out the .github.com in the Host part)

So `ssh git@me.github.com` now works...

And then key the github config off of that? But I didn't try that part. So I could be wrong there.

Yes this is what they mean. I've use this setup in the past when for example I wanted to use different SSH keys for bitbucket, gitlab and github for example.

It works even for same hostname like I did here - https://github.com/hashhar/dotfiles-tmp/blob/master/ssh/.ssh...

Reply on news.ycombinator.com