Tell HN: GitHub Please Reset Your Password

7 points by tridentlead ↗ HN
Just received via email

———————-

Hi there,

During the course of regular auditing, GitHub discovered that a recently introduced bug exposed a small number of users’ passwords to our internal logging system, including yours. We have corrected this, but you'll need to reset your password to regain access to your account.

GitHub stores user passwords with secure cryptographic hashes (bcrypt). However, this recently introduced bug resulted in our secure internal logs recording plaintext user passwords when users initiated a password reset. Rest assured, these passwords were not accessible to the public or other GitHub users at any time. Additionally, they were not accessible to the majority of GitHub staff and we have determined that it is very unlikely that any GitHub staff accessed these logs. GitHub does not intentionally store passwords in plaintext format. Instead, we use modern cryptographic methods to ensure passwords are stored securely in production. To note, GitHub has not been hacked or compromised in any way.

You can regain access to your account by resetting your password using the link below::

https://github.com/password_reset

If you have any lingering questions or concerns about this, don't hesitate to let us know. You can reach us by emailing support@github.com or by using our contact form:

https://github.com/contact

Thanks,

GitHub Support

5 comments

[ 3.3 ms ] story [ 22.6 ms ] thread
Seems like it’s often the side channels that get people, even when they apply best practices to the primary system. I would be interested to know how passwords got into a log entry though.
Just got this as well. I changed my password on GitHub about a month ago, and it looks like only those who changed a password were affected.

If I have to guess, they maybe saved the plaintext from the form when testing the password reset feature for some reason?

I got the alert. My last password change was 2018-02-04
I also changed my password pretty recently, this seems like a good candidate for the source of the problem.
(comment deleted)