From a70940667f0bff95b1713207fb193394afc30fca Mon Sep 17 00:00:00 2001
From: Chris Wanstrath <chris@ozmm.org>
Date: Thu, 3 Sep 2009 20:46:23 -0700
Subject: damn you tekkub

---
 _posts/2009-06-23-security.textile | 1 +
 1 file changed, 1 insertion(+)

(limited to '_posts/2009-06-23-security.textile')

diff --git a/_posts/2009-06-23-security.textile b/_posts/2009-06-23-security.textile
index 62ce4e0..7805e61 100644
--- a/_posts/2009-06-23-security.textile
+++ b/_posts/2009-06-23-security.textile
@@ -20,6 +20,7 @@ We do not encrypt repositories on disk because it would not be any more secure:
 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.
 
 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.
 
 h2. Maintaining security
-- 
cgit v1.3.1

