]> git.ipfire.org Git - thirdparty/openssl.git/commitdiff
DOC: OSSL_PARAM_{set,get,construct}_BN() currently only supports nonnegative numbers
authorRichard Levitte <levitte@openssl.org>
Sun, 21 Nov 2021 08:48:05 +0000 (09:48 +0100)
committerRichard Levitte <levitte@openssl.org>
Tue, 23 Nov 2021 10:40:29 +0000 (11:40 +0100)
Reviewed-by: Matt Caswell <matt@openssl.org>
Reviewed-by: Tomas Mraz <tomas@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/17074)

doc/man3/OSSL_PARAM_int.pod

index 69b723d3482fccff1f34cc6a85aa221df1a51a24..9ca725d120ec2d19fa14bfdcf41ebd706d930baa 100644 (file)
@@ -331,6 +331,12 @@ representable by the target type or parameter.
 Apart from that, the functions must be used appropriately for the
 expected type of the parameter.
 
+OSSL_PARAM_get_BN() and OSSL_PARAM_set_BN() currently only support
+nonnegative B<BIGNUM>s, and by consequence, only
+B<OSSL_PARAM_UNSIGNED_INTEGER>.  OSSL_PARAM_construct_BN() currently
+constructs an B<OSSL_PARAM> structure with the data type
+B<OSSL_PARAM_UNSIGNED_INTEGER>.
+
 For OSSL_PARAM_construct_utf8_ptr() and OSSL_PARAM_consstruct_octet_ptr(),
 I<bsize> is not relevant if the purpose is to send the B<OSSL_PARAM> array
 to a I<responder>, i.e. to get parameter data back.