Update OpenSSL-1.1.1-pre9-dev
This commit is contained in:
+37
-8
@@ -2,7 +2,9 @@
|
||||
|
||||
=head1 NAME
|
||||
|
||||
BN_rand, BN_pseudo_rand, BN_rand_range, BN_pseudo_rand_range - generate pseudo-random number
|
||||
BN_rand, BN_priv_rand, BN_pseudo_rand,
|
||||
BN_rand_range, BN_priv_rand_range, BN_pseudo_rand_range
|
||||
- generate pseudo-random number
|
||||
|
||||
=head1 SYNOPSIS
|
||||
|
||||
@@ -10,10 +12,14 @@ BN_rand, BN_pseudo_rand, BN_rand_range, BN_pseudo_rand_range - generate pseudo-r
|
||||
|
||||
int BN_rand(BIGNUM *rnd, int bits, int top, int bottom);
|
||||
|
||||
int BN_priv_rand(BIGNUM *rnd, int bits, int top, int bottom);
|
||||
|
||||
int BN_pseudo_rand(BIGNUM *rnd, int bits, int top, int bottom);
|
||||
|
||||
int BN_rand_range(BIGNUM *rnd, BIGNUM *range);
|
||||
|
||||
int BN_priv_rand_range(BIGNUM *rnd, BIGNUM *range);
|
||||
|
||||
int BN_pseudo_rand_range(BIGNUM *rnd, BIGNUM *range);
|
||||
|
||||
=head1 DESCRIPTION
|
||||
@@ -37,7 +43,16 @@ If B<bits> is 1 then B<top> cannot also be B<BN_RAND_FLG_TOPTWO>.
|
||||
BN_rand_range() generates a cryptographically strong pseudo-random
|
||||
number B<rnd> in the range 0 E<lt>= B<rnd> E<lt> B<range>.
|
||||
|
||||
The PRNG must be seeded prior to calling BN_rand() or BN_rand_range().
|
||||
BN_priv_rand() and BN_priv_rand_range() have the same semantics as
|
||||
BN_rand() and BN_rand_range() respectively. They are intended to be
|
||||
used for generating values that should remain private, and mirror the
|
||||
same difference between L<RAND_bytes(3)> and L<RAND_priv_bytes(3)>.
|
||||
|
||||
=head1 NOTES
|
||||
|
||||
Always check the error return value of these functions and do not take
|
||||
randomness for granted: an error occurs if the CSPRNG has not been
|
||||
seeded with enough randomness to ensure an unpredictable byte sequence.
|
||||
|
||||
=head1 RETURN VALUES
|
||||
|
||||
@@ -46,20 +61,34 @@ The error codes can be obtained by L<ERR_get_error(3)>.
|
||||
|
||||
=head1 HISTORY
|
||||
|
||||
Starting with OpenSSL release 1.1.0,
|
||||
BN_pseudo_rand() has been identical to BN_rand()
|
||||
and
|
||||
BN_pseudo_rand_range() has been identical to BN_rand_range().
|
||||
=over 2
|
||||
|
||||
=item *
|
||||
|
||||
Starting with OpenSSL release 1.1.0, BN_pseudo_rand() has been identical
|
||||
to BN_rand() and BN_pseudo_rand_range() has been identical to
|
||||
BN_rand_range().
|
||||
The "pseudo" functions should not be used and may be deprecated in
|
||||
a future release.
|
||||
|
||||
=item *
|
||||
|
||||
BN_priv_rand() and BN_priv_rand_range() were added in OpenSSL 1.1.1.
|
||||
|
||||
=back
|
||||
|
||||
=head1 SEE ALSO
|
||||
|
||||
L<ERR_get_error(3)>, L<RAND_add(3)>, L<RAND_bytes(3)>
|
||||
L<ERR_get_error(3)>,
|
||||
L<RAND_add(3)>,
|
||||
L<RAND_bytes(3)>,
|
||||
L<RAND_priv_bytes(3)>,
|
||||
L<RAND(7)>,
|
||||
L<RAND_DRBG(7)>
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
Copyright 2000-2017 The OpenSSL Project Authors. All Rights Reserved.
|
||||
Copyright 2000-2018 The OpenSSL Project Authors. All Rights Reserved.
|
||||
|
||||
Licensed under the OpenSSL license (the "License"). You may not use
|
||||
this file except in compliance with the License. You can obtain a copy
|
||||
|
||||
@@ -65,7 +65,7 @@ BUF_MEM_new_ex() was added in OpenSSL 1.1.0.
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
Copyright 2000-2016 The OpenSSL Project Authors. All Rights Reserved.
|
||||
Copyright 2000-2018 The OpenSSL Project Authors. All Rights Reserved.
|
||||
|
||||
Licensed under the OpenSSL license (the "License"). You may not use
|
||||
this file except in compliance with the License. You can obtain a copy
|
||||
|
||||
@@ -58,7 +58,7 @@ L<DSA_do_sign(3)>
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
Copyright 2000-2016 The OpenSSL Project Authors. All Rights Reserved.
|
||||
Copyright 2000-2018 The OpenSSL Project Authors. All Rights Reserved.
|
||||
|
||||
Licensed under the OpenSSL license (the "License"). You may not use
|
||||
this file except in compliance with the License. You can obtain a copy
|
||||
|
||||
@@ -316,7 +316,7 @@ OBJECT IDENTIFIER or NID_undef if it has no defined OBJECT IDENTIFIER.
|
||||
EVP_CIPHER_CTX_cipher() returns an B<EVP_CIPHER> structure.
|
||||
|
||||
EVP_CIPHER_param_to_asn1() and EVP_CIPHER_asn1_to_param() return greater
|
||||
than zero for success and zero or a negative number.
|
||||
than zero for success and zero or a negative number on failure.
|
||||
|
||||
EVP_CIPHER_CTX_rand_key() returns 1 for success.
|
||||
|
||||
|
||||
@@ -7,7 +7,7 @@ EVP_PKEY_get1_RSA, EVP_PKEY_get1_DSA, EVP_PKEY_get1_DH, EVP_PKEY_get1_EC_KEY,
|
||||
EVP_PKEY_get0_RSA, EVP_PKEY_get0_DSA, EVP_PKEY_get0_DH, EVP_PKEY_get0_EC_KEY,
|
||||
EVP_PKEY_assign_RSA, EVP_PKEY_assign_DSA, EVP_PKEY_assign_DH,
|
||||
EVP_PKEY_assign_EC_KEY, EVP_PKEY_get0_hmac, EVP_PKEY_type, EVP_PKEY_id,
|
||||
EVP_PKEY_base_id, EVP_PKEY_set1_engine - EVP_PKEY assignment functions
|
||||
EVP_PKEY_base_id, EVP_PKEY_set_alias_type, EVP_PKEY_set1_engine - EVP_PKEY assignment functions
|
||||
|
||||
=head1 SYNOPSIS
|
||||
|
||||
@@ -37,6 +37,7 @@ EVP_PKEY_base_id, EVP_PKEY_set1_engine - EVP_PKEY assignment functions
|
||||
int EVP_PKEY_id(const EVP_PKEY *pkey);
|
||||
int EVP_PKEY_base_id(const EVP_PKEY *pkey);
|
||||
int EVP_PKEY_type(int type);
|
||||
int EVP_PKEY_set_alias_type(EVP_PKEY *pkey, int type);
|
||||
|
||||
int EVP_PKEY_set1_engine(EVP_PKEY *pkey, ENGINE *engine);
|
||||
|
||||
@@ -78,6 +79,10 @@ must be called after the key algorithm and components are set up.
|
||||
If B<engine> does not include an B<EVP_PKEY_METHOD> for B<pkey> an
|
||||
error occurs.
|
||||
|
||||
EVP_PKEY_set_alias_type() allows modifying a EVP_PKEY to use a
|
||||
different set of algorithms than the default. This is currently used
|
||||
to support SM2 keys, which use an identical encoding to ECDSA.
|
||||
|
||||
=head1 NOTES
|
||||
|
||||
In accordance with the OpenSSL naming convention the key obtained
|
||||
@@ -98,6 +103,13 @@ is no longer possible: the equivalent is EVP_PKEY_base_id(pkey).
|
||||
EVP_PKEY_set1_engine() is typically used by an ENGINE returning an HSM
|
||||
key as part of its routine to load a private key.
|
||||
|
||||
=head1 EXAMPLES
|
||||
|
||||
After loading an ECC key, it is possible to convert it to using SM2
|
||||
algorithms with EVP_PKEY_set_alias_type:
|
||||
|
||||
EVP_PKEY_set_alias_type(pkey, EVP_PKEY_SM2);
|
||||
|
||||
=head1 RETURN VALUES
|
||||
|
||||
EVP_PKEY_set1_RSA(), EVP_PKEY_set1_DSA(), EVP_PKEY_set1_DH() and
|
||||
@@ -115,13 +127,15 @@ type or B<NID_undef> (equivalently B<EVP_PKEY_NONE>) on error.
|
||||
|
||||
EVP_PKEY_set1_engine() returns 1 for success and 0 for failure.
|
||||
|
||||
EVP_PKEY_set_alias_type() returns 1 for success and 0 for error.
|
||||
|
||||
=head1 SEE ALSO
|
||||
|
||||
L<EVP_PKEY_new(3)>
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
Copyright 2002-2016 The OpenSSL Project Authors. All Rights Reserved.
|
||||
Copyright 2002-2018 The OpenSSL Project Authors. All Rights Reserved.
|
||||
|
||||
Licensed under the OpenSSL license (the "License"). You may not use
|
||||
this file except in compliance with the License. You can obtain a copy
|
||||
|
||||
@@ -236,7 +236,7 @@ type checking.
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
Copyright 2000-2017 The OpenSSL Project Authors. All Rights Reserved.
|
||||
Copyright 2000-2018 The OpenSSL Project Authors. All Rights Reserved.
|
||||
|
||||
Licensed under the OpenSSL license (the "License"). You may not use
|
||||
this file except in compliance with the License. You can obtain a copy
|
||||
|
||||
@@ -22,7 +22,8 @@ the structure and B<cert> its corresponding certificates. B<ca>, if not B<NULL>
|
||||
is an optional set of certificates to also include in the structure.
|
||||
|
||||
B<nid_key> and B<nid_cert> are the encryption algorithms that should be used
|
||||
for the key and certificate respectively. B<iter> is the encryption algorithm
|
||||
for the key and certificate respectively. The modes
|
||||
GCM, CCM, XTS, and OCB are unsupported. B<iter> is the encryption algorithm
|
||||
iteration count to use and B<mac_iter> is the MAC iteration count to use.
|
||||
B<keytype> is the type of key.
|
||||
|
||||
|
||||
+26
-6
@@ -20,13 +20,21 @@ Deprecated:
|
||||
=head1 DESCRIPTION
|
||||
|
||||
RAND_bytes() puts B<num> cryptographically strong pseudo-random bytes
|
||||
into B<buf>. An error occurs if the CSPRNG has not been seeded with
|
||||
enough randomness to ensure an unpredictable byte sequence.
|
||||
into B<buf>.
|
||||
|
||||
RAND_priv_bytes() has the same semantics as RAND_bytes(). It is intended to
|
||||
be used for generating long-term private keys. If using the default
|
||||
RAND_METHOD, this function uses a separate instance of the PRNG so that
|
||||
a compromise of the global generator will not affect such key generation.
|
||||
be used for generating values that should remain private. If using the
|
||||
default RAND_METHOD, this function uses a separate "private" PRNG
|
||||
instance so that a compromise of the "public" PRNG instance will not
|
||||
affect the secrecy of these private values, as described in L<RAND(7)>
|
||||
and L<RAND_DRBG(7)>.
|
||||
|
||||
=head1 NOTES
|
||||
|
||||
Always check the error return value of RAND_bytes() and
|
||||
RAND_priv_bytes() and do not take randomness for granted: an error occurs
|
||||
if the CSPRNG has not been seeded with enough randomness to ensure an
|
||||
unpredictable byte sequence.
|
||||
|
||||
=head1 RETURN VALUES
|
||||
|
||||
@@ -37,14 +45,26 @@ obtained by L<ERR_get_error(3)>.
|
||||
|
||||
=head1 HISTORY
|
||||
|
||||
=over 2
|
||||
|
||||
=item *
|
||||
|
||||
RAND_pseudo_bytes() was deprecated in OpenSSL 1.1.0; use RAND_bytes() instead.
|
||||
|
||||
=item *
|
||||
|
||||
RAND_priv_bytes() was added in OpenSSL 1.1.1.
|
||||
|
||||
=back
|
||||
|
||||
=head1 SEE ALSO
|
||||
|
||||
L<RAND_add(3)>,
|
||||
L<RAND_bytes(3)>,
|
||||
L<RAND_priv_bytes(3)>,
|
||||
L<ERR_get_error(3)>,
|
||||
L<RAND(7)>
|
||||
L<RAND(7)>,
|
||||
L<RAND_DRBG(7)>
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
|
||||
@@ -43,9 +43,9 @@ L<SSL_CTX_set_session_cache_mode(3)>).
|
||||
(SSL/TLS server only.)
|
||||
|
||||
SSL_CTX_sess_get_new_cb(), SSL_CTX_sess_get_remove_cb(), and
|
||||
SSL_CTX_sess_get_get_cb() allow to retrieve the function pointers of the
|
||||
provided callback functions. If a callback function has not been set,
|
||||
the NULL pointer is returned.
|
||||
SSL_CTX_sess_get_get_cb() retrieve the function pointers set by the
|
||||
corresponding set callback functions. If a callback function has not been
|
||||
set, the NULL pointer is returned.
|
||||
|
||||
=head1 NOTES
|
||||
|
||||
|
||||
@@ -34,10 +34,10 @@ argument I<arg> is specified by the application when setting I<callback>.
|
||||
I<callback> should return 1 to indicate verification success and 0 to
|
||||
indicate verification failure. If SSL_VERIFY_PEER is set and I<callback>
|
||||
returns 0, the handshake will fail. As the verification procedure may
|
||||
allow to continue the connection in case of failure (by always returning 1)
|
||||
the verification result must be set in any case using the B<error>
|
||||
member of I<x509_store_ctx> so that the calling application will be informed
|
||||
about the detailed result of the verification procedure!
|
||||
allow the connection to continue in the case of failure (by always
|
||||
returning 1) the verification result must be set in any case using the
|
||||
B<error> member of I<x509_store_ctx> so that the calling application
|
||||
will be informed about the detailed result of the verification procedure!
|
||||
|
||||
Within I<x509_store_ctx>, I<callback> has access to the I<verify_callback>
|
||||
function set using L<SSL_CTX_set_verify(3)>.
|
||||
|
||||
@@ -61,7 +61,7 @@ L<ssl(7)>, L<SSL_CIPHER_get_name(3)>
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
Copyright 2000-2016 The OpenSSL Project Authors. All Rights Reserved.
|
||||
Copyright 2000-2018 The OpenSSL Project Authors. All Rights Reserved.
|
||||
|
||||
Licensed under the OpenSSL license (the "License"). You may not use
|
||||
this file except in compliance with the License. You can obtain a copy
|
||||
|
||||
@@ -155,7 +155,7 @@ B<X509_CHECK_FLAG_NEVER_CHECK_SUBJECT> host flag, or because some DNS subject
|
||||
alternative names are present in the certificate, DNS name constraints in
|
||||
issuer certificates will not be applied to the subject DN.
|
||||
As described in X509_check_host(3) the B<X509_CHECK_FLAG_NEVER_CHECK_SUBJECT>
|
||||
flag takes precendence over the B<X509_CHECK_FLAG_ALWAYS_CHECK_SUBJECT> flag.
|
||||
flag takes precedence over the B<X509_CHECK_FLAG_ALWAYS_CHECK_SUBJECT> flag.
|
||||
|
||||
X509_VERIFY_PARAM_get_hostflags() returns any host flags previously set via a
|
||||
call to X509_VERIFY_PARAM_set_hostflags().
|
||||
|
||||
@@ -132,7 +132,7 @@ L<X509V3_get_d2i(3)>
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
Copyright 2015-2016 The OpenSSL Project Authors. All Rights Reserved.
|
||||
Copyright 2015-2018 The OpenSSL Project Authors. All Rights Reserved.
|
||||
|
||||
Licensed under the OpenSSL license (the "License"). You may not use
|
||||
this file except in compliance with the License. You can obtain a copy
|
||||
|
||||
+12
-9
@@ -24,16 +24,19 @@ to be initialized ('seeded') explicitly.
|
||||
It seeds and reseeds itself automatically using trusted random sources
|
||||
provided by the operating system.
|
||||
|
||||
As a normal application developer, you don't have to worry about any details,
|
||||
As a normal application developer, you do not have to worry about any details,
|
||||
just use L<RAND_bytes(3)> to obtain random data.
|
||||
Having said that, there is one important rule to obey: Always check the error
|
||||
return value of L<RAND_bytes(3)> and don't take randomness for granted.
|
||||
return value of L<RAND_bytes(3)> and do not take randomness for granted.
|
||||
|
||||
For long-term secrets, you can use L<RAND_priv_bytes(3)> instead.
|
||||
For values that should remain secret, you can use L<RAND_priv_bytes(3)>
|
||||
instead.
|
||||
This method does not provide 'better' randomness, it uses the same type of CSPRNG.
|
||||
The intention behind using a dedicated CSPRNG exclusively for long-term secrets is
|
||||
that none of its output should be visible to an attacker (e.g used as salt value),
|
||||
in order to reveal as little information as possible about its internal state.
|
||||
The intention behind using a dedicated CSPRNG exclusively for private
|
||||
values is that none of its output should be visible to an attacker (e.g.,
|
||||
used as salt value), in order to reveal as little information as
|
||||
possible about its internal state, and that a compromise of the "public"
|
||||
CSPRNG instance will not affect the secrecy of these private values.
|
||||
|
||||
In the rare case where the default implementation does not satisfy your special
|
||||
requirements, there are two options:
|
||||
@@ -61,10 +64,10 @@ of cryptographic principles and understand the implications of your changes.
|
||||
L<RAND_add(3)>,
|
||||
L<RAND_bytes(3)>,
|
||||
L<RAND_priv_bytes(3)>,
|
||||
L<RAND_get_rand_method(3)>
|
||||
L<RAND_set_rand_method(3)>
|
||||
L<RAND_get_rand_method(3)>,
|
||||
L<RAND_set_rand_method(3)>,
|
||||
L<RAND_OpenSSL(3)>,
|
||||
L<RAND_DRBG(7)>,
|
||||
L<RAND_DRBG(7)>
|
||||
|
||||
=head1 COPYRIGHT
|
||||
|
||||
|
||||
@@ -222,7 +222,7 @@ This is in fact done automatically by L<RAND_DRBG_bytes(3)>.
|
||||
|
||||
In most cases OpenSSL will automatically choose a suitable seed source
|
||||
for automatically seeding and reseeding its <master> DRBG. In some cases
|
||||
however, it will be necessary to explicitely specify a seed source during
|
||||
however, it will be necessary to explicitly specify a seed source during
|
||||
configuration, using the --with-rand-seed option. For more information,
|
||||
see the INSTALL instructions. There are also operating systems where no
|
||||
seed source is available and automatic reseeding is disabled by default.
|
||||
|
||||
Reference in New Issue
Block a user