3 ms·
Feature request: allow association of the same ssh key with multiple accounts. In essence stop using git username globally and start supporting user names.
by noncoml 7y ago
Feature request: allow association of the same ssh key with multiple accounts.
In essence stop using git username globally and start supporting user names.
- sleepychu 7y agoWhy would you want this though? Your multiple git accounts are not the same identity.
- noncoml 7y agoSSH treats the key as password, you can have the same authorized key associated with multiple accounts. Not sure why you choose to look at the key as identity.
- sleepychu 7y agoSSH treats your key as evidence of your identity. You can choose to give the public half of your key to multiple entities to allow them to verify your possesion of the private half of the key but that does not translate into multiple identities.
- oefrha 7y agoI was once told explicitly by GitHub Support (just as a reminder) that one person having multiple accounts is against their TOS, so there’s that. (This was years ago, not sure if TOS has changed in this aspect.)
- achamayou 7y agoThe same person creating separate accounts for automation is explicitly permitted however: https://help.github.com/en/github/getting-started-with-github/types-of-github-accounts#personal-user-accounts https://help.github.com/en/github/getting-started-with-githu...
- chrisweekly 7y agowat Never heard such a restriction even mentioned, let alone enforced.
- oefrha 7y agoWell you just heard. At least they say “we do not recommend creating more than one account” at the moment. https://help.github.com/en/github/getting-started-with-github/types-of-github-accounts#personal-user-accounts https://help.github.com/en/github/getting-started-with-githu... Enforced — of course not (guess why I was told), but it stands to reason that they probably won’t add a feature to facilitate TOS violation.
- noncoml 7y agoGitHub is not what it used to be when this "restriction" was made. These days, where a lot of companies decide to go with github, it's not uncommon for people to have one personal account and one work account. This becomes messy to manage, as it's not easy(as far as I know) to use the same account on your personal PC to do both personal and work work.
- jakear 7y agoI was told by GitHub Support less than a month ago that in order for Actions to trigger other Actions I'd need to make a new separate account with repo access and have them act using its PAT.
- smitop 7y agoTheir Terms of Service (https://help.github.com/en/github/site-policy/github-terms-of-service https://help.github.com/en/github/site-policy/github-terms-o...) say: One person or legal entity may maintain no more than one free Account (if you choose to control a machine account as well, that's fine, but it can only be used for running a machine).
- antoncohen 7y agoThe main way I've found this to be annoying is GitHub "Deploy Keys"[1]. They treat them similar to users, so you need a unique deploy key per repository. That is pretty annoying when trying to authenticate something like a CI server. The main alternative is "Machine Users"[1], which are actually normal user accounts. That means they have the same policies as regular users, like mandated 2FA for an organization. And to manage them you have to log-in as that user. That makes it a pain for a team to manage a Machine User. GitHub really needs to have Service Accounts that belong to an organization, and can be managed by admins of the organization (without having to log-in as the Service Account). The Service Accounts should be able to have SSH keys and API tokens associated with them. [1] https://developer.github.com/v3/guides/managing-deploy-keys/ https://developer.github.com/v3/guides/managing-deploy-keys/
- shim__ 7y agoWont't work since the user is identified by his public key on the ssh level.