/openssl/test/ssl-tests/ |
H A D | 09-alpn.cnf | 9 test-4 = 4-alpn-no-server-support 10 test-5 = 5-alpn-no-client-support 150 [4-alpn-no-server-support] 151 ssl_conf = 4-alpn-no-server-support-ssl 153 [4-alpn-no-server-support-ssl] 157 [4-alpn-no-server-support-server] 162 [4-alpn-no-server-support-client] 176 [5-alpn-no-client-support] 179 [5-alpn-no-client-support-ssl] 183 [5-alpn-no-client-support-server] [all …]
|
H A D | 08-npn.cnf | 9 test-4 = 4-npn-no-server-support 10 test-5 = 5-npn-no-client-support 157 [4-npn-no-server-support] 158 ssl_conf = 4-npn-no-server-support-ssl 160 [4-npn-no-server-support-ssl] 164 [4-npn-no-server-support-server] 169 [4-npn-no-server-support-client] 184 [5-npn-no-client-support] 187 [5-npn-no-client-support-ssl] 191 [5-npn-no-client-support-server] [all …]
|
H A D | 05-sni.cnf | 7 test-2 = 2-SNI-no-server-support 8 test-3 = 3-SNI-no-client-support 84 [2-SNI-no-server-support] 85 ssl_conf = 2-SNI-no-server-support-ssl 87 [2-SNI-no-server-support-ssl] 91 [2-SNI-no-server-support-server] 96 [2-SNI-no-server-support-client] 111 [3-SNI-no-client-support] 114 [3-SNI-no-client-support-ssl] 119 [3-SNI-no-client-support-server] [all …]
|
H A D | 09-alpn.cnf.in | 85 name => "alpn-no-server-support", 97 name => "alpn-no-client-support", 180 name => "alpn-selected-sni-server-does-not-support-alpn", 287 name => "alpn-no-server-support-resumption", 306 name => "alpn-no-client-support-resumption",
|
H A D | 06-sni-ticket.cnf.in | 61 # If the client has session tickets disabled, then No support 62 # If the server initial_ctx has session tickets disabled, then No support 64 # then No support
|
H A D | 08-npn.cnf.in | 87 name => "npn-no-server-support", 100 name => "npn-no-client-support", 223 name => "npn-selected-sni-server-does-not-support-npn", 383 name => "npn-no-server-support-resumption", 403 name => "npn-no-client-support-resumption",
|
/openssl/crypto/thread/ |
H A D | api.c | 16 int support = 0; in OSSL_get_thread_support_flags() local 19 support |= OSSL_THREAD_SUPPORT_FLAG_THREAD_POOL; in OSSL_get_thread_support_flags() 22 support |= OSSL_THREAD_SUPPORT_FLAG_DEFAULT_SPAWN; in OSSL_get_thread_support_flags() 25 return support; in OSSL_get_thread_support_flags()
|
/openssl/ |
H A D | NEWS.md | 780 * SSLv2 support removed 806 * HKDF support. 963 * TLS Brainpool support. 964 * ALPN support. 1138 * SCTP support. 1146 * SRP support. 1359 * Add gcc 4.2 support. 1365 * RFC4507bis support. 1371 * RFC3779 support. 1764 * EGD support [all …]
|
H A D | README-ENGINES.md | 14 users who need to maintain or support existing ENGINE implementations. 35 1. Integration of EVP support. 36 2. Configuration support. 39 Integration of EVP support 42 With respect to EVP, this relates to support for ciphers and digests in 47 Configuration support 50 Configuration support currently exists in the ENGINE API itself, in the 85 guarantees) have experience in using the ENGINE support to drive their 114 The recommended way of doing this is for the application to support 216 Applications that support the ENGINE API and more specifically, the [all …]
|
H A D | INSTALL.md | 587 Build with Kernel TLS support. 629 Do not build support for async operations. 727 Don't build support for SSL/TLS compression. 751 Don't build support for datagram based BIOs. 778 Don't build support for Elliptic Curves. 782 Don't build support for binary Elliptic Curves 803 Don't build support for loading engines. 863 Disable HTTP support. 970 Don't build support for socket BIOs. 1027 Don't build with QUIC support. [all …]
|
/openssl/doc/designs/quic-design/ |
H A D | dgram-api.md | 5 eventual BIO_dgram_mem) to support APIs which allow multiple datagrams to be 23 on OSes which do not support `sendmmsg` or `sendmsg`. 61 - We do not support iovecs. The motivations for this are: 63 - Not all platforms can support iovecs (e.g. Windows). 78 - Even if we did support iovecs, we would have to impose a limit 157 Local address support is enabled as follows: 167 fails if support is not available. 211 - If we choose to support these functions when OS support is not available 267 - Not providing these functions on OSes that don't support 392 - Flexible support for single-copy (zero-copy). [all …]
|
/openssl/providers/implementations/ciphers/ |
H A D | cipher_aes_gcm_hw_rv64i.inc | 11 * RISC-V 64 support for AES GCM. 16 * RISC-V 64 ZKND and ZKNE support for AES GCM. 38 * RISC-V RV64 ZVKNED support for AES GCM. 71 * RISC-V RV64 ZVKB, ZVKG and ZVKNED support for AES GCM.
|
H A D | cipher_aes_ccm_hw_rv64i.inc | 11 * RISC-V 64 ZKND ZKNE support for AES CCM. 35 * RISC-V RV64 ZVKNED support for AES CCM.
|
/openssl/doc/man3/ |
H A D | BIO_sendmmsg.pod | 73 of received datagrams to be determined. Unlike I<peer>, support for I<local> 76 support for I<local> has not been enabled, processing of that B<BIO_MSG> fails. 89 before local address support was enabled for a receiving socket. These are 90 OS-specific limitations. As such, users of this API using local address support 105 Unlike most BIO functions, these functions explicitly support multi-threaded 111 The support for concurrent use extends to BIO_sendmmsg() and BIO_recvmmsg() 116 whether local address support is enabled. To enable local address support, call 118 local address support is not available for the platform. 163 The I<peer> field was set to a non-NULL value, but peer address support is not 204 BIO_dgram_set_local_addr_enable() returns 1 if local address support was [all …]
|
H A D | EVP_PKEY_CTX_set1_pbe_pass.pod | 6 - generic KDF support functions 17 These functions are generic support functions for all KDF algorithms. 32 There is also support for string based control operations via
|
H A D | CRYPTO_THREAD_run_once.pod | 12 OSSL_THREAD_SUPPORT_FLAG_DEFAULT_SPAWN - OpenSSL thread support 48 support for the underlying OS threading API is built-in. Currently, OpenSSL 50 any multi-threading support, for example on platforms that don't provide 51 any threading support or that provide a threading API that is not yet 162 OpenSSL is compiled with and is able to support in the current run time 183 necessary support). 207 You can find out if OpenSSL was configured with thread support: 211 /* thread support enabled */ 213 /* no thread support */
|
H A D | OPENSSL_ia32cap.pod | 30 =item bit #23 denoting MMX support; 34 =item bit #25 denoting SSE support; 36 =item bit #26 denoting SSE2 support; 45 =item bit #41 denoting SSSE3, Supplemental SSE3, support; 47 =item bit #43 denoting AMD XOP support (forced to zero on non-AMD CPUs);
|
/openssl/doc/designs/ |
H A D | thread-api.md | 4 OpenSSL wishes to support the internal use of threads for purposes of 12 To support this end, OpenSSL can manage an internal thread pool. Tasks can be 40 * support). 60 support. 64 * Retrieves flags indicating what threading functionality OpenSSL can support 102 to support this functionality, however there is no intention of making
|
H A D | passing-algorithmidentifier-parameters.md | 7 We currently only support passing the AlgorithmIdentifier (`X509_ALGOR`) 9 only support getting full AlgorithmIdentifier (`X509_ALGOR`) from signature 12 We do support passing them to legacy implementations of other types of 27 This is currently only specified for `EVP_CIPHER`, in support of 113 will have to implement support for passing AlgorithmIdentifier parameter 121 current provider functionality doesn't support passing AlgorithmIdentifier 142 - For asymmetric key operations, PKCS#7 and CMS support was added as 145 With providers, some of that support was retained, but not others. Most 173 Some of it can be claimed to already have support in OpenSSL. However, this
|
H A D | fetching-composite-algorithms.md | 7 We currently support - at least in the public libcrypto API - explicitly 12 However, there is one class of algorithms where the support for *using* 139 As a matter of fact, we already have built-in support for fetching 141 that support, and *most of the time*, we also have public APIs to use the 142 fetched result, commonly known as support for explicit fetching. 172 There are some classes of algorithms for which we have no support for using 178 support implicit fetching.
|
/openssl/engines/ |
H A D | e_afalg.txt | 13 AFALG_R_KERNEL_DOES_NOT_SUPPORT_AFALG:101:kernel does not support afalg 15 kernel does not support async afalg
|
/openssl/doc/man7/ |
H A D | EVP_ASYM_CIPHER-SM2.pod | 6 - SM2 Asymmetric Cipher algorithm support 10 Asymmetric Cipher support for the B<SM2> key type.
|
H A D | EVP_PKEY-X25519.pod | 7 - EVP_PKEY X25519, X448, ED25519 and ED448 keytype and algorithm support 13 support the associated key, containing the public key I<pub> and the 41 In addition to the common parameters that all keytypes should support (see 43 support the following.
|
H A D | EVP_KEYEXCH-X25519.pod | 7 - X25519 and X448 Key Exchange algorithm support 11 Key exchange support for the B<X25519> and B<X448> key types.
|
/openssl/doc/internal/man3/ |
H A D | ossl_rcu_lock_new.pod | 32 support for the underlying OS threading API is built-in. Currently, OpenSSL 34 any multi-threading support, for example on platforms that don't provide 35 any threading support or that provide a threading API that is not yet 131 You can find out if OpenSSL was configured with thread support: 135 /* thread support enabled */ 137 /* no thread support */
|