Re:A GitHub Issue Title Compromised 4k Developer Machines
by sheept on Thursday March 05, 2026 @04:48PM
(#47267769)
Needs to be a fork.
Related: https://trufflesecurity.com/blog/anyone-can-access-deleted-a...
Re:A GitHub Issue Title Compromised 4k Developer Machines
by PunchyHamster on Friday March 06, 2026 @03:53AM
(#47272622)
It appears that under their system all forks belong to same repo (I imagine they just make _fork/<forkname> ref under git when there is something forked off main repo) presumably to save on storage. And so accessing a single commit doesn't really care about origin(as finding to which branch(es) commit belongs would be a lot of work)
Wow. Does the SHA need to belong to a fork of the repo? Or is GitHub just exposing all (public?) repo commits as a giant content-addressable store?