[openssl-commits] [openssl] OpenSSL_1_0_2-stable update

Rich Salz rsalz at openssl.org
Fri Sep 29 16:53:27 UTC 2017

The branch OpenSSL_1_0_2-stable has been updated
       via  d9a38e859dfe30a112c421dc7b32821370efd805 (commit)
      from  20d2aaf22e54d07ead144c5e79fdaf6903cdbf2d (commit)

- Log -----------------------------------------------------------------
commit d9a38e859dfe30a112c421dc7b32821370efd805
Author: Hubert Kario <hkario at redhat.com>
Date:   Fri Sep 29 15:40:43 2017 +0200

    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 at openssl.org>
    Reviewed-by: Rich Salz <rsalz at openssl.org>
    (Merged from https://github.com/openssl/openssl/pull/4443)


Summary of changes:
 doc/crypto/BN_new.pod | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/doc/crypto/BN_new.pod b/doc/crypto/BN_new.pod
index 413a1ea..d446603 100644
--- a/doc/crypto/BN_new.pod
+++ b/doc/crypto/BN_new.pod
@@ -34,7 +34,8 @@ If B<a> is NULL, nothing is done.
-BN_new() returns a pointer to the B<BIGNUM>. If the allocation fails,
+BN_new() returns a pointer to the B<BIGNUM> initialised to the value 0.
+If the allocation fails,
 it returns B<NULL> and sets an error code that can be obtained
 by L<ERR_get_error(3)|ERR_get_error(3)>.

More information about the openssl-commits mailing list