diff options
Diffstat (limited to '_posts/2009-06-23-security.textile')
| -rw-r--r-- | _posts/2009-06-23-security.textile | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/_posts/2009-06-23-security.textile b/_posts/2009-06-23-security.textile index 53bea67..8a2f17d 100644 --- a/_posts/2009-06-23-security.textile +++ b/_posts/2009-06-23-security.textile @@ -1,6 +1,7 @@ --- layout: default title: GitHub Security +categories: "Site Policy" --- We know your code is extremely important to you and your business and we're very protective of it. After all, GitHub's code is hosted on GitHub, too! @@ -25,7 +26,7 @@ Every piece of hardware we use has an identical copy ready and waiting for an im We do not encrypt repositories on disk because it would not be any more secure: the website and git back-end would need to decrypt the repositories on demand, slowing down response times. Any user with shell access to the file system would have access to the decryption routine, thus negating any security it provides. Therefore, we focus on making our machines and network as secure as possible. -h2. Employee access +h2. Employee access No GitHub employees ever access private repositories unless required to for support reasons. Staff working directly in the file store access the compressed Git database, your code is never present as plaintext files like it would be in a local clone. Support staff may log into your account to access settings related to your support issue. In rare cases staff may need to pull a clone of your code, this will only be done with your consent. Support staff does not have direct access to clone any repo, he will need to temporarily attach his SSH key to your account to pull a clone. When working a support issue we do our best to respect your privacy as much as possible, we only access the files and settings needed to resolve your issue. All cloned repos are deleted as soon as the support issue has been resolved. |