Menu
I'm wondering, how Github is able to handle so many public keys, which are used for authenticating over ssh.
One user owns aprox 3 certificates and how many users are on Github - millions? Easy multiplication gives us millions of certificates. It isn't in one .ssh/authorized_keys file for user git I guess, right?
They have own ssh server implemented, or exists any mod for OpenSSH solving this kind of problem?
Thanks.
506
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. Show activity on this post. Use a key per developer - each dev should generate their own key.
You can launch projects from a repository on GitHub.com to your server by using a deploy key, which is an SSH key that grants access to a single repository. GitHub attaches the public part of the key directly to your repository instead of a personal account, and the private part of the key remains on your server.
As a security precaution, GitHub automatically deletes SSH keys that haven't been used in a year.
Add your public key to GitHubLogin to github.com and bring up your account settings by clicking the tools icon. Select SSH Keys from the side menu, then click the Add SSH key button. Name your key something whatever you like, and paste the contents of your clipboard into the Key text box. Finally, hit Add key to save.
They have patched sshd to lookup key in the MySQL database:
https://github.com/blog/530-how-we-made-github-fast
99
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
