/freebsd/crypto/openssl/util/perl/TLSProxy/ |
H A D | ServerHello.pm | 51 $self->{ciphersuite} = 0; 74 my $ciphersuite = unpack('n', substr($self->data, $ptr)); 125 $self->ciphersuite($ciphersuite); 126 TLSProxy::Proxy->ciphersuite($ciphersuite); 135 print " Ciphersuite:".$ciphersuite."\n"; 145 TLSProxy::Message->ciphersuite($self->ciphersuite); 159 $data .= pack('n', $self->ciphersuite); 212 sub ciphersuite subroutine 216 $self->{ciphersuite} = shift; 218 return $self->{ciphersuite};
|
H A D | Proxy.pm | 78 my $ciphersuite = undef; 198 $ciphersuite = undef; 827 sub ciphersuite subroutine 831 $ciphersuite = shift; 833 return $ciphersuite;
|
H A D | ServerKeyExchange.pm | 56 return if TLSProxy::Proxy->ciphersuite() 58 && TLSProxy::Proxy->ciphersuite()
|
H A D | Message.pm | 158 my $ciphersuite = 0; 553 sub ciphersuite subroutine 557 $ciphersuite = shift; 559 return $ciphersuite;
|
/freebsd/crypto/openssl/doc/man3/ |
H A D | SSL_CTX_set_psk_client_callback.pod | 49 case the server will have specified a ciphersuite to use already and the PSK 50 must be compatible with the digest for that ciphersuite. The digest will be 69 =item A ciphersuite 71 Only the handshake digest associated with the ciphersuite is relevant for the 72 PSK (the server may go on to negotiate any ciphersuite which is compatible with 73 the digest). The application can use any TLSv1.3 ciphersuite. If B<md> is 74 not NULL the handshake digest for the ciphersuite should be the same. 75 The ciphersuite can be set via a call to <SSL_SESSION_set_cipher(3)>. The
|
H A D | SSL_CTX_set_cipher_list.pod | 39 ciphersuite names in order of preference. Valid TLSv1.3 ciphersuite names are: 111 ciphersuite list was configured, and 0 otherwise.
|
H A D | SSL_set_session_secret_cb.pod | 37 ciphersuite by setting it in I<*cipher>. 41 the B<SSL_SESSION> - but it does not affect the ciphersuite selected by the
|
H A D | SSL_SESSION_get0_cipher.pod | 24 SSL_SESSION_set_cipher() can be used to set the ciphersuite associated with the
|
H A D | SSL_CIPHER_get_name.pod | 127 The minimum protocol version that the ciphersuite supports, such as B<TLSv1.2>. 129 ciphersuite was first defined because some ciphersuites are backwards compatible
|
H A D | SSL_get_client_random.pod | 45 suitable for the ciphersuite associated with the SSL_SESSION.
|
H A D | SSL_get_ciphers.pod | 72 a ciphersuite is available (i.e. it is configured in the cipher list) and shared
|
H A D | SSL_CTX_use_psk_identity_hint.pod | 50 the ciphersuite and the protocol version. See
|
H A D | SSL_CONF_cmd.pod | 235 Sets the TLSv1.2 and below ciphersuite list to B<ciphers>. This list will be 243 colon-separated list of TLSv1.3 ciphersuite names in order of preference. This 347 Sets the ciphersuite list for TLSv1.2 and below to B<value>. This list will be 355 colon-separated list of TLSv1.3 ciphersuite names in order of preference. This
|
H A D | SSL_CTX_set_options.pod | 69 when GOST ciphersuite is negotiated. Required for interoperability with CryptoPro
|
/freebsd/crypto/openssl/test/recipes/ |
H A D | 70-test_renegotiation.t | 195 my @ciphersuite = (0x002f); 196 $message->ciphersuites(\@ciphersuite);
|
H A D | 70-test_tls13hrr.t | 130 $hrr->ciphersuite(TLSProxy::Message::CIPHER_TLS13_AES_256_GCM_SHA384);
|
/freebsd/contrib/wpa/src/eap_common/ |
H A D | eap_pwd_common.h | 66 const u32 *ciphersuite, u8 *msk, u8 *emsk, u8 *session_id);
|
H A D | eap_pwd_common.c | 334 const u32 *ciphersuite, u8 *msk, u8 *emsk, u8 *session_id) in compute_keys() argument 358 eap_pwd_h_update(hash, (const u8 *) ciphersuite, sizeof(u32)); in compute_keys()
|
/freebsd/crypto/openssl/test/ssl-tests/ |
H A D | 14-curves.cnf.in | 186 #ciphersuite
|
H A D | 02-protocol-version.cnf | 681 test-676 = 676-ciphersuite-sanity-check-client 682 test-677 = 677-ciphersuite-sanity-check-server 18775 [676-ciphersuite-sanity-check-client] 18776 ssl_conf = 676-ciphersuite-sanity-check-client-ssl 18778 [676-ciphersuite-sanity-check-client-ssl] 18779 server = 676-ciphersuite-sanity-check-client-server 18780 client = 676-ciphersuite-sanity-check-client-client 18782 [676-ciphersuite-sanity-check-client-server] 18788 [676-ciphersuite-sanity-check-client-client] 18800 [677-ciphersuite-sanity-check-server] [all …]
|
/freebsd/crypto/openssl/doc/man7/ |
H A D | ossl-guide-libssl-introduction.pod | 87 ciphersuite. Such a set is represented by an B<SSL_CIPHER> object.
|
/freebsd/crypto/openssl/ |
H A D | NEWS.md | 412 * Support for using the IANA standard names in TLS ciphersuite configuration 533 * Fixed a bug where the RC4-MD5 ciphersuite incorrectly used the 851 * Kerberos ciphersuite support removed 1372 * SSL/TLS GOST ciphersuite support. 1374 * RFC4279 PSK ciphersuite support. 1440 * Various ciphersuite selection fixes. 1447 * Changes to ciphersuite selection algorithm 1546 * Various ciphersuite selection fixes. 1596 * Security: Fix Kerberos ciphersuite SSL/TLS handshaking bug
|
H A D | CHANGES.md | 2090 * Fixed a bug where the RC4-MD5 ciphersuite incorrectly used the 2109 the handshake when using this ciphersuite. 2112 cannot decrypt data that has been encrypted using this ciphersuite - they can 2116 the RC4-MD5 ciphersuite. This ciphersuite is not compiled by default in 2118 ciphersuite list. This ciphersuite will never be used if TLSv1.3 has been 2119 negotiated. In order for an OpenSSL 3.0 endpoint to use this ciphersuite the 2128 3) The ciphersuite must have been explicitly added to the ciphersuite list 2134 6) Both endpoints must negotiate the RC4-MD5 ciphersuite in preference to any 4505 * Separated TLSv1.3 ciphersuite configuration out from TLSv1.2 ciphersuite 4508 In order to avoid issues where legacy TLSv1.2 ciphersuite configuration [all …]
|
/freebsd/crypto/openssl/doc/man1/ |
H A D | openssl-s_time.pod.in | 112 simple colon (":") separated list of TLSv1.3 ciphersuite names.
|
/freebsd/crypto/openssl/doc/designs/quic-design/ |
H A D | quic-api-ssl-funcs.md | 839 layer has not negotiated a ciphersuite so it has no “current” cipher. We could 847 ciphersuite has been negotiated and NULL can be used to infer that Initial
|