> out of an abundance of caution, we replaced our RSA SSH host [...]
> GitHub.com’s RSA SSH private key was briefly exposed in a public GitHub repository
What the... That's not "an abundance of caution". That's the only possible course of action.
> GitHub.com’s RSA SSH private key was briefly exposed in a public GitHub repository
What the... That's not "an abundance of caution". That's the only possible course of action.
Do they expect people to think "Wow, Github leaked a key, but even without knowing if anyone snagged it, they're still replacing it. Wow, they go above and beyond."
It's so ridiculous.
After all it’s them hosting and serving the requests for that (and every other) repo.
Only _reasonable_ course of action. Possible is to do nothing =)
That's the "caution" part.