Re:Lavabit code open sourced
by darawk on Sunday May 01, 2016 @03:26AM
(#11605265)
That isn't entirely true. You could easily develop a web extension that validated the hash of the scripts being sent down the wire. Then you'd have an equivalent security guarantee to a normal desktop client.
[ Parent
| on HN ]
Re:Lavabit code open sourced
by deadmaildrop on Sunday May 01, 2016 @08:38PM
(#11608558)
Or you just inject your own payload and pad the payload until it has a hash collision with the original. At 128M hashes per second you can probably find a payload that works within a day. Since the hashes are published, usually, you know your target so it's just a matter of time.
Re:Lavabit code open sourced
by colejohnson66 on Sunday May 01, 2016 @09:56PM
(#11608780)
You do know how hard it would be to find a SHA-256 collision? We haven't even found /one/. Sure, if you used MD5, you could expect a collision, but SHA256?
Re:Lavabit code open sourced
by deadmaildrop on Sunday May 01, 2016 @10:34PM
(#11608905)
I've seen them. Just recently I had a short burst of collisions. It happens. Don't underestimate the resolve of someone who wants to grind an axe.
Lol, no. You have not seen a SHA256 collision. One has never been found, by anyone, ever.
Re:Lavabit code open sourced
by deadmaildrop on Tuesday May 03, 2016 @12:47AM
(#11617978)
Thanks for calling me a liar. I see the quality of people on this thread has suddenly dropped. So, stick with respectful discourse or keep it to yourself. You are clearly not in the industry, just another useless troll.