From: Arran Cudbard-Bell Date: Mon, 28 Mar 2022 19:13:39 +0000 (-0600) Subject: Document the fact that setting a BIO create function means the BIO will no longer... X-Git-Tag: openssl-3.2.0-alpha1~2788 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=dedb1927751bc9a7ada08cfc4dcc481b8ce1ad81;p=thirdparty%2Fopenssl.git Document the fact that setting a BIO create function means the BIO will no longer be marked as initialised Reviewed-by: Tomas Mraz Reviewed-by: Paul Dale Reviewed-by: Todd Short (Merged from https://github.com/openssl/openssl/pull/17983) --- diff --git a/doc/man3/BIO_meth_new.pod b/doc/man3/BIO_meth_new.pod index 15c369e7a98..51db3af0d48 100644 --- a/doc/man3/BIO_meth_new.pod +++ b/doc/man3/BIO_meth_new.pod @@ -118,7 +118,10 @@ for creating a new instance of the BIO respectively. This function will be called in response to the application calling BIO_new() and passing in a pointer to the current BIO_METHOD. The BIO_new() function will allocate the memory for the new BIO, and a pointer to this newly allocated structure will -be passed as a parameter to the function. +be passed as a parameter to the function. If a create function is set, +BIO_new() will not mark the BIO as initialised on allocation. +L must then be called either by the create function, or later, +by a BIO ctrl function, once BIO initialisation is complete. BIO_meth_get_destroy() and BIO_meth_set_destroy() get and set the function used for destroying an instance of a BIO respectively. This function will be