More precision on what exactly OCSP_id_cmp and OCSP_issuer_id_cmp compare.
The existing description was lacking and incorrect, respectively.

man pages: add missing commas between subordinate and main clauses

jmc@ dislikes a comma before "then" in a conditional, so leave those
untouched.

ok jmc@

new manual page X509_ocspid_print(3)
using input from tb@, and OK tb@ on an earlier version

Tree structure for manual pages: crypto(3) links to 33 function
group pages, and these link on to all their second-level subpages.
Only a handful of second-level pages have third-level subpages.
So a

Tree structure for manual pages: crypto(3) links to 33 function
group pages, and these link on to all their second-level subpages.
Only a handful of second-level pages have third-level subpages.
So all crypto pages can now be reached from the www.libressl.org
frontpage via at most four clicks, in most cases three clicks.
Also link back from leaf pages to their respective group pages
and add a couple of additional links between related pages.
Triggered by a question from deraadt@.
OK jmc@ tb@

show more ...

Document const change for OCSP_cert_to_id()

ok jsing

In ocsp.h rev. 1.14 2018/05/13 10:30:52, tb@ added const qualifiers
to the arguments of OCSP_cert_id_new(3). Adjust the manual.

crypto HISTORY up to 0.9.7; researched from OpenSSL git

Consistently mark up various ASN.1 type names defined in standards
related to X.509 with .Vt such that they can be searched for.

Make sure all manual pages discussing X509_NAME objects
reference X509_NAME_new(3). Sparingly add a few other
references to relevant X509_NAME*(3) pages while here.

Document OCSP_CERTID_new(3) listed in <openssl/ocsp.h> and in OpenSSL
doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies
the wrong header file.

Add some information about what the

Document OCSP_CERTID_new(3) listed in <openssl/ocsp.h> and in OpenSSL
doc/man3/X509_dup.pod. Note that the OpenSSL documentation specifies
the wrong header file.

Add some information about what the OCSP_CERTID object actually
represents, along with the pertinent STANDARDS reference.

show more ...

Delete most references to crypto(3). That page isn't useful enough
to be pointed to from random individual pages.

various cleanup;

Import OCSP documentation from OpenSSL, leaving out some stuff
that we don't have, fixing some bugs and tweaking some parts for
readability.

P.S.
Why did some people write a HTTP client implementati

Import OCSP documentation from OpenSSL, leaving out some stuff
that we don't have, fixing some bugs and tweaking some parts for
readability.

P.S.
Why did some people write a HTTP client implementation and then
decide that the best place to publish it might be a crypto(3)
library? Oh never mind, to go easy on my sanity, i should probably
stop asking such questions and just document what i find.

show more ...