diff options
| author | tekkub <tekkub@gmail.com> | 2009-06-23 17:49:36 -0600 |
|---|---|---|
| committer | tekkub <tekkub@gmail.com> | 2009-06-23 17:49:36 -0600 |
| commit | f9baeeee746ea7d76d81d9941561b09eff54ec16 (patch) | |
| tree | 92894d8448c530b0b51e6b34053322f26d59987e /_posts/2009-06-23-security.textile | |
| parent | 6e38f80495ecd99d6bea11c157f9cfb2831a177d (diff) | |
Typo
Diffstat (limited to '_posts/2009-06-23-security.textile')
| -rw-r--r-- | _posts/2009-06-23-security.textile | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/_posts/2009-06-23-security.textile b/_posts/2009-06-23-security.textile index f9a7b3d..711e29a 100644 --- a/_posts/2009-06-23-security.textile +++ b/_posts/2009-06-23-security.textile @@ -16,7 +16,7 @@ The SSH login credentials used to push and pull can not be used to access a shel h3. File system and backups -We do not encrypt repositories on disk because it would not be any more secure: the website and git backend 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. +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. Our database and your repositories are backed up nightly off-site. We do not retroactively remove repositories from backups when deleted by the user, as we may need to restore the repo for the user if it was removed accidentally. |