/netbsd-src/crypto/external/bsd/openssl.old/dist/test/ssl-tests/ |
H A D | 20-cert-select.conf | 37 test-32 = 32-TLS 1.2 Ed25519 Client Auth 38 test-33 = 33-TLS 1.2 Ed448 Client Auth 39 test-34 = 34-Only RSA-PSS Certificate, TLS v1.1 40 test-35 = 35-TLS 1.3 ECDSA Signature Algorithm Selection 41 test-36 = 36-TLS 1.3 ECDSA Signature Algorithm Selection compressed point 42 test-37 = 37-TLS 1.3 ECDSA Signature Algorithm Selection SHA1 43 test-38 = 38-TLS 1.3 ECDSA Signature Algorithm Selection with PSS 44 test-39 = 39-TLS 1.3 RSA Signature Algorithm Selection SHA384 with PSS 45 test-40 = 40-TLS 1.3 ECDSA Signature Algorithm Selection, no ECDSA certificate 46 test-41 = 41-TLS 1.3 RSA Signature Algorithm Selection, no PSS [all …]
|
H A D | 17-renegotiate.conf.in | 27 "Method" => "TLS", 40 "Method" => "TLS", 54 "Method" => "TLS", 67 "Method" => "TLS", 86 "Method" => "TLS", 105 "Method" => "TLS", 126 "Method" => "TLS", 145 "Method" => "TLS", 164 "Method" => "TLS", 183 "Method" => "TLS", [all …]
|
H A D | 20-cert-select.conf.in | 64 # Note: certificate_authorities not sent for TLS < 1.3 88 # Note: certificate_authorities not sent for TLS < 1.3 125 # Note: certificate_authorities not sent for TLS < 1.3 143 # Note: certificate_authorities not sent for TLS < 1.3 165 # Note: certificate_authorities not sent for TLS < 1.3 522 name => "TLS 1.2 Ed25519 Client Auth", 540 name => "TLS 1.2 Ed448 Client Auth", 561 name => "Only RSA-PSS Certificate, TLS v1.1", 609 name => "TLS 1.3 ECDSA Signature Algorithm Selection", 623 name => "TLS 1.3 ECDSA Signature Algorithm Selection compressed point", [all …]
|
/netbsd-src/crypto/external/bsd/openssl/dist/test/ssl-tests/ |
H A D | 20-cert-select.cnf | 22 test-17 = 17-TLS 1.2 Ed25519 Client Auth 23 test-18 = 18-TLS 1.2 Ed448 Client Auth 39 test-34 = 34-Only RSA-PSS Certificate, TLS v1.1 40 test-35 = 35-TLS 1.3 ECDSA Signature Algorithm Selection 41 test-36 = 36-TLS 1.3 ECDSA Signature Algorithm Selection compressed point 42 test-37 = 37-TLS 1.3 ECDSA Signature Algorithm Selection SHA1 43 test-38 = 38-TLS 1.3 ECDSA Signature Algorithm Selection with PSS 44 test-39 = 39-TLS 1.3 RSA Signature Algorithm Selection SHA384 with PSS 45 test-40 = 40-TLS 1.3 ECDSA Signature Algorithm Selection, no ECDSA certificate 46 test-41 = 41-TLS 1.3 RSA Signature Algorithm Selection, no PSS [all …]
|
H A D | 17-renegotiate.cnf.in | 27 "Method" => "TLS", 40 "Method" => "TLS", 54 "Method" => "TLS", 67 "Method" => "TLS", 86 "Method" => "TLS", 105 "Method" => "TLS", 122 "Method" => "TLS", 143 "Method" => "TLS", 162 "Method" => "TLS", 181 "Method" => "TLS", [all …]
|
H A D | 20-cert-select.cnf.in | 75 # Note: certificate_authorities not sent for TLS < 1.3 99 # Note: certificate_authorities not sent for TLS < 1.3 308 # Note: certificate_authorities not sent for TLS < 1.3 326 # Note: certificate_authorities not sent for TLS < 1.3 332 name => "TLS 1.2 Ed25519 Client Auth", 350 name => "TLS 1.2 Ed448 Client Auth", 409 # Note: certificate_authorities not sent for TLS < 1.3 587 name => "Only RSA-PSS Certificate, TLS v1.1", 635 name => "TLS 1.3 ECDSA Signature Algorithm Selection", 649 name => "TLS 1.3 ECDSA Signature Algorithm Selection compressed point", [all …]
|
H A D | 17-renegotiate.cnf | 47 Method = TLS 74 Method = TLS 102 Method = TLS 129 Method = TLS 161 Method = TLS 193 Method = TLS 221 Method = TLS 249 Method = TLS 281 Method = TLS 313 Method = TLS [all …]
|
/netbsd-src/external/bsd/wpa/dist/wpa_supplicant/ |
H A D | eap_testing.txt | 56 EAP-TLS + + + + + + + + - - + + 61 EAP-PEAPv0/TLS + + - + + + F + - - + + 72 EAP-PEAPv1/TLS - - - + + +1 F +5 - - + + 87 EAP-TTLS/EAP-TLS + - +2 + F + + + - - + - 107 EAP-FAST/TLS(aprov) - - - - - - - - - - + + 112 EAP-FAST/TLS(auth) - - - - - - - - - - + + 145 - EAP-TLS 149 - EAP-PEAPv0 / TLS 153 - EAP-TTLS / EAP-TLS 163 - EAP-TLS [all …]
|
/netbsd-src/crypto/external/bsd/libsaslc/dist/ref/ |
H A D | rfc2595.txt | 12 Using TLS with IMAP, POP3 and ACAP 29 The TLS protocol (formerly known as SSL) provides a way to secure an 34 version of this service, TLS is complimentary to simple 44 desire simple password authentication in combination with TLS 52 used for this purpose, TLS provides an additional tool with different 53 deployability characteristics. A server supporting both TLS with 60 RFC 2595 Using TLS with IMAP, POP3 and ACAP June 1999 93 Implementation of the TLS_DHE_DSS_WITH_3DES_EDE_CBC_SHA [TLS] cipher 103 layer (such as that provided by TLS) occurs prior to or at the time 116 RFC 2595 Using TLS with IMAP, POP3 and ACAP June 1999 [all …]
|
/netbsd-src/external/bsd/wpa/dist/hostapd/ |
H A D | eap_testing.txt | 21 EAP-TLS + + +1 + + 25 EAP-PEAPv0/TLS + F - + + 35 EAP-PEAPv1/TLS + F - - + 49 EAP-TTLS/EAP-TLS + F - - - 63 EAP-FAST/TLS(aprov) + - - - - 68 EAP-FAST/TLS(auth) + - - - - 75 1) EAP-TLS itself worked, but peer certificate validation failed at 76 least when using the internal TLS server (peer included incorrect
|
/netbsd-src/libexec/ld.elf_so/ |
H A D | README.TLS | 7 (a) static thread-local storage for the TLS data of initial objects, 11 (b) a pointer to a dynamic thread vector (DTV) for the TLS data 24 TP enable twice the range of static TLS offsets when biased like this. 33 Each architecture has one of two TLS variants, variant I or variant II. 86 See [ELFTLS] Sec. 3 `Run-Time Handling of TLS', Figs 1 and 2, for 87 bigger pictures including the DTV and dynamically allocated TLS blocks. 90 the architecture-specific relocations and TLS details. 99 Steps for adding TLS support for a new platform: 101 (1) Declare TLS variant in machine/types.h by defining either 128 TLS offse [all...] |
/netbsd-src/external/apache2/llvm/dist/llvm/lib/CodeGen/AsmPrinter/ |
H A D | AddressPool.h | 26 bool TLS; member 28 AddressPoolEntry(unsigned Number, bool TLS) : Number(Number), TLS(TLS) {} in AddressPoolEntry() 43 unsigned getIndex(const MCSymbol *Sym, bool TLS = false);
|
/netbsd-src/crypto/external/bsd/openssl/dist/doc/man7/ |
H A D | EVP_KDF-TLS13_KDF.pod | 5 EVP_KDF-TLS13_KDF - The TLS 1.3 EVP_KDF implementation 9 Support for computing the TLS 1.3 version of the B<HKDF> KDF through 13 as used by TLS 1.3. 38 This parameter sets the label prefix on the specified TLS 1.3 KDF context. 39 For TLS 1.3 this should be set to the ASCII string "tls13 " without a 44 This parameter sets the label on the specified TLS 1.3 KDF context. 49 This parameter sets the context data on the specified TLS 1.3 KDF context. 54 This parameter sets the mode for the TLS 1.3 KDF operation. 84 This KDF is intended for use by the TLS 1.3 implementation in libssl. 91 A context for a TLS 1.3 KDF can be obtained by calling: [all …]
|
H A D | ssl.pod | 5 ssl - OpenSSL SSL/TLS library 20 TLS/SSL enabled connections (see L<SSL_CTX_new(3)>). 30 When the TLS/SSL handshake is performed using 34 used to read and write data on the TLS/SSL connection. 36 TLS/SSL connection. 53 are a core part of the SSL/TLS protocol. The available ciphers are configured 65 This is a structure containing the current TLS/SSL session details for a 70 This is the main SSL/TLS structure which is created by a server or client per 86 This is the common header file for the SSL/TLS API. Include it into your
|
H A D | EVP_KDF-TLS1_PRF.pod | 11 The EVP_KDF-TLS1_PRF algorithm implements the PRF used by TLS versions up to 12 and including TLS 1.2. 32 associated with the TLS PRF. 34 PRF algorithm using both B<MD5> and B<SHA1> as used in TLS 1.0 and 1.1. 38 This parameter sets the secret value of the TLS PRF. 45 this should be more than enough for any normal use of the TLS PRF. 51 A context for the TLS PRF can be obtained by calling:
|
/netbsd-src/crypto/external/bsd/openssl/dist/doc/man3/ |
H A D | EVP_PKEY_CTX_set_tls1_prf_md.pod | 7 TLS PRF key derivation algorithm 22 TLS. It has no associated private key and only implements key derivation 26 TLS PRF. EVP_md5_sha1() is treated as a special case which uses the PRF 27 algorithm using both B<MD5> and B<SHA1> as used in TLS 1.0 and 1.1. 29 EVP_PKEY_CTX_set_tls1_prf_secret() sets the secret value of the TLS PRF 38 The TLS PRF also supports string based control operations using 49 A context for the TLS PRF can be obtained by calling: 57 be more than enough for any normal use of the TLS PRF. 61 the buffer to B<NULL> is not meaningful for the TLS PRF. 63 Optimised versions of the TLS PRF can be implemented in an ENGINE.
|
H A D | SSL_accept.pod | 5 SSL_accept - wait for a TLS/SSL client to initiate a TLS/SSL handshake 15 SSL_accept() waits for a TLS/SSL client to initiate the TLS/SSL handshake. 46 The TLS/SSL handshake was not successful but was shut down controlled and 47 by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the 52 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been 57 The TLS/SSL handshake was not successful because a fatal error occurred either
|
H A D | SSL_get_client_random.pod | 9 - get internal TLS/SSL random values and get/set master key 25 to the server during the initial SSL/TLS handshake. It copies as many 33 sent from the server to the client during the initial SSL/TLS handshake. 36 secret used to guarantee the security of the SSL/TLS session. This one 51 These functions expose internal values from the TLS handshake, for 58 were already generated and used in the TLS protocol. Using them 61 The security of your TLS session depends on keeping the master key secret: 67 In current versions of the TLS protocols, the length of client_random 70 in case of the unlikely event that a future version or variant of TLS 74 "random", many TLS implementations will generate four bytes of those
|
H A D | SSL_do_handshake.pod | 5 SSL_do_handshake - perform a TLS/SSL handshake 15 SSL_do_handshake() will wait for a SSL/TLS handshake to take place. If the 47 The TLS/SSL handshake was not successful but was shut down controlled and 48 by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the 53 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been 58 The TLS/SSL handshake was not successful because a fatal error occurred either
|
/netbsd-src/crypto/external/bsd/openssl.old/dist/doc/man3/ |
H A D | EVP_PKEY_CTX_set_tls1_prf_md.pod | 7 TLS PRF key derivation algorithm 22 TLS. It has no associated private key and only implements key derivation 26 TLS PRF. EVP_md5_sha1() is treated as a special case which uses the PRF 27 algorithm using both B<MD5> and B<SHA1> as used in TLS 1.0 and 1.1. 29 EVP_PKEY_CTX_set_tls1_prf_secret() sets the secret value of the TLS PRF 38 The TLS PRF also supports string based control operations using 51 A context for the TLS PRF can be obtained by calling: 59 be more than enough for any normal use of the TLS PRF. 63 the buffer to B<NULL> is not meaningful for the TLS PRF. 65 Optimised versions of the TLS PRF can be implemented in an ENGINE.
|
H A D | SSL_accept.pod | 5 SSL_accept - wait for a TLS/SSL client to initiate a TLS/SSL handshake 15 SSL_accept() waits for a TLS/SSL client to initiate the TLS/SSL handshake. 46 The TLS/SSL handshake was not successful but was shut down controlled and 47 by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the 52 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been 57 The TLS/SSL handshake was not successful because a fatal error occurred either
|
H A D | SSL_get_client_random.pod | 9 - get internal TLS/SSL random values and get/set master key 25 to the server during the initial SSL/TLS handshake. It copies as many 33 sent from the server to the client during the initial SSL/TLS handshake. 36 secret used to guarantee the security of the SSL/TLS session. This one 51 These functions expose internal values from the TLS handshake, for 58 were already generated and used in the TLS protocol. Using them 61 The security of your TLS session depends on keeping the master key secret: 67 In current versions of the TLS protocols, the length of client_random 70 in case of the unlikely event that a future version or variant of TLS 74 "random", many TLS implementations will generate four bytes of those
|
H A D | SSL_get_error.pod | 5 SSL_get_error - obtain result code for TLS/SSL I/O operation 18 SSL_write_ex() or SSL_write() on B<ssl>. The value returned by that TLS/SSL I/O 23 used in the same thread that performed the TLS/SSL I/O operation, and no 25 thread's error queue must be empty before the TLS/SSL I/O operation is 36 The TLS/SSL I/O operation completed. This result code is returned 41 The TLS/SSL peer has closed the connection for writing by sending the 80 TLS/SSL I/O function should be retried. 82 Caveat: Any TLS/SSL I/O function can lead to either of 88 TLS/SSL handshakes may occur at any time during the protocol (initiated by 94 The operation did not complete; the same TLS/SSL I/O function should be [all …]
|
H A D | SSL_do_handshake.pod | 5 SSL_do_handshake - perform a TLS/SSL handshake 15 SSL_do_handshake() will wait for a SSL/TLS handshake to take place. If the 47 The TLS/SSL handshake was not successful but was shut down controlled and 48 by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the 53 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been 58 The TLS/SSL handshake was not successful because a fatal error occurred either
|
/netbsd-src/external/ibm-public/postfix/dist/ |
H A D | TLS_TODO | 3 * Code cleanup: split smtp_session.c into generic SMTP, legacy TLS, 4 and current TLS. The amount of TLS code now dominates the file. 8 * Code cleanup: TLS_LEV_NOTFOUND no longer belongs in the TLS 18 so Postfix/TLS should support loading CRLs. 23 * Move TLS based information from separate lines into Postfix's smtpd
|