> Besides, the known collision attack generates files with blocks of binary garbage, which makes it difficult to trick someone into accepting. It won't look lik

> Besides, the known collision attack generates files with blocks of binary garbage, which makes it difficult to trick someone into accepting. It won't look like source code, and if someone accepts binary blobs of executable code, you don't need collisions to pwn them. IDK, I could see this happening in multiple ways. 1. Images / media artifacts stored for display purposes 2. Cached files - 'zero install' config for yarn comes to mind, where every dependency has its file cached in git. Plus binary files aren't displayed in git diffs so it seems somewhat easy to sneak in. Otherwise, yeah, agree. Most people don't rely on Git's security model, they rely on Github's.