3 ms·
Whose fault is that, then? If you know so much about crypto, and you know OWASP's info on crypto is bad, then why haven't you contributed? This is the problem
by moron4hire 11y ago
Whose fault is that, then? If you know so much about crypto, and you know OWASP's info on crypto is bad, then why haven't you contributed?
This is the problem with crypto experts. You're all "find a crypto expert". But you just sit there on your thumbs and don't contribute in any way other than building libraries with such bad UX that lead to more "find a crypto expert" advice.
- sarciszewski 11y ago> This is the problem with crypto experts. You're all "find a crypto expert". But you just sit there on your thumbs and don't contribute in any way other than building libraries with such bad UX that lead to more "find a crypto expert" advice. Well, I for one have been contributing, so there's that. https://www.owasp.org/index.php?title=How_to_protect_sensitive_data_in_URL%27s&diff=prev&oldid=200468 https://www.owasp.org/index.php?title=How_to_protect_sensiti...
- tptacek 11y agoThat's just the wiki. The wiki has all the problems any wiki does, but the formal documents OWASP issues are worse, and not as easily fixed.
- sarciszewski 11y agoI can clean up the OWASP wiki, but not the people or the paperwork they produce. I can clean up Stack Overflow, but not Google's search results. I try where I can, and hope that makes an impact. (Aside: the people at the local OWASP chapter here in Orlando are competent and want to fix things. Not sure about everywhere else.)
- tptacek 11y agoThat's a self-evidently dumb comment, but in fact I've had experience trying to talk to OWASP about crypto, and found it an enervating waste of time. Things may have gotten better in the last 2 years since I stopped paying attention (though: I doubt it), but my experience of it is that it's governed mostly by the kinds of consultants who parachute into projects to configure Fortify. Despite not having much software development experience, those kinds of consultants have very strong opinions about things like crypto. The problem is very much not limited to crypto. I think OWASP is mostly unsalvageable, and that the most productive thing to be done is to warn developers to take their advice with a grain of salt. There's useful stuff in there, but there's bad stuff too. That's fine if all you're purporting to build is a wiki, but it's less fine when your goal is to be the bible of appsec. They are simply not that.
- deleted 11y ago[deleted]
- sarciszewski 11y agoLet me offer a concrete example of the attitude Thomas is referring to: https://github.com/OWASP/phpsec/issues/108 https://github.com/OWASP/phpsec/issues/108 Highlight: Kerckhoff's principle applies to cryptography, not application security. - AbiusX, OWASP project leader for PHP Security https://github.com/OWASP/phpsec/issues/108#issuecomment-159689730 https://github.com/OWASP/phpsec/issues/108#issuecomment-1596...
- deleted 11y ago[deleted]
- pm24601 11y agoMaybe because people have other things to do with their day? There are lots of things I could contribute to or fix. I pick the things I care about. The same is true for anyone that actually wants to improve things. Lack of focus is the surest way to frustration and ineffectiveness.