我需要一个小型开发团队多少个github ssh密钥？ [英] How many github ssh keys do I need for a small dev team?

问题描述

当涉及到使用由GitHub托管的远程存储库时，我对SSH密钥的概念感到困惑。我按照 http://help.github.com/win-set中的说明生成密钥-up-git / ，但现在我有多个开发人员推入回购协议，我不清楚我们是否都共享一个SSH密钥，或者如果我们都需要生成单个密钥，机器和使用它？

有人可以为我澄清这一点吗？

解决方案

SSH密钥用于用户进行身份验证并标识为 GitHub 。

通常，对于用户用来访问GitHub的每个不同设备，他会生成一个不同的ssh-key并将其注册/链接到他的GitHub帐户。

控制项目时，您可以根据用户而不是 SSH密钥控制访问权限和权限。

<因此，当你（作为用户）设置你的git环境时，你只能创建一个ssh-key为您希望授予您的GitHub帐户的每台机器。

---

更新：

，但如果您将 SSH密钥引用替换为 Github的个人访问令牌

I'm confused by the concept of SSH keys when it comes to using a remote repository hosted by GitHub. I generated the keys as instructed in http://help.github.com/win-set-up-git/ , but now that I have multiple devs pushing into the repo, I'm not clear if we're all to share one single SSH key or if we all need to generate an individual key per-machine and use that?

Could someone kindly clarify that for me?

解决方案

An SSH key is used for the user to be authenticated and identified into GitHub.

It is common that, for every different device a user uses to access GitHub, he generates a different ssh-key and register/link it to his GitHub's account.

When you control a project, you control access and permissions based on users, and not SSH keys.

So, when you (as a user) setup your git environment you can create only one ssh-key for each machine you would like to give permission to your GitHub's account.

---

Update:

Github now recommends using HTTPS instead of SSH keys but everything in this answer remains valid if you replace all SSH key references above by Github's Personal Access Tokens

这篇关于我需要一个小型开发团队多少个github ssh密钥？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！