Lines Matching refs:ciphersuite

824  * Fixed a bug where the RC4-MD5 ciphersuite incorrectly used the
843    the handshake when using this ciphersuite.
846    cannot decrypt data that has been encrypted using this ciphersuite - they can
850    the RC4-MD5 ciphersuite. This ciphersuite is not compiled by default in
852    ciphersuite list. This ciphersuite will never be used if TLSv1.3 has been
853    negotiated. In order for an OpenSSL 3.0 endpoint to use this ciphersuite the
862    3) The ciphersuite must have been explicitly added to the ciphersuite list
868    6) Both endpoints must negotiate the RC4-MD5 ciphersuite in preference to any
3236  * Separated TLSv1.3 ciphersuite configuration out from TLSv1.2 ciphersuite
3239    In order to avoid issues where legacy TLSv1.2 ciphersuite configuration
3692    During key agreement in a TLS handshake using a DH(E) based ciphersuite a
3906    this can cause OpenSSL to crash (dependant on ciphersuite). Both clients
4764    in 1.0.2 EXPORT was already removed and the only RC2 ciphersuite is also
5294    This parameter will be set to 1 or 0 depending on the ciphersuite selected
5477    During key agreement in a TLS handshake using a DH(E) based ciphersuite a
6150    reusing the private DH exponent or it's using a static DH ciphersuite.
6468    ciphersuite being selected and a zero length ClientKeyExchange message
6482    - A ciphersuite is used that does not require additional random data from
6747  * New function ssl_set_client_disabled to set a ciphersuite disabled
6749    hello and checking the requested ciphersuite.
6904  * Support for fixed DH ciphersuite client authentication: where both
7837    ciphersuite and sending carefully crafted handshake messages.
7880    dereference (read) by specifying an SRP ciphersuite even though it was not
8051  * Call OCSP Stapling callback after ciphersuite has been chosen, so
8832    ciphersuite and sending carefully crafted handshake messages.
8989  * Call OCSP Stapling callback after ciphersuite has been chosen, so
9174    and servers: an attacker can use it in a ciphersuite downgrade attack.
9622    ciphersuite support.
9648    the work each time a ciphersuite string requests enabling
9680  * Split the SSL/TLS algorithm mask (as used for ciphersuite string
9697    With the change, we also introduce new ciphersuite aliases that
9832    The temporary ciphersuite alias "ECCdraft" is no longer
10117  * New option -V for 'openssl ciphers'. This prints the ciphersuite code
10871    different requirements, clients could circumvent ciphersuite
10878    a ciphersuite string such as "DEFAULT:RSA" cannot enable
10947  * Since 0.9.8b, ciphersuite strings naming explicit ciphersuites
10951    have a single AES bit in the ciphersuite description bitmap.
10952    That change, however, also applied to ciphersuite strings such as
10958    ciphersuite selects this one ciphersuite, and any other similar
10959    ciphersuite (same bitmap) from *other* protocol versions.
10961    ciphersuite and the SSL 3.0/TLS 1.0 ciphersuite.
11798    the "ECCdraft" ciphersuite group alias can be used to select them.
12060    a ciphersuite string such as "DEFAULT:RSA" cannot enable
12120  * Change ciphersuite string processing so that an explicit
12121    ciphersuite selects this one ciphersuite (so that "AES256-SHA"
12123    ciphersuite (same bitmap) from *other* protocol versions (so that
12124    "RC4-MD5" will still include both the SSL 2.0 ciphersuite and the
12125    SSL 3.0/TLS 1.0 ciphersuite).  This is a backport combining
14037    not enabled by default and were not part of the "ALL" ciphersuite
14039    explicitly requested by specifying the "AESdraft" ciphersuite