openbsd - A mirror of https://github.com/libressl/openbsd.git

	Commit message (Collapse)	Author	Age	Files	Lines
*	Consistently mark up various ASN.1 type names defined in standards	schwarze	2016-12-25	1	-7/+17
\| \| \| \|	related to X.509 with .Vt such that they can be searched for.
*	Document OCSP_RESPONSE_new(3), OCSP_RESPONSE_free(3),	schwarze	2016-12-12	1	-36/+144
\| \| \| \| \| \| \| \| \| \| \| \|	OCSP_RESPBYTES_new(3), OCSP_RESPBYTES_free(3), OCSP_BASICRESP_new(3), OCSP_BASICRESP_free(3), OCSP_RESPDATA_new(3), OCSP_RESPDATA_free(3), OCSP_RESPID_new(3), and OCSP_RESPID_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. Sort functions into a logical order and apply minor wording tweaks.
*	Delete most references to crypto(3). That page isn't useful enough	schwarze	2016-12-06	1	-3/+2
\| \| \| \|	to be pointed to from random individual pages.
*	Import OCSP documentation from OpenSSL, leaving out some stuff	schwarze	2016-11-27	1	-0/+134
	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.