| /third_party/curl/docs/libcurl/opts/ |
| D | CURLOPT_SSLVERSION.md | 16 CURLOPT_SSLVERSION - preferred TLS/SSL version
28 Pass a long as parameter to control which version range of SSL/TLS versions to
31 The SSL and TLS versions have typically developed from the most insecure
33 SSLv3, TLS v1.0, TLS v1.1, TLS v1.2 and the most recent TLS v1.3.
40 default TLS v1.0 since 7.39.0 (unless the TLS library has a stricter rule).
44 TLS v1.0 or later
56 TLS v1.0 or later (Added in 7.34.0)
60 TLS v1.1 or later (Added in 7.34.0)
64 TLS v1.2 or later (Added in 7.34.0)
68 TLS v1.3 or later (Added in 7.52.0)
[all …]
|
| D | CURLOPT_PROXY_SSLVERSION.md | 16 CURLOPT_PROXY_SSLVERSION - preferred HTTPS proxy TLS version
29 Pass a long as parameter to control which version of SSL/TLS to attempt to use
58 The maximum TLS version can be set by using *one* of the
65 The flag defines the maximum supported TLS version as TLSv1.2, or the default
71 The flag defines maximum supported TLS version as TLSv1.0.
76 The flag defines maximum supported TLS version as TLSv1.1.
81 The flag defines maximum supported TLS version as TLSv1.2.
86 The flag defines maximum supported TLS version as TLSv1.3.
90 documented to allow *only* the specified TLS version, but behavior was
91 inconsistent depending on the TLS library.
[all …]
|
| D | CURLOPT_TLSAUTH_TYPE.md | 14 CURLOPT_TLSAUTH_TYPE - TLS authentication methods
27 the method of the TLS authentication. Supported method is "SRP".
31 TLS-SRP authentication. Secure Remote Password authentication for TLS is
33 shared secret. To use TLS-SRP, you must also set the
40 TLS SRP does not work with TLS 1.3.
48 All TLS-based protocols
70 You need to build libcurl with GnuTLS or OpenSSL with TLS-SRP support for this
|
| /third_party/openssl/test/ssl-tests/ |
| D | 20-cert-select.cnf | 24 test-19 = 19-TLS 1.2 Ed25519 Client Auth
25 test-20 = 20-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 …]
|
| 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 …]
|
| 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
367 name => "TLS 1.2 Ed25519 Client Auth",
385 name => "TLS 1.2 Ed448 Client Auth",
444 # 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 …]
|
| /third_party/libcoap/man/ |
| D | coap_tls_library.txt.in | 25 - Work with CoAP TLS libraries
53 For specific (D)TLS library support, link with
57 *-lcoap-@LIBCOAP_API_VERSION@* to get the default (D)TLS library support.
62 specific TLS implementation type (e.g. https://www.openssl.org[OpenSSL],
64 https://www.trustedfirmware.org/projects/mbed-tls/[Mbed TLS],
67 the application needs to dynamically determine whether DTLS or TLS is
68 supported, what type of TLS implementation libcoap was compiled with, as well
69 as detect what is the version of the currently loaded TLS library is.
84 Due to the nature of TLS, there can be Callbacks that are invoked as the TLS
89 match the TLS implementation type.
[all …]
|
| /third_party/wpa_supplicant/wpa_supplicant-2.9/wpa_supplicant/ |
| 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 …]
|
| /third_party/wpa_supplicant/wpa_supplicant-2.9_standard/wpa_supplicant/ |
| 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 …]
|
| /third_party/mbedtls/ |
| D | SECURITY.md | 3 If you think you have found an Mbed TLS security vulnerability, then please
33 Mbed TLS aims to fully protect against remote attacks and to enable the user
36 being implemented. (For example Mbed TLS alone won't guarantee that the
37 messages will arrive without delay, as the TLS protocol doesn't guarantee that
47 machine. The attacker has insufficient privileges to directly access Mbed TLS
52 The attacker is able to observe the timing of instructions executed by Mbed TLS
53 by leveraging shared hardware that both Mbed TLS and the attacker have access
57 Mbed TLS provides limited protection against timing attacks. The cost of
59 the measurements and the noise present. Therefore the protection in Mbed TLS is
63 As attacks keep improving, so does Mbed TLS's protection. Mbed TLS is moving
[all …]
|
| D | BRANCHES.md | 5 - The [`master`](https://github.com/Mbed-TLS/mbedtls/tree/master) branch:
8 - The [`development`](https://github.com/Mbed-TLS/mbedtls/tree/development) branch:
9 this is where the current major version of Mbed TLS (version 3.x) is being
10 prepared. It has API changes that make it incompatible with Mbed TLS 2.x,
14 [`mbedtls-2.28`](https://github.com/Mbed-TLS/mbedtls/tree/mbedtls-2.28).
17 such as [`archive/mbedtls-2.7`](https://github.com/Mbed-TLS/mbedtls/tree/archive/mbedtls-2.7).
28 We maintain API compatibility in released versions of Mbed TLS. If you have
29 code that's working and secure with Mbed TLS x.y.z and does not rely on
42 Note that new releases of Mbed TLS may extend the API. Here are some
43 examples of changes that are common in minor releases of Mbed TLS, and are
[all …]
|
| /third_party/mbedtls/docs/architecture/ |
| D | tls13-support.md | 1 TLS 1.3 support
7 Mbed TLS provides a partial implementation of the TLS 1.3 protocol defined in
8 the "Support description" section below. The TLS 1.3 support enablement
11 The development of the TLS 1.3 protocol is based on the TLS 1.3 prototype
24 - Mbed TLS implements both the client and the server side of the TLS 1.3
27 - Mbed TLS supports ECDHE key establishment.
29 - Mbed TLS does not support DHE key establishment.
31 - Mbed TLS supports pre-shared keys for key establishment, pre-shared keys
34 - Mbed TLS supports session resumption via the ticket mechanism.
36 - Mbed TLS does not support sending or receiving early data (0-RTT data).
[all …]
|
| /third_party/curl/docs/cmdline-opts/ |
| D | tlsv1.3.md | 6 Protocols: TLS
19 Forces curl to use TLS version 1.3 or later when connecting to a remote TLS
22 If the connection is done without TLS, this option has no effect. This
25 Note that TLS 1.3 is not supported by all TLS backends.
|
| D | tlsv1.0.md | 6 Protocols: TLS
18 Forces curl to use TLS version 1.0 or later when connecting to a remote TLS server.
20 In old versions of curl this option was documented to allow _only_ TLS 1.0.
21 That behavior was inconsistent depending on the TLS library. Use --tls-max if
22 you want to set a maximum TLS version.
|
| D | tlsv1.2.md | 6 Protocols: TLS
19 Forces curl to use TLS version 1.2 or later when connecting to a remote TLS server.
21 In old versions of curl this option was documented to allow _only_ TLS 1.2.
22 That behavior was inconsistent depending on the TLS library. Use --tls-max if
23 you want to set a maximum TLS version.
|
| D | tlsv1.1.md | 6 Protocols: TLS
19 Forces curl to use TLS version 1.1 or later when connecting to a remote TLS server.
21 In old versions of curl this option was documented to allow _only_ TLS 1.1.
22 That behavior was inconsistent depending on the TLS library. Use --tls-max if
23 you want to set a maximum TLS version.
|
| D | tlsauthtype.md | 6 Help: TLS authentication type
7 Protocols: TLS
19 Set TLS authentication type. Currently, the only supported option is "SRP",
20 for TLS-SRP (RFC 5054). If --tlsuser and --tlspassword are specified but
22 only if the underlying libcurl is built with TLS-SRP support, which requires
23 OpenSSL or GnuTLS with TLS-SRP support.
|
| D | tls-max.md | 7 Protocols: TLS
9 Requires: TLS
10 Help: Set maximum allowed TLS version
25 VERSION defines maximum supported TLS version. The minimum acceptable version
28 If the connection is done without TLS, this option has no effect. This
32 Use up to recommended TLS version.
|
| D | ssl-reqd.md | 5 Help: Require SSL/TLS
19 Require SSL/TLS for the connection. Terminates the connection if the transfer
20 cannot be upgraded to use SSL/TLS.
23 OpenLDAP backend and rejected by the generic ldap backend if explicit TLS is
27 immediate and implicit use of TLS, like for FTPS, IMAPS, POP3S, SMTPS and
28 LDAPS. Such a transfer always fails if the TLS handshake does not work.
|
| /third_party/mbedtls/tests/git-scripts/ |
| D | README.md | 4 The git hooks are located in `<Mbed TLS root>/.git/hooks`, and as such are not under version control
7 …TLS git hooks are located in `<Mbed TLS root>/tests/git-scripts` directory, and one must create a …
11 Execute the following command to create a link on Linux from the Mbed TLS `.git/hooks` directory:
14 **Note: Currently the Mbed TLS git hooks work only on a GNU platform. If using a non-GNU platform, …
|
| /third_party/wpa_supplicant/wpa_supplicant-2.9_standard/hostapd/ |
| 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
|
| /third_party/wpa_supplicant/wpa_supplicant-2.9/hostapd/ |
| 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
|
| /third_party/mbedtls/docs/proposed/ |
| D | psa-driver-integration-guide.md | 1 Building Mbed TLS with PSA cryptoprocessor drivers
4 **This is a specification of work in progress. The implementation is not yet merged into Mbed TLS.**
6 This document describes how to build Mbed TLS with additional cryptoprocessor drivers that follow t…
8 The interface is not fully implemented in Mbed TLS yet and is disabled by default. You can enable t…
12 The PSA cryptography driver interface provides a way to build Mbed TLS with additional code that im…
14 …SA cryptography API (crypto functions beginning with `psa_`, and X.509 and TLS interfaces that ref…
18 ## How to build Mbed TLS with drivers
20 To build Mbed TLS with drivers:
|
| /third_party/curl/docs/ |
| D | CIPHERS.md | 7 users can control which ciphers to consider when negotiating TLS connections.
9 TLS 1.3 ciphers are supported since curl 7.61 for OpenSSL 1.1.1+, and since
14 . If you are using a different SSL backend you can try setting TLS 1.3 cipher
17 The names of the known ciphers differ depending on which TLS backend that
41 ### TLS v1.0 cipher suites
54 ### AES cipher suites from RFC 3268, extending TLS v1.0
69 ### SEED cipher suites from RFC 4162, extending TLS v1.0
78 ### GOST cipher suites, extending TLS v1.0
103 ### TLS v1.2 cipher suites
151 ### Camellia HMAC-Based cipher suites from RFC 6367, extending TLS v1.2
[all …]
|
| /third_party/skia/third_party/externals/swiftshader/third_party/llvm-10.0/llvm/lib/CodeGen/AsmPrinter/ |
| 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);
|