3 ms·
A lot of this may come down to learning materials. If you go pick up some books and tutorials on how to learn X, I can pretty much guarantee that they're going
by fencepost 8y ago
A lot of this may come down to learning materials.
If you go pick up some books and tutorials on how to learn X, I can pretty much guarantee that they're going to follow a pattern of "here's how to build a basic functional and maybe useful application" and security is going to be an afterthought if it's considered at all. As you continue to learn, there's a fair chance that you'll start with expanding on some of what you've already done in building that sample application - the one with no security.
- baby 8y agoThis was one of the critique of "Applied Cryptography", see https://blog.cryptographyengineering.com/2011/11/07/in-defense-of-applied-cryptography/ https://blog.cryptographyengineering.com/2011/11/07/in-defen... > The detailed argument goes something like this: Applied Cryptography demystified cryptography for a lot of people. By doing so, it empowered them to experiment with crypto techniques, and to implement their own code. No problem so far. > Unfortunately, some readers, abetted by Bruce’s detailed explanations and convenient source code examples, felt that they were now ready to implement crypto professionally. Inevitably their code made its way into commercial products, which shipped full of horribly ridiculous, broken crypto implementations. This is the part that was not so good. We’re probably still dealing with the blowback today. The follow up book from Schneier (Cryptography Engineering) included a whole chapter on "bringing in experts if you deal with cryptography).