3 ms·
I feel like this article is missing a disclaimer that you should never, ever roll your own crypto and that this is purely an educational exercise.
by Svetlitski 5y ago
I feel like this article is missing a disclaimer that you should never, ever roll your own crypto and that this is purely an educational exercise.
- deleted 5y ago[deleted]
- sverhagen 5y agoI totally agree. But meanwhile, I'm wondering if the droves of people that I have met who forego proven libraries and frameworks to roll their own, wouldn't also just do the same for crypto? Because exactly the integration and maintenance and socialization of these projects are underestimated. Now, probably there are less people rolling their own crypto than there are people running their own, say... application framework, or ORM. Because crypto has more of a general feeling of "it's hard" about it. But I am still suspicious that there wouldn't be a bunch of folks out there who had to prove to their team that they were smart enough to roll their own crypto too, and are now stuck with it!
- dnautics 5y agoOn the other hand I once had a CTO get mad at me because I customized a few options in the builtin TLS library for erlang (I made it possible to sign the keys against an IP address instead of only FQDNs, which was fine for our use case) - for "rolling your own crypto".