4 ms·
i mean, pretty sure you mean "Never roll your own crypto".. most people should be writing some bit of "security".. You probably want authentication, authorizati
by spydum 8y ago
i mean, pretty sure you mean "Never roll your own crypto".. most people should be writing some bit of "security".. You probably want authentication, authorization, audit and so on in your app.
Now, I do think I agree in the spirit of what you mean: frameworks and libraries should make this stuff easy.. I think for the most part, they do, for example: django has authentication; ruby has gems like Devise; python has stuff like flask-security..
So they exist, there are solutions, it's just not always well known by developers. So they do what they have been trained to: just write their own (faster to reason about my own code than consuming another dependency with all it's archaic config!).
- strken 8y agoYeah, I was taking a bit of license with the term. The problem is that rolling your own non-crypto security is still fraught with danger, and not all languages provide good libraries that hide the dangerous choices for you. Even worse, those libraries often aren't written or audited by security experts either, which is a bigger problem.