2 ms·
My engineering intuition is that from a practical standpoint, this isn't an issue for Git. It's much more likely that the network will go down or all the copies
by brudgers 10y ago
My engineering intuition is that from a practical standpoint, this isn't an issue for Git. It's much more likely that the network will go down or all the copies of the repository become deleted or a developer will use Git tooling maliciously than for an unintended collision to occur.
Could a malicious actor construct a collision and use it to subvert some code base? Sure. And it has probably already happened. Crytography is considered a munition in the US and there are US government agencies which have been devoted to cryptography continuously since the Second World War and there are similar agencies in other countries and every last one of them employs many highly motivated highly educated and highly skilled cryptographic experts and the latest money is not an object compute hardware to find exactly this type of vulnerability, create capabilities based on that discovery, and to deploy them into the wild for national and political and economic interests.
To put it a different way, by the time something like this hits Hacker News, the odds are that organizations with the capability and funding to do things like inventing computers have already figured it out. Just as there is a discontinuity between what Google and SpaceX can do that looks like the future and the average engineer with a laptop or a garage can do that looks like the future, there is a similar gap between the future that Space X and Google can build and what a government institution can build. Space X hauls payloads to an existing station in LEO and Google runs on an internet that existed before it did.
The horses are long gone before anyone realizes the barn door is open.