| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
using input from tb@, and OK tb@ on an earlier version
|
|
|
|
|
| |
and to isolated obsolete pages;
OK bcook@ jmc@
|
|
|
|
|
|
|
|
|
|
|
| |
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@
|
| |
|
|
|
|
| |
related to X.509 with .Vt such that they can be searched for.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
These two and OCSP_CRLID_free(3) and OCSP_SERVICELOC_free(3) are
public by being in OpenSSL doc/man3/X509_dup.pod.
OCSP_crlID_new(3) and OCSP_url_svcloc_new(3) are related and,
even though completely undocumented in OpenSSL, obviously much
more important.
If you had told me a year ago that i would ever write such text,
i would have called you crazy.
|
|
|
|
|
|
|
|
|
|
|
| |
OCSP_REQINFO_new(3), OCSP_REQINFO_free(3), OCSP_ONEREQ_new(3),
OCSP_ONEREQ_free(3), all 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 these objects actually represent,
along with the pertinent STANDARDS reference.
Minor wording tweaks.
|
|
|
|
| |
to be pointed to from random individual pages.
|
| |
|
|
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.
|