2 ms·
Option 1: Rely on what everyone else does. What happens if that method is flawed? You hear about it as soon as it's discovered and it gets fixed quick. Option
by InclinedPlane 15y ago
Option 1: Rely on what everyone else does.
What happens if that method is flawed? You hear about it as soon as it's discovered and it gets fixed quick.
Option 2: Roll your own stack based on a personal understanding of cryptography.
What happens if that method is flawed? Perhaps only you and an attacker could possibly know such a thing. You have to be ever vigilant and you have to acquire an incredible amount of crypto knowledge. If you ever leave the company they are pretty much fucked from then on until whatever you wrote is replaced.
Don't roll your own system.
- InclinedPlane 15y agoTo add on to this, it is of course necessary to have enough familiarity and competence with the basic principles of cryptography to know that you're "doing what everyone else is doing" correctly, instead of just some silly pantomime, such as: http://thedailywtf.com/Articles/Topgrade,-SHA1-Encryption.aspx http://thedailywtf.com/Articles/Topgrade,-SHA1-Encryption.as... But it's not necessary to understand the depths of cryptography beyond that there are various black boxes that have certain properties.