And what are you supposed to do if someone maliciously puts your ssh public key on a junk github account so you can't put it on your own?
-
-
-
Is there a reason github doesn't just give you privileges equal to union of all accounts matching the ssh key used?
End of conversation
New conversation -
-
-
ugly an inconvenient workaround with a ssh stub script (-i otherkey) and run "GIT_SSH='ssh-otherkey' git"
-
Right. Because GIT_SSH is an executable name, not a shell command, you can't even put -i in it. Need a nasty wrapper script per key.
-
a trick using fake hostname for git repository, translated via .ssh/confighttp://stackoverflow.com/questions/37895592/how-to-use-multiple-ssh-keys-for-multiple-gitlab-accounts-with-the-same-host …
-
Wow, thanks. That looks like a viable fix.
-
I'd thought of the same using /etc/hosts but it's not stable against github changing IPs. A DNS domain full of CNAMES would work tho
End of conversation
New conversation -
-
-
What's wrong with using a different SSH key per account?
-
The ssh client doesn't know which key to present (always same server - http://github.com ) and uses the first accepted.
-
And git doesn't have any good way to tell ssh which key to present for a given repo.
End of conversation
New conversation -
-
-
because github forces all users through the one username "git" and uses unique ssh key as actual actual identity
-
not saying it's a great idea, but IIRC it discovered nasty PRNG/keygen bugs before when users showed up with identical keys :)
End of conversation
New conversation -
-
-
Can work around that to some extent with organizations. They can also be (ab)used as namespaces since it's missing that feature.
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.