| /freebsd-12.1/contrib/wpa/wpa_supplicant/ |
| H A D | eap_testing.txt | 145 - EAP-TLS
149 - EAP-PEAPv0 / TLS
163 - EAP-TLS
165 - EAP-PEAPv0 / TLS
170 - EAP-TLS
194 - EAP-TLS
215 - EAP-TLS
249 - EAP-TLS
287 - EAP-TLS
312 - EAP-TLS
[all …]
|
| H A D | wpa_supplicant.conf | 1561 eap=TLS
1675 eap=TLS
1809 eap=TTLS PEAP TLS
1823 eap=TLS
|
| /freebsd-12.1/contrib/wpa/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
|
| H A D | hostapd.eap_user | 19 # EAP-TLS, EAP-PEAP, EAP-TTLS, EAP-FAST, EAP-SIM, and EAP-AKA do not use
27 # avoid having to configure every certificate for EAP-TLS authentication. The
61 "example user" TLS
72 "0"* AKA,TTLS,TLS,PEAP,SIM
73 "1"* SIM,TTLS,TLS,PEAP,AKA
74 "2"* AKA,TTLS,TLS,PEAP,SIM
75 "3"* SIM,TTLS,TLS,PEAP,AKA
76 "4"* AKA,TTLS,TLS,PEAP,SIM
77 "5"* SIM,TTLS,TLS,PEAP,AKA
83 * PEAP,TTLS,TLS,SIM,AKA
|
| /freebsd-12.1/contrib/llvm/lib/CodeGen/AsmPrinter/ |
| H A D | AddressPool.h | 27 bool TLS; member
29 AddressPoolEntry(unsigned Number, bool TLS) : Number(Number), TLS(TLS) {} in AddressPoolEntry()
44 unsigned getIndex(const MCSymbol *Sym, bool TLS = false);
|
| H A D | AddressPool.cpp | 20 unsigned AddressPool::getIndex(const MCSymbol *Sym, bool TLS) { in getIndex() argument
23 Pool.insert(std::make_pair(Sym, AddressPoolEntry(Pool.size(), TLS))); in getIndex()
64 I.second.TLS in emit()
|
| /freebsd-12.1/crypto/openssl/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_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
|
| H A D | SSL_connect.pod | 5 SSL_connect - initiate the TLS/SSL handshake with an TLS/SSL server
15 SSL_connect() initiates the TLS/SSL handshake with a server. The communication
61 The TLS/SSL handshake was not successful but was shut down controlled and
62 by the specifications of the TLS/SSL protocol. Call SSL_get_error() with the
67 The TLS/SSL handshake was successfully completed, a TLS/SSL connection has been
72 The TLS/SSL handshake was not successful, because a fatal error occurred either
|
| 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
94 The operation did not complete; the same TLS/SSL I/O function should be
107 The TLS/SSL I/O function should be called again later.
[all …]
|
| H A D | SSL_CTX_new.pod | 13 - create a new SSL_CTX object as framework for TLS/SSL or DTLS enabled
74 establish TLS/SSL or DTLS enabled connections. An B<SSL_CTX> object is
92 These are the general-purpose I<version-flexible> SSL/TLS methods.
110 A TLS/SSL connection established with these methods will only understand the
115 A TLS/SSL connection established with these methods will only understand the
120 A TLS/SSL connection established with these methods will only understand the
125 A TLS/SSL connection established with these methods will only understand the
161 allow newer protocols like TLS 1.0, TLS 1.1, TLS 1.2 or TLS 1.3.
|
| H A D | SSL_CIPHER_get_name.pod | 50 SSLv3 and TLS, it returns the TLS name.
54 it returns "(NONE)". Where both exist, B<stdname> should be the TLS name rather
60 SSL_CIPHER_get_version() returns string which indicates the SSL/TLS protocol
72 the SSL/TLS handshake when using the SSL_CIPHER B<c>. Note that this may be
77 If any appropriate key exchange algorithm can be used (as in the case of TLS 1.3
88 TLS 1.3 cipher suites) B<NID_auth_any> is returned. Examples (not comprehensive):
99 two-byte TLS cipher ID (as allocated by IANA) in network byte order. This parameter
100 is usually retrieved from a TLS packet by using functions like
107 SSL_CIPHER_get_protocol_id() returns the two-byte ID used in the TLS protocol of the given
180 SSL_CIPHER_get_protocol_id() returns a 2-byte integer representing the TLS
|
| H A D | SSL_get_peer_signature_nid.pod | 6 SSL_get_signature_nid, SSL_get_signature_type_nid - get TLS message signing
21 by the peer to sign TLS messages. It is implemented as a macro.
24 type used by the peer to sign TLS messages. Currently the signature type
37 uses RSA key exchange or is anonymous), the TLS version is below 1.2 or
|
| H A D | SSL_CTX_set_keylog_callback.pod | 6 SSL_CTX_keylog_cb_func - logging TLS key material
19 SSL_CTX_set_keylog_callback() sets the TLS key logging callback. This callback
20 is called whenever TLS key material is generated or received, in order to allow
23 SSL_CTX_get_keylog_callback() retrieves the previously set TLS key logging
|
| H A D | SSL_CTX_set_ssl_version.pod | 6 - choose a new TLS/SSL method
18 SSL_CTX_set_ssl_version() sets a new default TLS/SSL B<method> for SSL objects
23 SSL_set_ssl_method() sets a new TLS/SSL B<method> for a particular B<ssl>
26 SSL_get_ssl_method() returns a function pointer to the TLS/SSL method
|
| H A D | SSL_in_init.pod | 28 SSL_in_init() returns 1 if the SSL/TLS state machine is currently processing or
31 SSL_in_before() returns 1 if no SSL/TLS handshake has yet been initiated, or 0
34 SSL_is_init_finished() returns 1 if the SSL/TLS connection is in a state where
56 B<protocol> is one of TLS or DTLS. DTLS is used where a state is specific to the
57 DTLS protocol. Otherwise TLS is used.
|
| H A D | SSL_CTX_set_record_padding_callback.pod | 12 SSL_set_block_padding - install callback to specify TLS 1.3 record padding
34 for TLS 1.3 records. The value set in B<ctx> is copied to a new SSL by SSL_new().
48 The B<type> parameter is the TLS record type that is being processed; may be
75 These functions only apply to TLS 1.3 records being written.
85 The record padding API was added for TLS 1.3 support in OpenSSL 1.1.1.
|
| H A D | SSL_CTX_set_tlsext_ticket_key_cb.pod | 22 to TLS and there is no SSLv3 implementation.
24 The callback function I<cb> will be called for every client instigated TLS
25 session when session ticket extension is presented in the TLS hello
29 The OpenSSL library uses your callback function to help implement a common TLS
34 In order to reuse a session, a TLS client must send the a session ticket
37 ticket information or it starts a full TLS handshake to create a new session
93 the SSL/TLS session will continue by negotiating a set of cryptographic
94 parameters or using the alternate SSL/TLS resumption mechanism, session ids.
107 Session resumption shortcuts the TLS so that the client certificate
|
| H A D | SSL_set_session.pod | 5 SSL_set_session - set a TLS/SSL session to be used during TLS/SSL connect
15 SSL_set_session() sets B<session> to be used when the TLS/SSL connection
16 is to be established. SSL_set_session() is only useful for TLS/SSL clients.
|
| H A D | SSL_CTX_sess_number.pod | 29 SSL_CTX_sess_connect() returns the number of started SSL/TLS handshakes in
33 SSL/TLS sessions in client mode.
38 SSL_CTX_sess_accept() returns the number of started SSL/TLS handshakes in
42 SSL/TLS sessions in server mode.
|
| H A D | SSL_extension_supported.pod | 9 - custom TLS extension handling
72 SSL_CTX_add_custom_ext() adds a custom extension for a TLS/DTLS client or server
79 SSL_CTX_add_client_custom_ext() adds a custom extension for a TLS/DTLS client
88 SSL_CTX_add_server_custom_ext() adds a custom extension for a TLS/DTLS server
104 included in various TLS messages. The B<ext_type> parameter is set to the
116 If B<add_cb> returns -1 a fatal handshake error occurs using the TLS
146 The callback B<parse_cb> receives data for TLS extensions. The callback is only
162 using the TLS alert value specified in B<*al>.
178 The extension is only allowed in TLS
186 The extension is allowed in DTLS, but there is only a TLS implementation
[all …]
|
| /freebsd-12.1/crypto/openssl/ |
| H A D | NEWS | 76 o ARIA (including TLS support)
264 o TLS automatic EC curve selection.
267 o TLS Brainpool support.
333 o Fix renegotiation in TLS 1.1, 1.2 by using the correct TLS version.
358 o TLS/DTLS heartbeat support.
365 o Support TLS v1.2 and TLS v1.1.
432 o SSL/TLS GOST ciphersuite support.
493 o TLS Extensions support.
731 o SSL/TLS: add callback to retrieve SSL/TLS messages.
775 o Various SSL/TLS library bugfixes.
[all …]
|
| /freebsd-12.1/sys/contrib/libsodium/m4/ |
| H A D | ax_tls.m4 | 11 # Provides a test for the compiler support of thread local storage (TLS)
12 # extensions. Defines TLS if it is found. Currently knows about C++11,
50 AC_MSG_CHECKING([for thread local storage (TLS) class])
71 …[AC_DEFINE_UNQUOTED([TLS],[$ac_cv_tls],[If the compiler supports a TLS storage class define it to …
|