[openssl-commits] [openssl] master update

[Kurt Roeckx]

The branch master has been updated
       via  b9e54e98066c1ff8adab5d68b6c114b14d2f74e5 (commit)
      from  9e4c97774861949f6f987772c0b579fe8a9c7d5a (commit)


- Log -----------------------------------------------------------------
commit b9e54e98066c1ff8adab5d68b6c114b14d2f74e5
Author: Kurt Roeckx <kurt at roeckx.be>
Date:   Thu Jul 26 11:10:24 2018 +0200

    Fix inconsisten use of bit vs bits
    
    Reviewed-by: Tim Hudson <tjh at openssl.org>
    GH: #6794

-----------------------------------------------------------------------

Summary of changes:
 doc/man3/BN_generate_prime.pod | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/man3/BN_generate_prime.pod b/doc/man3/BN_generate_prime.pod
index 4b085e7..7cfa96e 100644
--- a/doc/man3/BN_generate_prime.pod
+++ b/doc/man3/BN_generate_prime.pod
@@ -103,8 +103,8 @@ probabilistic primality test with B<nchecks> iterations. If
 B<nchecks == BN_prime_checks>, a number of iterations is used that
 yields a false positive rate of at most 2^-64 for random input.
 The error rate depends on the size of the prime and goes down for bigger primes.
-The rate is 2^-80 starting at 308 bits, 2^-112 at 852 bit, 2^-128 at 1080 bits,
-2^-192 at 3747 bit and 2^-256 at 6394 bit.
+The rate is 2^-80 starting at 308 bits, 2^-112 at 852 bits, 2^-128 at 1080 bits,
+2^-192 at 3747 bits and 2^-256 at 6394 bits.
 
 When the source of the prime is not random or not trusted, the number
 of checks needs to be much higher to reach the same level of assurance: