summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorKurt Roeckx <kurt@roeckx.be>2018-07-26 11:10:24 +0200
committerKurt Roeckx <kurt@roeckx.be>2018-07-26 11:29:52 +0200
commitd69f31fcc38878769c8c917f8724c5aef10fd847 (patch)
tree299be591f3240e9eccf886dcce6735bc54ec5d2e /doc
parentbe4e1f79f631e49c76d02fe4644b52f907c374b2 (diff)
Fix inconsistent use of bit vs bits
Reviewed-by: Tim Hudson <tjh@openssl.org> GH: #6794 (cherry picked from commit b9e54e98066c1ff8adab5d68b6c114b14d2f74e5)
Diffstat (limited to 'doc')
-rw-r--r--doc/crypto/BN_generate_prime.pod4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/crypto/BN_generate_prime.pod b/doc/crypto/BN_generate_prime.pod
index 0079f17a57..003d123940 100644
--- a/doc/crypto/BN_generate_prime.pod
+++ b/doc/crypto/BN_generate_prime.pod
@@ -92,8 +92,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: