3 ms·
It only bothers me in the same sense that I'd be bothered seeing the 3rd or 4th article about "why I don't conduct routine operations on my family to save some
by davidw 13y ago
It only bothers me in the same sense that I'd be bothered seeing the 3rd or 4th article about "why I don't conduct routine operations on my family to save some money".
More seriously, as someone else says elsewhere, it seems better to confront the problem head on, and help people figure things out in terms of what's a really bad idea, what you can reasonably hope to piece together yourself using off the shelf pieces, and what the heck: what to do to get more experience if you're interested in different areas of crypto and security. I mean, those "perfect" people who write stuff had to get their start somewhere, right? The author of this particular piece strikes me as correctly cautious - "I'm not smart enough" - or something like that. Should crypto writing be left to people who feel like they are pretty hot shit? Somehow that doesn't strike me as a good way to decide. What are some materials you should master in order to do X, Y, or Z with some degree of certainty?
I don't know much about crypto and security stuff, so I'm not the one to write it, but I think a more detailed article might be more beneficial, because "don't touch crypto stuff" is awfully vague. For instance, utilizing GPG or SSL seems like it makes sense for some situations, and that there are a fair number of people who can make them work ok. Designing your own crypto algorithm and implementing it in C probably is not something most people ought to do outside of experimenting for their own interest. But they why's and how's ought to be explained some too. I guess what bugs me about some of these articles is that they feel a bit cargo-culty in the sense of worshiping the security gods that you must make obeisance to rather than simply explaining some facts about various aspects of crypto and security.
One more thought on the subject: if people don't understand why some things are bad ideas, how can they explain it to their bosses asking them to do something silly?
- tptacek 13y agoThanks for writing this. I don't agree with a lot of it but I'm glad to have good counterpoints to my (uh) strongly held opinions, well articulated.
- davidw 13y agoI think at heart, the thing I'm trying to say is that a "just the facts, m'am" approach will work well with some people like myself. I am fully convinced that I am not competent to write crypto algorithms; nor am I enthusiastic about attempting to code them in C. But at the same time, there's something grating about the "ooooh, scary" approach. Maybe it works better with younger developers who aren't as cognizant of the risks and difficulties?