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

	Commit message (Collapse)	Author	Age	Files	Lines
*	mention what BN_ULONG is	schwarze	2022-11-22	1	-3/+12
\|
*	delete references to ERR pages from SEE ALSO where such	schwarze	2019-06-10	1	-4/+3
\| \| \| \|	references were already given below RETURN VALUES right above
*	found a complete archive of SSLeay-0.4 to SSLeay-0.8.1b tarballs	schwarze	2018-03-27	1	-6/+5
\| \| \| \|	on the web, so fix up SSLeay HISTORY accordingly
*	bn.h HISTORY up to SSLeay 0.9.0; researched from OpenSSL git	schwarze	2018-03-21	1	-5/+4
\|
*	bn.h HISTORY up to SSLeay 0.8.1b; researched from OpenSSL git	schwarze	2018-03-20	1	-5/+8
\|
*	replace all references to bn(3) with BN_new(3),	schwarze	2016-12-10	1	-3/+3
\| \| \| \|	and make sure all BN*(3) pages point back to BN_new(3)
*	Add Copyright and license.	schwarze	2016-11-20	1	-6/+53
\| \| \| \| \|	Delete duplicate specification of the error return value of BN_mod_word(3). Fix a markup error in the remaining copy of the same return value.
*	first pass; ok schwarze	jmc	2016-11-06	1	-1/+3
\|
*	On systems where we do not have BN_ULLONG defined (most 64-bit systems),	bcook	2016-07-05	1	-2/+3
\| \| \| \| \| \| \| \| \| \| \| \| \| \|	BN_mod_word() can return incorrect results if the supplied modulus is too big, so we need to fall back to BN_div_word. Now that BN_mod_word may fail, handle errors properly update the man page. Thanks to Brian Smith for pointing out these fixes from BoringSSL: https://boringssl.googlesource.com/boringssl/+/67cb49d045f04973ddba0f92fe8a8ad483c7da89 https://boringssl.googlesource.com/boringssl/+/44bedc348d9491e63c7ed1438db100a4b8a830be ok beck@
*	fourth batch of perlpod(1) to mdoc(7) conversion	schwarze	2015-02-23	1	-0/+123