It's funny to me when people complain about something they get for free. There are at least two solutions to this problem and neither of them are writing a blog to complain about the work that someone else has done and given a way for free. You could write some documentation and give it to them. Or you could pay someone to write it for the project. The author seems to know quite a bit about OpenSSL/LibreSSL. I'd thin…
But there is documentation for LibreSSL. As an OpenBSD project they take documentation just as seriously as code. I just don't get how the article makes that claim when there are links to any man page you need here: http://www.libressl.org/
The sorry state of OpenSSL usability
41–45 of 45 posts
Re: The sorry state of OpenSSL usability
#42This is a macOS problem. OpenSSL on Linux has extensive man pages and a --help switch.
E.g. OpenSSL on OpenBSD does have a man page. But unfortunately no --help, at least on my older version.
Also, on OpenBSD his example of generating an RSA key creates one with a 2048 bit modulus.
Re: The sorry state of OpenSSL usability
#43Earlier quoted context omitted.
Original quote: > Going to that website and clicking on openssl reveals a manual page Please tell me where the very first OpenSSL link takes you. That's the one I clicked just to check. Oh, right, it has to be the openssl(1), helpfully hidden away in the list of various utilities.
> Please tell me where the very first OpenSSL link takes you. That's the one I clicked just to check. Are you referring to the line informing the reader that LibreSSL is a fork and provides a link the the OpenSSL project?
Re: The sorry state of OpenSSL usability
#44Re: The sorry state of OpenSSL usability
#45Earlier quoted context omitted.
openssl(1) links to https://man.openbsd.org/openssl
It took me a while to find where the link to openssl(1) is on that page. So, in order to find documentation, one would have to land on LibreSSL webpage and click on all links hoping to get to the correct one.