2 ms·
[stub for offtopicness] (title fixed now)
by dang 1y ago
[stub for offtopicness]
(title fixed now)
- jmclnx 1y ago[flagged]
- jasonjmcghee 1y agoSounds like they got their hands on authentication tokens. Through RedHat, not GitHub.
- tzs 1y agoIt looks to me like the article is talking about authentication tokens that they found in the data they took from the breach.
- reactordev 1y ago>”They allegedly found authentication tokens, full database URIs, and other private information in Red Hat code and CERs, which they claimed to use to gain access to downstream customer infrastructure.” They published CERs somewhere that had access keys and urls. Probably to somewhere that it wasn’t authorized to be published or shared and they got a hold of it. Using that, they got a hold of everything else. More CERs, GitHub repos using access tokens, vpn credentials to all the hottest players. At this point, you’d have to tear down and rebuild to undo the damage. Rotating certs, keys, IP’s, the whole nine yards.
- stingrae 1y agoCorrection Posted: "After publishing, Red Hat confirmed that it was a GitLab account breach, not GitHub."
- erikerikson 1y ago"Correction: After publishing, Red Hat confirmed that it was a breach of one of its GitLab instances, and not GitHub. Title and story updated." Title needs updating
- sateesh 1y agoIt's GitLab not GitHub