News for hackers. Stuff that matters.
Re:How I implemented my own crypto by mrschwabe on Thursday August 03, 2017 @06:31AM (#14918390)
Another angle is that a compromised security protocol used by a 100,000 developers is far more fruitful than having to assign a human specialist to crack & reverse engineer 100,000 uniquely thought-out implementations.
Re:How I implemented my own crypto by wolco on Thursday August 03, 2017 @08:13AM (#14918843)
This is the point people miss. Same as wordpress vs creating your own blog. The more popular the software the larger the interest and the bigger exploit if successful.
Re:How I implemented my own crypto by arcticbull on Thursday August 03, 2017 @09:46AM (#14919499)
It is less likely, though, and more likely to get fixed everywhere fast.

100,000 easy to crack implementations with obvious errors isn't really more secure than 1 super difficult, super well optimized/secured implementation, is it?

Re:How I implemented my own crypto by wolco on Thursday August 03, 2017 @10:11AM (#14919707)
It is more difficult to crack 100,000 different interfaces because the time required to learn each one is a fixed cost. Having one central implementation makes it much easier to expliot because if an issue is discovered it can be immediately used everywhere. Don't put all your eggs in one basket.
Re:How I implemented my own crypto by calafrax on Thursday August 03, 2017 @01:39PM (#14921788)
> more likely to get fixed everywhere fast openssl bugs were around for a very long time
Re:How I implemented my own crypto by calafrax on Thursday August 03, 2017 @01:38PM (#14921771)
exactly. a very shitty unique implementation is much less likely to be hacked than a near bulletproof implementation used by millions with a single flaw.