3 ms·
Another way to think about it: if there's a use-case where the API OpenSSL provides (requiring that the consumer specify a list of cipher-suites, etc.) is wrong
by derefr 12y ago
Another way to think about it: if there's a use-case where the API OpenSSL provides (requiring that the consumer specify a list of cipher-suites, etc.) is wrong, then that consumer should not be directly consuming OpenSSL; that level of abstraction is the wrong fit for their project.
What we need is a "library" that just hardcodes agreed-upon conventions on top of OpenSSL. Import that instead of OpenSSL, use its API (which would be mostly transparent calls through to OpenSSL using the current best practices), and everything gets taken care of. New best practices? Updated library package.
- nailer 12y agoMozilla Server Side TLS is that set of agreed upon conventions. The Moz logic is great, since the conventions produce 3 sets of cipher suites with different compatibility / security tradeoffs. The idea of a library to implement that logic is solid: we made https://www.npmjs.com/package/ssl-rsa-strength https://www.npmjs.com/package/ssl-rsa-strength as a library implementing Mozilla's logic a little while ago.
- thrownaway2424 12y agoAre you uncertain about whether OpenSSL's APIs are suited to their use cases? Let me tell you, every API that OpenSSL provides is as wrong as it can get. It has the wrongest APIs that have ever been perpetrated.