3 ms·
The OpenSSL command line is more or less a test driver / reference for the library. It's a little weird to criticize its UX. Also: it's pretty easy to make some
by tptacek 2y ago
The OpenSSL command line is more or less a test driver / reference for the library. It's a little weird to criticize its UX. Also: it's pretty easy to make something look bananas if you surface every obscure option in its main screen!
- teruakohatu 2y ago> The OpenSSL command line is more or less a test driver / reference for the library hmmm, not sure about that. Its the main (only?) interface if an individual wants to mess with certificates or generate them. It is often reported ACME/LE took off because it is easier to configure an ACME client than the annual wrestling with openssl. But if openssl had been easy for common user tasks maybe LE would have taken longer to be adopted. ffmpeg also has a notoriously difficult CLI interface. Today you can just ask a LLM to generate you a command, the consequences are low if it gets it slightly wrong. The consequences of getting openssl wrong could not be obvious immediately and result in a lot of debugging down the line.
- throwup238 2y agoLE took off because everyone was charging ridiculous amounts for certificates and few people needed the verification that comes with that. ISRG created ACME for LE.
- tpmoney 2y agoOne of my personal frustrations with SSL as implemented in most systems is the conflation between encrypted communication and verified communication. SSH sort of got this right with ToFU as a default behavior but I think a lot of the resistance and difficulty in adopting SSL for encrypted intranet communication comes from the need to do the CA and cert signing song and dance. If you could turn on encryption without needing to do ID validation by default it would make things easier for people I know that encrypted communication without knowing that your talking to the right person is somewhat useless, but it works for SSH most of the time, there’s no reason it couldn’t work well for https and encrypted db connections etc.
- wolf550e 2y agoI recommend https://cryptography.io/en/latest/ https://cryptography.io/en/latest/ as a way to use openssl library instead of the command line.
- teruakohatu 2y agoThat actually looks very useful. Thanks.
- larusso 2y agoI think you are right. On the other hand it’s the fact that a lot of tutorials / getting started guides etc include some ssl invocations to execute a specific command for key/cert creation. And a user wishing to adjust and maybe understand things gets thrown at a man page that is so overloaded. Similar to git. But git’s cli at least has a clear setup with optional vs mandatory values. I always disliked commandline interfaces with mandatory option fields.
- tuwtuwtuwtuw 2y agoWhere do I find the UI for it then?
- epistasis 2y agoI don't think it's a critique of the library; calling the x509 specification complex enough to be magic seems accurate. Honestly I love the UI presented: concise, shows all the options, a fantastic summary of the CLI without having to scroll a massive man page or website. I'd love this for all the super complex CLI tools I need to use, as a visual cheatsheet on where to search in the man page.
- behringer 2y agoI'd love this for all the cli tools. Instead we'll get more boot managers and desktop managers.
- bckr 2y agoConsider helping make such a thing!
- AlotOfReading 2y agoI wrote a personal tool to do this automatically by parsing '--help' after I couldn't remember the tar options for the millionth time. Turns out the programs that have complicated, undiscoverable interfaces also tend to omit useful options from automatically discoverable documentation, so it wasn't especially reliable.
- BoingBoomTschak 2y agoReminds me of a similar wish for argv introspection I had at some point (e.g. https://github.com/ImageMagick/ImageMagick/issues/7688 https://github.com/ImageMagick/ImageMagick/issues/7688) that went nowhere. I hardcoded curl this way.
- gyomu 2y agoI’ve always found it a shame that the UNIX philosophy seemed to stop at system/command line tools and no one ever took the further step to apply it to user interfaces. UIs generated in systematic, composable ways emerging naturally from all the plumbing (pipes, option flags, etc) we already have in place.