Announcing the first SHA-1 collision
security.googleblog.com
Announcing the first SHA-1 collision
1–10 of 524 posts
Re: Announcing the first SHA-1 collision
#2So good timing to have just started working on a sha3 version of git I guess...
Re: Announcing the first SHA-1 collision
#3[deleted]
Re: Announcing the first SHA-1 collision
#4[deleted]
Re: Announcing the first SHA-1 collision
#5[deleted]
Re: Announcing the first SHA-1 collision
#6Anyone have back of the envelope calculations for the cost of the CPU and GPU time?
Re: Announcing the first SHA-1 collision
#7Here's a good blog about how SHA-1 works:
http://www.metamorphosite.com/one-way-hash-encryption-sha1-d....
The biggest risk I see with this is how torrents are affected:
https://en.wikipedia.org/wiki/Torrent_poisoning
There's also a problem with git, but I don't see it being that as susceptible as torrents:
Re: Announcing the first SHA-1 collision
#8So good timing to have just started working on a sha3 version of git I guess...
[deleted]
Re: Announcing the first SHA-1 collision
#9Anyone have back of the envelope calculations for the cost of the CPU and GPU time?
On the shattered webpage:
This attack required over 9,223,372,036,854,775,808 SHA1 computations. This took the equivalent processing power as 6,500 years of single-CPU computations and 110 years of single-GPU computations.
Re: Announcing the first SHA-1 collision
#10Anyone have back of the envelope calculations for the cost of the CPU and GPU time?
[deleted]