wireguard-openbsd - WireGuard implementation for the OpenBSD kernel

	Commit message (Collapse)	Author	Age	Files	Lines
*	Tree structure for manual pages: crypto(3) links to 33 function	schwarze	2019-06-06	1	-2/+3
\| \| \| \| \| \| \| \| \| \| \|	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@
*	Document const change for OCSP_cert_to_id()	tb	2018-08-24	1	-4/+4
\| \| \| \|	ok jsing
*	In ocsp.h rev. 1.14 2018/05/13 10:30:52, tb@ added const qualifiers	schwarze	2018-05-13	1	-5/+5
\| \| \| \|	to the arguments of OCSP_cert_id_new(3). Adjust the manual.
*	crypto HISTORY up to 0.9.7; researched from OpenSSL git	schwarze	2018-03-22	1	-2/+6
\|
*	Consistently mark up various ASN.1 type names defined in standards	schwarze	2016-12-25	1	-3/+5
\| \| \| \|	related to X.509 with .Vt such that they can be searched for.
*	Make sure all manual pages discussing X509_NAME objects	schwarze	2016-12-14	1	-3/+5
\| \| \| \| \|	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	schwarze	2016-12-12	1	-16/+52
\| \| \| \| \| \| \| \|	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.
*	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.
*	various cleanup;	jmc	2016-11-30	1	-3/+3
\|
*	Import OCSP documentation from OpenSSL, leaving out some stuff	schwarze	2016-11-27	1	-0/+187
	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.