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

	Commit message (Collapse)	Author	Age	Files	Lines
*	man pages: add missing commas between subordinate and main clauses	naddy	2022-03-31	1	-4/+4
\| \| \| \| \| \| \|	jmc@ dislikes a comma before "then" in a conditional, so leave those untouched. ok jmc@
*	document OCSP_cert_status_str(3)	schwarze	2019-08-27	1	-3/+19
\|
*	Document OCSP_basic_verify(3).	schwarze	2019-03-15	1	-5/+75
\| \| \| \| \| \|	From David dot von dot Oheimb at siemens dot com via OpenSSL commit b8c32081 Feb 10 15:45:11 2018 +0100, which is still under a free license because it is before the 1.1.1 branch point.
*	finish crypto HISTORY; mostly 1.1.0/6.3, but also various other fixes	schwarze	2018-03-23	1	-2/+6
\|
*	crypto HISTORY up to 0.9.7; researched from OpenSSL git	schwarze	2018-03-22	1	-2/+18
\|
*	In ocsp.h rev. 1.12 2018/03/17 14:44:34, jsing@ provided	schwarze	2018-03-18	1	-4/+14
\| \| \| \| \|	OCSP_SINGLERESP_get0_id(3). OpenSSL fails to document it, so document it from scratch.
*	Consistently mark up various ASN.1 type names defined in standards	schwarze	2016-12-25	1	-5/+11
\| \| \| \|	related to X.509 with .Vt such that they can be searched for.
*	Write OCSP_CRLID_new(3) and OCSP_SERVICELOC_new(3) from scratch.	schwarze	2016-12-12	1	-1/+2
\| \| \| \| \| \| \| \| \| \| \|	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.
*	Document OCSP_SINGLERESP_new(3), OCSP_SINGLERESP_free(3),	schwarze	2016-12-12	1	-3/+90
\| \| \| \| \| \| \| \| \| \|	OCSP_CERTSTATUS_new(3), OCSP_CERTSTATUS_free(3), OCSP_REVOKEDINFO_new(3), and OCSP_REVOKEDINFO_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.
*	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/+285
	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.