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

	Commit message (Collapse)	Author	Age	Files	Lines
*	.Lb libcrypto ; OK tb@	schwarze	2025-06-08	1	-2/+3
\|
*	ASN1_{,F,T}BOOLEAN_it and the encoding and decoding API will move	tb	2022-01-12	1	-5/+2
\| \| \| \| \| \|	to internal only soon. Stop documenting them. ok inoguchi jsing
*	new manual page ASN1_NULL_new(3), also documenting ASN1_NULL_free(3)	schwarze	2021-11-22	1	-2/+3
\|
*	new manual page d2i_ASN1_BOOLEAN(3) also documenting i2d_ASN1_BOOLEAN(3)	schwarze	2021-11-21	1	-2/+3
\|
*	document ASN1_item_pack(3) and ASN1_item_unpack(3)	schwarze	2021-11-15	1	-2/+3
\|
*	new manual pages	schwarze	2021-11-07	1	-2/+5
\| \| \| \|	ASN1_item_digest(3), ASN1_item_sign(3), and ASN1_item_verify(3)
*	document ASN1_get_object(3)	schwarze	2021-07-11	1	-2/+3
\|
*	Improve pages that briefly mentioned ERR - usually below SEE ALSO -	schwarze	2019-06-14	1	-5/+7
\| \| \| \| \|	but failed to provide any real information. OK tb@ jmc@
*	crypto HISTORY up to 0.9.7; researched from OpenSSL git	schwarze	2018-03-22	1	-2/+8
\|
*	Correct the description of ASN1_item_free(3) with respect to	schwarze	2018-02-25	1	-4/+13
\| \| \| \| \|	optional reference counting. ETOOMUCHMAGIC. By the way, this public hellhole is still undocumented in OpenSSL.
*	Document ASN1_TYPE_new(3) and ASN1_TYPE_free(3), even though OpenSSL	schwarze	2017-01-03	1	-2/+4
\| \| \| \| \| \| \| \| \| \| \|	does not document them. By being in <openssl/asn1.h>, they are public, and it makes no sense to document accessors but not document constructors and destructors. Improve the one-line description. Mention various missing details. Many wording improvements. Add some cross references.
*	Very carefully tweak OpenSSL doc/man3/d2i_X509.pod and create a new	schwarze	2016-12-24	1	-0/+103
	ASN1_item_d2i(3) manual page from it. Enough text remains to keep Stephen Henson's Copyright. The eight functions documented in this new page are listed in <openssl/asn1.h> and in Symbols.list, so they are public even though OpenSSL does not document them. They are very important because hundreds of documented, much-used public interface functions are trivial wrappers around them, sharing their complicated semantics and their copious CAVEATS and BUGS. The plan is for the many pages documenting the wrappers to become very concise, to focus on the few type-dependent specifics, and to point to this new page for the details of the semantics, for the CAVEATS, and for the BUGS. While here, write a companion page ASN1_item_new(3) from scratch. The user interface described in that page scares the hell out of me, and i think people writing code to handle ASN.1 ought to be aware of that dangerous user interface design, or they will sooner or later get trapped.