2 ms·
You say those OpenSSL alternatives can be dangerous. Yet, you also never recommend against OpenSSL despite it proving itself to be quite dangerous in more ways
by nickpsecurity 11y ago
You say those OpenSSL alternatives can be dangerous. Yet, you also never recommend against OpenSSL despite it proving itself to be quite dangerous in more ways than just cryptographic. Strange double standard.
Anyway, Fox IT [1] recently used PolarSSL in their OpenVPN respin. It's been immune to a number of issues that hit OpenSSL while their mailing list indicates steady work at finding and fixing its own problems. Improved the cryptographic defaults, too. The effort is open source. If you see non-OpenSSL crypto problems, feel free to publish them and suggest improvements so people in or outside those projects can make the systems better. So far, you mainly just blanket recommend against while pushing dangerous stuff (OpenSSL) on readers.
Note: At least you endorsed two alternatives to OpenSSL in this one. A first.
[1] https://openvpn.fox-it.com/background.html https://openvpn.fox-it.com/background.html
- tptacek 11y agoThat's correct. I do not recommend against BoringSSL and LibreSSL, and I do recommend against PolarSSL. PolarSSL is, obviously, immune to the specific coding errors in OpenSSL. What you seem to have trouble acknowledging is the converse issue.
- nickpsecurity 11y agoThat'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.