GitHub

GitHub

@github

Social coding.

San Francisco, CA · github.com

Tweets

  1. Another note regarding the OpenSSL vulnerability: SSH is not affected. You don't need to do anything with your SSH keys.

  2. We will have a detailed blog post describing the OpenSSL issues, our response, and what you should do later today. (5/5)

  3. We are continuing work on other services and coordinating with all of our service providers to make sure we're protected. (4/5)

  4. We patched OpenSSL last night and regenerated SSL keys and certificates for and our API today. (3/5)

  5. GitHub Enterprise instances are not affected by the OpenSSL vulnerability. (2/5)

  6. We are aware of the OpenSSL "Heartbleed" vulnerability and have been working to mitigate it since it was announced yesterday. (1/5)

  7. Want to get started with Git and GitHub? Join us for another Patchwork night at GitHub HQ on March 27th!

Loading seems to be taking a while.

Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.