3 ms·
That's straightforward and means we agree on an alternative (LibreSSL). You haven't mentioned the converse issue though: only vague warnings with a broad word (
by nickpsecurity 11y ago
That's straightforward and means we agree on an alternative (LibreSSL). You haven't mentioned the converse issue though: only vague warnings with a broad word (cryptographic). I'm not even disagreeing with you on PolarSSL, necessarily. The problem is you quickly dismiss them without details while you don't do the same for OpenSSL despite known, horrific details available justifying avoiding it. So, I guess the dispute boils down to those issues:
1. What's the specific reason those libraries suck worse than OpenSSL (which SUCKS) and where did you publish that for peer review/improvement?
2. Why don't you treat OpenSSL the same for all its problems and recommend what you believe is a decent alternative (eg LibreSSL)? (Double standards always bother me in this field.)
That's the consistent trend in these threads: deny several for vague reasons; fine with a known bad one despite non-vague reasons against.
- tptacek 11y agoI'm not going to share details with you. This is not an arbitrary recommendation I am just making up to troll you with.
- nickpsecurity 11y agoSounds like an NDA. Ok, I believe you on that one. With your seconding it & OpenBSD team's rep, my new recommendation was going to be LibreSSL anyway.