[openssl-commits] [openssl] OpenSSL_1_1_0-stable update

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

The branch OpenSSL_1_1_0-stable has been updated
       via  6787c60df982fe7631c97ca91eff83b5efac017f (commit)
      from  effdcf6c2a10afea8041addb8ccce2367ecaac0d (commit)

- Log -----------------------------------------------------------------
commit 6787c60df982fe7631c97ca91eff83b5efac017f
Author: Hubert Kario <hkario at redhat.com>
Date:   Fri Sep 29 15:36:01 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/4442)


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 36bd00d..08aae5e 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.
 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)>.

More information about the openssl-commits mailing list