@cwebber since git already uses that sha1 since SHAttered
@cwebber personally I assumed sha1 chosen-prefix attacks would be the next thing, and already hardened git-annex's use of git against them :P
@joeyh do you have a writeup somewhere on how you did so?
@cwebber no, but basically have enough control over your data formats that there's no place to hide the added data that makes the collision happen
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!