the SHAttered attack weakened SHA-1 by 17bits, one bit is lost to the birthday attack, and the other 142 bits were brute-forced
and the other 142 bits were brute-forcedWoah, so you can just brute-force md5 because it's 128 bit long, huh?
In total the computational effort spent is equivalent to 263.1 SHA-1 compressions
but IIRC git doesn't use SHA1 for securityThis is false, the -S command signs the SHA-1 of the commit, not to mention that if a collision happens it can mess your repo or even insert malicious code without warning.
It's not really a problem until someone comes up with two colliding source files (i.e. ASCII text.)Many projects have some kind of binaries in their repos, not necessarily the compiled program, it might just be binary blobs.
I, for one, am not happy to have a publicly disclosed exploit kill SHA1 instead of it being silently exploited by theFTFYspies paid by oppressive governmentsjailbreaking, DRM-killing, freedom-fighting crackers who give us warez, pr0n, leaked datasheets, and other juicy 0day releases.
using actual brain power instead of CPU time
access to the exact source codeThat's open-source software, not free as in beer, which is what I meant.
To be free software means users are legally permittedTo be free software means you ain't gotta pay for it.