4 ms·
And Linus was told of this and, in typical Linus fashion, he dismissed it.
by staticassertion 5y ago
And Linus was told of this and, in typical Linus fashion, he dismissed it.
- stickfigure 5y agoIs there some way of co-opting the bitcoin network into calculating specific hash collisions?
- loeg 5y agoNo; it's a different algorithm.
- drexlspivey 5y agoYou would need 6 zettabytes per second to even store all the hashes generated by the BTC network. That’s many times the world’s storage capacity generated every second.
- Dylan16807 5y agoAnd was he wrong?
- staticassertion 5y agoYes. He chose to design his system with no ability to migrate and use a hash algorithm that was already known to be flawed. https://www.metzdowd.com/pipermail/cryptography/2017-February/031623.html https://www.metzdowd.com/pipermail/cryptography/2017-Februar...
- Dylan16807 5y agoOh, you're not talking about him dismissing news of practical attacks as a direct threat, you're talking about him being dismissive very early on about the idea that he was doing a bad job of picking a hash. Yeah, okay, he was wrong to be dismissive there.
- qqii 5y agoFrom the threat it looks like Linus' threat model for git is simply different from the common use today. Of course a judgement under a different threat model would make it seem like a bad tradeoff!
- staticassertion 5y agoIt's more that Linus: 1. Didn't understand the attack 2. Doesn't understand security 3. Doesn't care He's shown this repeatedly for decades.