tptacek

If you mean the OpenSSL CLI, it's hard to think of a more footgun-y cryptographic tool than the one that:

* defaults to unauthenticated encryption

* buries its one authenticated mode

* requires explicit command-line nonces

* defaults to an MD5 KDF

You could probably keep going for another 10 bullets. Never use the OpenSSL CLI for anything other than TLS stuff.

Jan 4 at 1:17amWeb
Show threadquotemstrJan 4

Yeah, the OpenSSL CLI sucks. So what's to be done?

Sure, we can build a 25519-specific tool with a less footgun-y interface. Fine, whatever, for that one use case.

Or we can build an alternative OpenSSL CLI that explodes OpenSSL and its numerous useful features in a general way and helps fix lots of use cases.

Show threadtptacekJan 4
Nothing is to be done. Just don't use the OpenSSL CLI. It's a deeply cursed concept for a tool!
Show threadquotemstrJan 4
A command like cryptography swiss army knife useful though. If not openssl, then what?
Show threadtptacekJan 4
It's useful as a toy and a learning tool, but for nothing else. For those two things, OpenSSL is fine as it is.