5 ms·
> The private key was exposed in a public GitHub repo. How do you know this? Github runs scanner for private keys in public and private repos and notifies own
by theteapot 4y ago
> The private key was exposed in a public GitHub repo.
How do you know this?
Github runs scanner for private keys in public and private repos and notifies owner (I did it once so I know ... ;)). So some Github engineer likely would have received such an email if what you say is true. Hilarious.
- 3np 4y agoFrom the OP: > This week, we discovered that GitHub.com’s RSA SSH private key was briefly exposed in a public GitHub repository.
- Veen 4y agoIt says exactly that in the article: > This week, we discovered that GitHub.com’s RSA SSH private key was briefly exposed in a public GitHub repository Hilarious.
- theteapot 4y agoI didn't read it fully before commenting. I'm sorry.
- comprev 4y agoIf everyone read the entire article of each HN submission the comments section would be wildly different :-)
- adrr 4y agoI can’t see that could ever happen. Is the key just floating around on their employees computers and skeins accidentally committed it?
- roblabla 4y agoMaybe because the article says so? > This week, we discovered that GitHub.com’s RSA SSH private key was briefly exposed in a public GitHub repository