From: Hubert Kario <hkario@redhat.com>
Date: Fri, 29 Sep 2017 13:36:01 +0000 (+0200)
Subject: doc: note that the BN_new() initialises the BIGNUM
X-Git-Tag: OpenSSL_1_1_0g~59
X-Git-Url: https://git.librecmc.org/?a=commitdiff_plain;h=6787c60df982fe7631c97ca91eff83b5efac017f;p=oweals%2Fopenssl.git

doc: note that the BN_new() initialises the BIGNUM

BN_new() and BN_secure_new() not only allocate memory, but also
initialise it to deterministic value - 0.

Document that behaviour to make it explicit

backport from #4438

Reviewed-by: Richard Levitte <levitte@openssl.org>
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/4442)
---

diff --git a/doc/crypto/BN_new.pod b/doc/crypto/BN_new.pod
index 36bd00da28..08aae5e919 100644
--- a/doc/crypto/BN_new.pod
+++ b/doc/crypto/BN_new.pod
@@ -36,7 +36,8 @@ If B<a> is NULL, nothing is done.
 =head1 RETURN VALUES
 
 BN_new() and BN_secure_new()
-return a pointer to the B<BIGNUM>. If the allocation fails,
+return a pointer to the B<BIGNUM> initialised to the value 0.
+If the allocation fails,
 they return B<NULL> and set an error code that can be obtained
 by L<ERR_get_error(3)>.