From 5d36fd8301731635dc8c8e88aa3b0eff831e2625 Mon Sep 17 00:00:00 2001
From: PJ Hyett <pjhyett@gmail.com>
Date: Tue, 12 Jan 2010 14:35:20 -0800
Subject: Merge security pages

---
 _posts/2009-06-23-security.textile | 26 ++++++++++++++++++++------
 1 file changed, 20 insertions(+), 6 deletions(-)

(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 7805e61..53bea67 100644
--- a/_posts/2009-06-23-security.textile
+++ b/_posts/2009-06-23-security.textile
@@ -1,11 +1,17 @@
 ---
 layout: default
-title: GitHub security
+title: GitHub Security
 ---
 
-h2. Engine Yard security
+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!
 
-Our host, Engine Yard, has a PDF available on their security practices "here":http://www.engineyard.com/docs/EY_Security_WP.pdf.
+h2. Physical security measures
+
+GitHub's infrastructure is hosted on "Rackspace":http://rackspace.com, a publicly-traded company that's committed to keeping your data secure. They provide us with state-of-the-art servers protected by biometric locks and round-the-clock interior and exterior surveillance monitoring. Only authorized personnel have access to the data center. 24/7/365 onsite staff also provides additional protection against unauthorized entry and security breaches.
+
+h2. Software security measures
+
+In addition to Rackspace's system monitoring, we also employ a team of 24/7/365 server specialists at "Anchor Hosting":http://www.anchor.com.au/dedicated-hosting/dedicated-support.py to keep our software and its dependencies up to date eliminating potential security vulnerabilities. They have also setup a wide range of monitoring solutions for preventing and eliminating attacks to the site.
 
 h2. Communications
 
@@ -15,9 +21,9 @@ The SSH login credentials used to push and pull can not be used to access a shel
 
 h2. File system and backups
 
-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.
+Every piece of hardware we use has an identical copy ready and waiting for an immediate hot-swap in case of hardware or software failure. Every line of code we store is saved on a minimum of three different servers, including an off-site backup just in case a meteor ever hits the Rackspace datacenter (we'll keep our fingers crossed that doesn't happen). 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.
 
-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.
+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 
 
@@ -31,6 +37,14 @@ We keep a security consultant on retainer to help identify and prevent new attac
 
 We're extremely concerned and active about security, but we're aware that many companies are not comfortable hosting code outside their firewall. For these companies we offer our "Firewall Install":http://fi.github.com/, a version of GitHub that can be installed to a server within the company's network.
 
-h2. Contact
+h2. Credit card safety
+
+When you sign up for a paid account on GitHub, we do not store any of your card information on our servers. It's handed off to "Braintree Payment Solutions":http://braintreepaymentsolutions.com, a company dedicated to storing your sensitive data on "PCI-Compliant":http://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard servers.
+
+h2. Contact Us
 
 Have a question, concern, or comment about GitHub security? Please email "support@github.com":mailto:support@github.com for general inquiries and "security@github.com":mailto:security@github.com for emergencies.
+
+h2. Need to report something?
+
+Please email us immediately at "security@github.com":mailto:security@github.com, this will go directly to one or more of the GitHub founders and will receive our full attention. If we don't respond immediately, there's a good chance we're trying to fix it first.
-- 
cgit v1.3.1


From 183b0a0a3cae437eadfc15d3218c3ec257618452 Mon Sep 17 00:00:00 2001
From: tekkub <tekkub@gmail.com>
Date: Tue, 12 Jan 2010 16:34:44 -0700
Subject: New policy pages

---
 _layouts/default.html              |  1 +
 _posts/2009-06-23-security.textile |  3 +-
 _posts/2010-01-12-privacy.markdown | 46 ++++++++++++++++++++
 _posts/2010-01-12-terms.markdown   | 88 ++++++++++++++++++++++++++++++++++++++
 4 files changed, 137 insertions(+), 1 deletion(-)
 create mode 100644 _posts/2010-01-12-privacy.markdown
 create mode 100644 _posts/2010-01-12-terms.markdown

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

diff --git a/_layouts/default.html b/_layouts/default.html
index afc4fa6..aeae66b 100644
--- a/_layouts/default.html
+++ b/_layouts/default.html
@@ -8,6 +8,7 @@ sidebar_cats:
 - windows
 - linux
 - other
+- "Site Policy"
 ---
 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
 	"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
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.
 
diff --git a/_posts/2010-01-12-privacy.markdown b/_posts/2010-01-12-privacy.markdown
new file mode 100644
index 0000000..a7c2273
--- /dev/null
+++ b/_posts/2010-01-12-privacy.markdown
@@ -0,0 +1,46 @@
+---
+layout: default
+title: GitHub Privacy Policy
+categories: "Site Policy"
+---
+
+General Information
+-------------------
+
+We collect the e-mail addresses of those who communicate with us via e-mail, aggregate information on what pages consumers access or visit, and information volunteered by the consumer (such as survey information and/or site registrations). The information we collect is used to improve the content of our Web pages and the quality of our service, and is not shared with or sold to other organizations for commercial purposes, except to provide products or services you've requested, when we have your permission, or under the following circumstances:
+
+* It is necessary to share information in order to investigate, prevent, or take action regarding illegal activities, suspected fraud, situations involving potential threats to the physical safety of any person, violations of [Terms of Service](/terms), or as otherwise required by law.
+* We transfer information about you if Logical Awesome or GitHub is acquired by or merged with another company. In this event, Logical Awesome will notify you before information about you is transferred and becomes subject to a different privacy policy.
+
+Information Gathering and Usage
+-------------------------------
+
+* When you register for GitHub we ask for information such as your name, email address, billing address, credit card information. Members who sign up for the free account are not required to enter a credit card.
+* Logical Awesome uses collected information for the following general purposes: products and services provision, billing, identification and authentication, services improvement, contact, and research.
+
+Cookies
+-------
+
+* A cookie is a small amount of data, which often includes an anonymous unique identifier, that is sent to your browser from a web site's computers and stored on your computer's hard drive.
+* Cookies are required to use the GitHub service.
+* We use cookies to record current session information, but do not use permanent cookies. You are required to re-login to your GitHub account after a certain period of time has elapsed to protect you against others accidentally accessing your account contents.
+
+Data Storage
+------------
+
+Logical Awesome uses third party vendors and hosting partners to provide the necessary hardware, software, networking, storage, and related technology required to run GitHub. Although Logical Awesome owns the code, databases, and all rights to the GitHub application, you retain all rights to your data.
+
+Disclosure
+----------
+
+Logical Awesome may disclose personally identifiable information under special circumstances, such as to comply with subpoenas or when your actions violate the [Terms of Service](/terms).
+
+Changes
+-------
+
+Logical Awesome may periodically update this policy. We will notify you about significant changes in the way we treat personal information by sending a notice to the primary email address specified in your GitHub primary account holder account or by placing a prominent notice on our site.
+
+Questions
+---------
+
+Any questions about this Privacy Policy should be addressed to <support@github.com>.
diff --git a/_posts/2010-01-12-terms.markdown b/_posts/2010-01-12-terms.markdown
new file mode 100644
index 0000000..95b50de
--- /dev/null
+++ b/_posts/2010-01-12-terms.markdown
@@ -0,0 +1,88 @@
+---
+layout: default
+title: GitHub Terms of Service
+categories: "Site Policy"
+---
+
+By using the GitHub.com web site ("Service"), or any services of Logical Awesome LLC ("Logical Awesome"), you are agreeing to be bound by the following terms and conditions ("Terms of Service").  IF YOU ARE ENTERING INTO THIS AGREEMENT ON BEHALF OF A COMPANY OR OTHER LEGAL ENTITY, YOU REPRESENT THAT YOU HAVE THE AUTHORITY TO BIND SUCH ENTITY, ITS AFFILIATES AND ALL USERS WHO ACCESS OUR  SERVICES THROUGH YOUR ACCOUNT TO THESE TERMS AND CONDITIONS, IN WHICH CASE THE TERMS "YOU" OR "YOUR" SHALL REFER TO SUCH ENTITY, ITS AFFILIATES AND USERS ASSOCIATED WITH IT. IF YOU DO NOT HAVE SUCH AUTHORITY, OR IF YOU DO NOT AGREE WITH THESE TERMS AND CONDITIONS, YOU MUST NOT ACCEPT THIS AGREEMENT AND MAY NOT USE THE SERVICES.
+
+Logical Awesome reserves the right to update and change the Terms of Service from time to time without notice. Any new features that augment or enhance the current Service, including the release of new tools and resources, shall be subject to the Terms of Service. Continued use of the Service after any such changes shall constitute your consent to such changes. You can review the most current version of the Terms of Service at any time at: <http://github.com/site/terms>
+
+Violation of any of the terms below will result in the termination of your Account. While Logical Awesome prohibits such conduct and Content on the Service, you understand and agree that Logical Awesome cannot be responsible for the Content posted on the Service and you nonetheless may be exposed to such materials. You agree to use the Service at your own risk.
+
+Account Terms
+-------------
+
+* You must be 13 years or older to use this Service.
+* You must be a human. Accounts registered by "bots" or other automated methods are not permitted.
+* You must provide your legal full name, a valid email address, and any other information requested in order to complete the signup process.
+* Your login may only be used by one person - a single login shared by multiple people is not permitted. You may create separate logins for as many people as your plan allows.
+* You are responsible for maintaining the security of your account and password. Logical Awesome cannot and will not be liable for any loss or damage from your failure to comply with this security obligation.
+* You are responsible for all Content posted and activity that occurs under your account (even when Content is posted by others who have accounts under your account).
+* If you are using a free account you are not permitted to block ads.
+* One person or legal entity may not maintain more than one free account.
+* You may not use the Service for any illegal or unauthorized purpose. You must not, in the use of the Service, violate any laws in your jurisdiction (including but not limited to copyright or trademark laws).
+
+API Terms
+---------
+
+Customers may access their GitHub account data via an API (Application Program Interface). Any use of the API, including use of the API through a third-party product that accesses GitHub, is bound by these Terms of Service plus the following specific terms:
+
+* You expressly understand and agree that Logical Awesome shall not be liable for any direct, indirect, incidental, special, consequential or exemplary damages, including but not limited to, damages for loss of profits, goodwill, use, data or other intangible losses (even if Logical Awesome has been advised of the possibility of such damages), resulting from your use of the API or third-party products that access data via the API.
+* Abuse or excessively frequent requests to GitHub via the API may result in the temporary or permanent suspension of your account's access to the API. Logical Awesome, in its sole discretion, will determine abuse or excessive usage of the API. Logical Awesome will make a reasonable attempt via email to warn the account owner prior to suspension.
+* Logical Awesome reserves the right at any time to modify or discontinue, temporarily or permanently, your access to the API (or any part thereof) with or without notice.
+
+Payment, Refunds, Upgrading and Downgrading Terms
+-------------------------------------------------
+
+* All paid plans must enter a valid credit card. Free accounts are not required to provide a credit card number.
+* __An upgrade from the free plan to any paying plan will immediately bill you.__
+* __The Service is billed in advance on a monthly basis and is non-refundable. There will be no refunds or credits for partial months of service, upgrade/downgrade refunds, or refunds for months unused with an open account. In order to treat everyone equally, no exceptions will be made.__
+* All fees are exclusive of all taxes, levies, or duties imposed by taxing authorities, and you shall be responsible for payment of all such taxes, levies, or duties, excluding only United States (federal or state) taxes.
+* For any upgrade or downgrade in plan level, your credit card that you provided will automatically be charged the new rate on your next billing cycle.
+* Downgrading your Service may cause the loss of Content, features, or capacity of your Account. Logical Awesome does not accept any liability for such loss.
+
+Cancellation and Termination
+----------------------------
+
+* __You are solely responsible for properly canceling your account. An email or phone request to cancel your account is not considered cancellation. You can cancel your account at any time by clicking on the Account link in the global navigation bar at the top of the screen. The Account screen provides a simple no questions asked cancellation link.__
+* All of your Content will be immediately deleted from the Service upon cancellation. This information can not be recovered once your account is cancelled.
+* If you cancel the Service before the end of your current paid up month, your cancellation will take effect immediately and you will not be charged again.
+* Logical Awesome, in its sole discretion, has the right to suspend or terminate your account and refuse any and all current or future use of the Service, or any other Logical Awesome service, for any reason at any time. Such termination of the Service will result in the deactivation or deletion of your Account or your access to your Account, and the forfeiture and relinquishment of all Content in your Account. Logical Awesome reserves the right to refuse service to anyone for any reason at any time.
+
+
+Modifications to the Service and Prices
+---------------------------------------
+
+* Logical Awesome reserves the right at any time and from time to time to modify or discontinue, temporarily or permanently, the Service (or any part thereof) with or without notice.
+* Prices of all Services, including but not limited to monthly subscription plan fees to the Service, are subject to change upon 30 days notice from us. Such notice may be provided at any time by posting the changes to the GitHub Site ([github.com](http://github.com)) or the Service itself.
+* GitHub shall not be liable to you or to any third party for any modification, price change, suspension or discontinuance of the Service.
+
+
+Copyright and Content Ownership
+-------------------------------
+
+* We claim no intellectual property rights over the material you provide to the Service. Your profile and materials uploaded remain yours. However, by setting your pages to be viewed publicly, you agree to allow others to view your Content. By setting your repositories to be viewed publicly, you agree to allow others to view and fork your repositories.
+* Logical Awesome does not pre-screen Content, but Logical Awesome and its designee have the right (but not the obligation) in their sole discretion to refuse or remove any Content that is available via the Service.
+* You shall defend Logical Awesome against any claim, demand, suit or proceeding made or brought against Logical Awesome by a third party alleging that Your Content, or Your use of the Service in violation of this Agreement, infringes or misappropriates the intellectual property rights of a third party or violates applicable law, and shall indemnify Logical Awesome for any damages finally awarded against, and for reasonable attorney’s fees incurred by, Logical Awesome in connection with any such claim, demand, suit or proceeding; provided, that Logical Awesome (a) promptly gives You written notice of the claim, demand, suit or proceeding; (b) gives You sole control of the defense and settlement of the claim, demand, suit or proceeding (provided that You may not settle any claim, demand, suit or proceeding unless the settlement unconditionally releases Logical Awesome of all liability); and (c) provides to You all reasonable assistance, at Your expense.
+* The look and feel of the Service is copyright &copy;2010 Logical Awesome LLC. All rights reserved. You may not duplicate, copy, or reuse any portion of the HTML/CSS, Javascript, or visual design elements or concepts without express written permission from Logical Awesome.
+
+
+General Conditions
+------------------
+
+* Your use of the Service is at your sole risk. The service is provided on an "as is" and "as available" basis.
+* Technical support is only provided to paying account holders and is only available via email.
+* You understand that Logical Awesome uses third party vendors and hosting partners to provide the necessary hardware, software, networking, storage, and related technology required to run the Service.
+* You must not modify, adapt or hack the Service or modify another website so as to falsely imply that it is associated with the Service, Logical Awesome, or any other Logical Awesome service.
+* You agree not to reproduce, duplicate, copy, sell, resell or exploit any portion of the Service, use of the Service, or access to the Service without the express written permission by Logical Awesome.
+* We may, but have no obligation to, remove Content and Accounts containing Content that we determine in our sole discretion are unlawful, offensive, threatening, libelous, defamatory, pornographic, obscene or otherwise objectionable or violates any party's intellectual property or these Terms of Service.
+* Verbal, physical, written or other abuse (including threats of abuse or retribution) of any Logical Awesome customer, employee, member, or officer will result in immediate account termination.
+* You understand that the technical processing and transmission of the Service, including your Content, may be transfered unencrypted and involve (a) transmissions over various networks; and (b) changes to conform and adapt to technical requirements of connecting networks or devices.
+* You must not upload, post, host, or transmit unsolicited email, SMSs, or "spam" messages.
+* You must not transmit any worms or viruses or any code of a destructive nature.
+* If your bandwidth usage exceeds 500 MB/month, or significantly exceeds the average bandwidth usage (as determined solely by Logical Awesome) of other GitHub customers, we reserve the right to immediately disable your account or throttle your file hosting until you can reduce your bandwidth consumption.
+* Logical Awesome does not warrant that (i) the service will meet your specific requirements, (ii) the service will be uninterrupted, timely, secure, or error-free, (iii) the results that may be obtained from the use of the service will be accurate or reliable, (iv) the quality of any products, services, information, or other material purchased or obtained by you through the service will meet your expectations, and (v) any errors in the Service will be corrected.
+* You expressly understand and agree that Logical Awesome shall not be liable for any direct, indirect, incidental, special, consequential or exemplary damages, including but not limited to, damages for loss of profits, goodwill, use, data or other intangible losses (even if Logical Awesome has been advised of the possibility of such damages), resulting from: (i) the use or the inability to use the service; (ii) the cost of procurement of substitute goods and services resulting from any goods, data, information or services purchased or obtained or messages received or transactions entered into through or from the service; (iii) unauthorized access to or alteration of your transmissions or data; (iv) statements or conduct of any third party on the service; (v) or any other matter relating to the service.
+* The failure of Logical Awesome to exercise or enforce any right or provision of the Terms of Service shall not constitute a waiver of such right or provision. The Terms of Service constitutes the entire agreement between you and Logical Awesome and govern your use of the Service, superceding any prior agreements between you and Logical Awesome (including, but not limited to, any prior versions of the Terms of Service). You agree that these Terms of Service and Your use of the Service are governed under California law.
+* Questions about the Terms of Service should be sent to <support@github.com>.
-- 
cgit v1.3.1


From 8e766e07a56690d8a84284afb0db85d2e9722128 Mon Sep 17 00:00:00 2001
From: tekkub <tekkub@gmail.com>
Date: Tue, 12 Jan 2010 16:43:44 -0700
Subject: Change the security page to markdown

---
 _posts/2009-06-23-security.markdown | 60 +++++++++++++++++++++++++++++++++++++
 _posts/2009-06-23-security.textile  | 51 -------------------------------
 2 files changed, 60 insertions(+), 51 deletions(-)
 create mode 100644 _posts/2009-06-23-security.markdown
 delete mode 100644 _posts/2009-06-23-security.textile

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

diff --git a/_posts/2009-06-23-security.markdown b/_posts/2009-06-23-security.markdown
new file mode 100644
index 0000000..08f7f4e
--- /dev/null
+++ b/_posts/2009-06-23-security.markdown
@@ -0,0 +1,60 @@
+---
+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!
+
+Physical security measures
+--------------------------
+
+GitHub's infrastructure is hosted on [Rackspace](http://rackspace.com), a publicly-traded company that's committed to keeping your data secure. They provide us with state-of-the-art servers protected by biometric locks and round-the-clock interior and exterior surveillance monitoring. Only authorized personnel have access to the data center. 24/7/365 onsite staff also provides additional protection against unauthorized entry and security breaches.
+
+Software security measures
+--------------------------
+
+In addition to Rackspace's system monitoring, we also employ a team of 24/7/365 server specialists at [Anchor Hosting](http://www.anchor.com.au/dedicated-hosting/dedicated-support.py) to keep our software and its dependencies up to date eliminating potential security vulnerabilities. They have also setup a wide range of monitoring solutions for preventing and eliminating attacks to the site.
+
+Communications
+--------------
+
+All private data exchanged with GitHub is always transmitted over SSL (which is why your dashboard is served over HTTPS, for instance). All pushing and pulling of private data is done over SSH authenticated with keys, not passwords.
+
+The SSH login credentials used to push and pull can not be used to access a shell or the filesystem. All users are virtual (meaning they have no user account on our machines) and are access controlled through the peer reviewed, open source git-shell.
+
+File system and backups
+-----------------------
+
+Every piece of hardware we use has an identical copy ready and waiting for an immediate hot-swap in case of hardware or software failure. Every line of code we store is saved on a minimum of three different servers, including an off-site backup just in case a meteor ever hits the Rackspace datacenter (we'll keep our fingers crossed that doesn't happen). 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.
+
+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.
+
+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.
+
+Maintaining security
+--------------------
+
+We protect your login from brute force attacks with rate limiting.  All passwords are filtered from all our logs and encrypted.  Login information is always sent over SSL.
+
+We keep a security consultant on retainer to help identify and prevent new attack vectors.  We always test new features in order to cut out potential attacks, such as XSS-protecting wikis, and ensuring that Pages cannot access cookies.
+
+We're extremely concerned and active about security, but we're aware that many companies are not comfortable hosting code outside their firewall. For these companies we offer our [Firewall Install](http://fi.github.com/), a version of GitHub that can be installed to a server within the company's network.
+
+Credit card safety
+------------------
+
+When you sign up for a paid account on GitHub, we do not store any of your card information on our servers. It's handed off to [Braintree Payment Solutions](http://braintreepaymentsolutions.com), a company dedicated to storing your sensitive data on [PCI-Compliant](http://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard) servers.
+
+Contact Us
+----------
+
+Have a question, concern, or comment about GitHub security? Please email <support@github.com> for general inquiries and <security@github.com> for emergencies.
+
+Need to report something?
+-------------------------
+
+Please email us immediately at <security@github.com>, this will go directly to one or more of the GitHub founders and will receive our full attention. If we don't respond immediately, there's a good chance we're trying to fix it first.
diff --git a/_posts/2009-06-23-security.textile b/_posts/2009-06-23-security.textile
deleted file mode 100644
index 8a2f17d..0000000
--- a/_posts/2009-06-23-security.textile
+++ /dev/null
@@ -1,51 +0,0 @@
----
-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!
-
-h2. Physical security measures
-
-GitHub's infrastructure is hosted on "Rackspace":http://rackspace.com, a publicly-traded company that's committed to keeping your data secure. They provide us with state-of-the-art servers protected by biometric locks and round-the-clock interior and exterior surveillance monitoring. Only authorized personnel have access to the data center. 24/7/365 onsite staff also provides additional protection against unauthorized entry and security breaches.
-
-h2. Software security measures
-
-In addition to Rackspace's system monitoring, we also employ a team of 24/7/365 server specialists at "Anchor Hosting":http://www.anchor.com.au/dedicated-hosting/dedicated-support.py to keep our software and its dependencies up to date eliminating potential security vulnerabilities. They have also setup a wide range of monitoring solutions for preventing and eliminating attacks to the site.
-
-h2. Communications
-
-All private data exchanged with GitHub is always transmitted over SSL (which is why your dashboard is served over HTTPS, for instance). All pushing and pulling of private data is done over SSH authenticated with keys, not passwords.
-
-The SSH login credentials used to push and pull can not be used to access a shell or the filesystem. All users are virtual (meaning they have no user account on our machines) and are access controlled through the peer reviewed, open source git-shell.
-
-h2. File system and backups
-
-Every piece of hardware we use has an identical copy ready and waiting for an immediate hot-swap in case of hardware or software failure. Every line of code we store is saved on a minimum of three different servers, including an off-site backup just in case a meteor ever hits the Rackspace datacenter (we'll keep our fingers crossed that doesn't happen). 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.
-
-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
-
-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
-
-We protect your login from brute force attacks with rate limiting.  All passwords are filtered from all our logs and encrypted.  Login information is always sent over SSL.
-
-We keep a security consultant on retainer to help identify and prevent new attack vectors.  We always test new features in order to cut out potential attacks, such as XSS-protecting wikis, and ensuring that Pages cannot access cookies.
-
-We're extremely concerned and active about security, but we're aware that many companies are not comfortable hosting code outside their firewall. For these companies we offer our "Firewall Install":http://fi.github.com/, a version of GitHub that can be installed to a server within the company's network.
-
-h2. Credit card safety
-
-When you sign up for a paid account on GitHub, we do not store any of your card information on our servers. It's handed off to "Braintree Payment Solutions":http://braintreepaymentsolutions.com, a company dedicated to storing your sensitive data on "PCI-Compliant":http://en.wikipedia.org/wiki/Payment_Card_Industry_Data_Security_Standard servers.
-
-h2. Contact Us
-
-Have a question, concern, or comment about GitHub security? Please email "support@github.com":mailto:support@github.com for general inquiries and "security@github.com":mailto:security@github.com for emergencies.
-
-h2. Need to report something?
-
-Please email us immediately at "security@github.com":mailto:security@github.com, this will go directly to one or more of the GitHub founders and will receive our full attention. If we don't respond immediately, there's a good chance we're trying to fix it first.
-- 
cgit v1.3.1

