News for hackers. Stuff that matters.

A comment on BitTorrent v2 (2020). Parent comment

Re:BitTorrent v2 (2020) by Stevvo on Monday January 10, 2022 @10:33AM (#29876373)
SHA1 collision was never much of a reason to change it in the first place; there is no practical attack that arises from it.
[ Parent | on HN ]
Re:BitTorrent v2 (2020) by EVa5I7bHFq9mnYK on Monday January 10, 2022 @11:43AM (#29877500)
1) Take a popular game torrent 2) add crypto mining code 3) pad it so the SHA1 stays the same 4) seed it, the magnet links will pick up your version 5) profit!
[ Parent | on HN ]
Re:BitTorrent v2 (2020) by GoblinSlayer on Tuesday January 11, 2022 @05:06AM (#29889576)
That's a preimage attack. For example, the entire bitcoin network today needs something on the order of a trillion years for a preimage attack on MD5, multiply by another trillion for a SHA1 preimage attack.
[ Parent | on HN ]
Re:BitTorrent v2 (2020) by daniel-cussen on Monday January 10, 2022 @12:26PM (#29878215)
Between 1 and 2, remove the crypto mining code that came with it.
[ Parent | on HN ]
Re:BitTorrent v2 (2020) by ttybird2 on Monday January 10, 2022 @01:24PM (#29879138)
Except that this is not how collision attacks work.
[ Parent | on HN ]