Lines Matching +full:in +full:- +full:functions

5 migration_guide - OpenSSL migration guide
16 For an overview of some of the key concepts introduced in OpenSSL 3.0 see
26 uses an older version of OpenSSL will at the very least need to be recompiled in
30 changes may be required in some cases. Changes may also be required if
31 applications need to take advantage of some of the new features available in
36 In previous versions, OpenSSL was licensed under the L<dual OpenSSL and SSLeay
37 licenses|https://www.openssl.org/source/license-openssl-ssleay.txt>
39 L<Apache License v2|https://www.openssl.org/source/apache-license-2.0.txt>.
50 "high level" APIs (for example those functions prefixed with C<EVP>). They cannot
56 at configuration time using the C<enable-fips> option. If it is enabled,
57 the FIPS provider gets built and installed in addition to the other standard
66 L<EVP_EncryptInit_ex(3)>, and L<EVP_DigestInit(3)> functions. In case when
67 the requested algorithm is not available, these functions will fail.
72 L</Using the FIPS Module in applications>.
80 For example, the EVP APIs provide the functions L<EVP_EncryptInit_ex(3)>,
82 encryption. Those functions can be used with the algorithms AES, CHACHA, 3DES etc.
84 to call AES specific functions such as L<AES_set_encrypt_key(3)>,
85 L<AES_encrypt(3)>, and so on. The functions for 3DES are different.
87 development team for a long time. However in OpenSSL 3.0 this is made more
88 formal. All such low level APIs have been deprecated. You may still use them in
94 This is described in more detail in L</Deprecation of Low Level Functions>
100 These legacy EVP algorithms are still available in OpenSSL 3.0 but not by
103 See L<OSSL_PROVIDER-legacy(7)> for a complete list of algorithms.
116 L<EC_KEY_METHOD_new(3)>, etc.). These functions are being deprecated in
131 Engine-backed keys can be loaded via custom B<OSSL_STORE> implementation.
132 In this case the B<EVP_PKEY> objects created via L<ENGINE_load_private_key(3)>
136 To prefer the provider-based hardware offload, you can specify the default
139 Setting engine-based or application-based default low-level crypto method such
141 default provider will use the engine-based implementation for the crypto
143 B<PEM_> or B<d2i_> APIs will be provider-based. To create a fully legacy
145 functions must be used.
156 instead the patch level is indicated by the final number in the version. A
157 change in the second (MINOR) number indicates that new features may have been
168 See L<openssl-cmp(1)> and L<OSSL_CMP_exec_certreq(3)> as starting points.
173 ASN.1-encoded contents, proxies, and timeouts.
179 Previously KDF algorithms had been shoe-horned into using the EVP_PKEY object
185 See also L<OSSL_PROVIDER-default(7)/Key Derivation Function (KDF)> and
186 L<OSSL_PROVIDER-FIPS(7)/Key Derivation Function (KDF)>.
193 use of MACs through raw private keys in functionality such as
197 See also L<OSSL_PROVIDER-default(7)/Message Authentication Code (MAC)>
198 and L<OSSL_PROVIDER-FIPS(7)/Message Authentication Code (MAC)>.
202 Using calls to convenience functions such as EVP_sha256() and EVP_aes_256_gcm() may
211 In order to use KTLS, support for it must be compiled in using the
212 C<enable-ktls> configuration option. It must also be enabled at run time using
223 See L<EVP_KDF-SS(7)> and L<EVP_KDF-SSHKDF(7)>
229 See L<EVP_MAC-GMAC(7)> and L<EVP_MAC-KMAC(7)>.
235 See L<EVP_KEM-RSA(7)>.
239 Cipher Algorithm "AES-SIV"
248 unwrapping. The algorithms are: "AES-128-WRAP-INV", "AES-192-WRAP-INV",
249 "AES-256-WRAP-INV", "AES-128-WRAP-PAD-INV", "AES-192-WRAP-PAD-INV" and
250 "AES-256-WRAP-PAD-INV".
256 The algorithms are "AES-128-CBC-CTS", "AES-192-CBC-CTS", "AES-256-CBC-CTS",
257 "CAMELLIA-128-CBC-CTS", "CAMELLIA-192-CBC-CTS" and "CAMELLIA-256-CBC-CTS".
268 Added CAdES-BES signature verification support.
272 Added CAdES-BES signature scheme and attributes support (RFC 5126) to CMS API.
278 This uses the AES-GCM parameter (RFC 5084) for the Cryptographic Message Syntax.
293 with the password-based encryption iteration count. The default digest
294 algorithm for the MAC computation was changed to SHA-256. The pkcs12
295 application now supports -legacy option that restores the previous
319 Unlike in 1.x.y, the PKCS12KDF algorithm used when a PKCS#12 structure
323 See L<EVP_KDF-PKCS12KDF(7)>, L<PKCS12_create(3)>, L<openssl-pkcs12(1)>,
324 L<OSSL_PROVIDER-FIPS(7)>.
336 configured with the C<enable-trace> option.
346 Previously (in 1.1.1) they would return -2. For key types that do not have
353 This code is now always set to zero. Related functions are deprecated.
357 The type-safe wrappers are declared everywhere and implemented once.
368 These functions are legacy APIs that are not applicable to the new provider
375 The Miller-Rabin test now uses 64 rounds, which is used for all prime generation,
378 The default key generation method for the regular 2-prime RSA keys was changed
379 to the FIPS186-4 B.3.6 method (Generation of Probable Primes with Conditions
383 =head4 Change PBKDF2 to conform to SP800-132 instead of the older PKCS5 RFC2898
387 For backwards compatibility these checks are disabled by default in the
388 default provider, but are enabled by default in the FIPS provider.
390 To enable or disable the checks see B<OSSL_KDF_PARAM_PKCS5> in
391 L<EVP_KDF-PBKDF2(7)>. The parameter can be set using L<EVP_KDF_derive(3)>.
395 Smaller sizes now result in an error.
402 Unlike in previous OpenSSL versions, this means that applications cannot
414 In particular, a private scalar I<k> outside the range I<< 1 <= k < n-1 >> is
419 This function made a B<EVP_PKEY> object mutable after it had been set up. In
423 =head4 Functions that return an internal key should be treated as read only
425 Functions such as L<EVP_PKEY_get0_RSA(3)> behave slightly differently in
426 OpenSSL 3.0. Previously they returned a pointer to the low-level key used
427 internally by libcrypto. From OpenSSL 3.0 this key may now be held in a
428 provider. Calling these functions will only return a handle on the internal key
429 where the EVP_PKEY was constructed using this key in the first place, for
432 Where the EVP_PKEY holds a provider managed key, then these functions now return
434 after the first time the cached key is accessed will not be reflected back in
436 code will not be reflected back in the internal provider key.
438 For the above reasons the keys returned from these functions should typically be
439 treated as read-only. To emphasise this the value returned from
443 to refactor the code to avoid the use of these deprecated functions. Failing
446 and L<EVP_PKEY_get1_DH(3)> functions continue to return a non-const pointer to
447 enable them to be "freed". However they should also be treated as read-only.
451 This may mean result in an error in L<EVP_PKEY_derive_set_peer(3)> rather than
455 =head4 The print format has cosmetic changes for some functions
457 The output from numerous "printing" functions such as L<X509_signature_print(3)>,
458 L<X509_print_ex(3)>, L<X509_CRL_print_ex(3)>, and other similar functions has been
460 observed in 1.1.1 and 3.0. This also applies to the B<-text> output from the
469 One significant change is that controls which used to return -2 for
470 invalid inputs, now return -1 indicating a generic error condition instead.
474 Previously (in 1.1.1) these conflicting parameters were allowed, but will now
475 result in errors. See L<EVP_PKEY-DH(7)> for further details. This affects the
476 behaviour of L<openssl-genpkey(1)> for DH parameter generation.
501 =head4 ChaCha20-Poly1305 cipher does not allow a truncated IV length to be used
503 In OpenSSL 3.0 setting the IV length to any value other than 12 will result in an
507 in an IV that had leading zero padding.
511 Please refer to the INSTALL.md file in the top of the distribution for
518 forward in most cases. The most likely area where you will encounter problems
519 is if you have used low level APIs in your code (as discussed above). In that
527 Ignore the warnings. They are just warnings. The deprecated functions are still present and you may…
535 Remove your usage of the low level APIs. In this case you will need to rewrite your code to use the…
545 Password-protected keys may deserve special attention. If only some errors
554 difficult. In addition to the issues discussed above in the section about
563 Check the file INSTALL.md in the top of the installation for instructions on how
565 files in the same directory, as applicable for your platform.
569 Many structures have been made opaque in OpenSSL 3.0.
572 moved to internal header files. In practice this means that you can no longer
575 Additionally you must use "setter" or "getter" functions to access the fields
611 In OpenSSL 3.0 the FIPS support is fully integrated into the mainline version of
617 See L<fips_module(7)> and L<OSSL_PROVIDER-FIPS(7)> for details.
622 been configured. The current documentation can be found in the
623 L<README-FIPS|https://github.com/openssl/openssl/blob/master/README-FIPS.md> file.
629 some of the new features that OpenSSL 3.0 makes available. In order to do that
630 you need to understand some new concepts introduced in OpenSSL 3.0.
641 functions may need to be changed to pass additional parameters to handle the
644 =head4 Using a Library Context - Old functions that should be changed
646 If a library context is needed then all EVP_* digest functions that return a
650 If a library context is needed then all EVP_* cipher functions that return a
654 Some functions can be passed an object that has already been set up with a library
661 All functions listed below with a I<NAME> have a replacement function I<NAME_ex>
662 that takes B<OSSL_LIB_CTX> as an additional argument. Functions that have other
851 =head4 New functions that use a Library context
853 The following functions can be passed a library context if required.
986 Providers are described in detail here L<crypto(7)/Providers>.
991 Implicit and Explicit Fetching is described in detail here
996 The existing functions for controls (such as L<EVP_CIPHER_CTX_ctrl(3)>) and
1007 =head3 Deprecation of Low Level Functions
1009 A significant number of APIs have been deprecated in OpenSSL 3.0.
1011 See L</Deprecated function mappings> for the list of deprecated functions
1014 =head4 Providers are a replacement for engines and low-level method overrides
1023 =head4 Deprecated i2d and d2i functions for low-level key types
1025 Any i2d and d2i functions such as d2i_DHparams() that take a low-level key type
1030 =head4 Deprecated low-level key object getters and setters
1032 Applications that set or get low-level key objects (such as EVP_PKEY_set1_DH()
1037 =head4 Deprecated low-level key parameter getters
1039 Functions that access low-level objects directly such as L<RSA_get0_n(3)> are now
1044 Gettable parameters are listed in L<EVP_PKEY-RSA(7)/Common RSA parameters>,
1045 L<EVP_PKEY-DH(7)/DH parameters>, L<EVP_PKEY-DSA(7)/DSA parameters>,
1046 L<EVP_PKEY-FFC(7)/FFC parameters>, L<EVP_PKEY-EC(7)/Common EC parameters> and
1047 L<EVP_PKEY-X25519(7)/Common X25519, X448, ED25519 and ED448 parameters>.
1050 =head4 Deprecated low-level key parameter setters
1052 Functions that access low-level objects directly such as L<RSA_set0_crt_params(3)>
1057 See L<EVP_PKEY-DH(7)/Examples> for more information.
1058 See L</Deprecated low-level key generation functions> for information on
1061 =head4 Deprecated low-level object creation
1063 Low-level objects were created using methods such as L<RSA_new(3)>,
1065 high-level EVP_PKEY APIs, e.g. L<EVP_PKEY_new(3)>, L<EVP_PKEY_up_ref(3)> and
1069 EVP_PKEYs may be created in a variety of ways:
1070 See also L</Deprecated low-level key generation functions>,
1071 L</Deprecated low-level key reading and writing functions> and
1072 L</Deprecated low-level key parameter setters>.
1074 =head4 Deprecated low-level encryption functions
1076 Low-level encryption functions such as L<AES_encrypt(3)> and L<AES_decrypt(3)>
1082 =head4 Deprecated low-level digest functions
1084 Use of low-level digest functions such as L<SHA1_Init(3)> have been
1087 and L<EVP_DigestFinal_ex(3)>, or the quick one-shot L<EVP_Q_digest(3)>.
1089 Note that the functions L<SHA1(3)>, L<SHA224(3)>, L<SHA256(3)>, L<SHA384(3)>
1092 =head4 Deprecated low-level signing functions
1094 Use of low-level signing functions such as L<DSA_sign(3)> have been
1097 See also L<EVP_SIGNATURE-RSA(7)>, L<EVP_SIGNATURE-DSA(7)>,
1098 L<EVP_SIGNATURE-ECDSA(7)> and L<EVP_SIGNATURE-ED25519(7)>.
1100 =head4 Deprecated low-level MAC functions
1102 Low-level mac functions such as L<CMAC_Init(3)> are deprecated.
1105 L<EVP_MAC_update(3)> and L<EVP_MAC_final(3)> or the single-shot MAC function
1107 See L<EVP_MAC(3)>, L<EVP_MAC-HMAC(7)>, L<EVP_MAC-CMAC(7)>, L<EVP_MAC-GMAC(7)>,
1108 L<EVP_MAC-KMAC(7)>, L<EVP_MAC-BLAKE2(7)>, L<EVP_MAC-Poly1305(7)> and
1109 L<EVP_MAC-Siphash(7)> for additional information.
1111 Note that the one-shot method HMAC() is still available for compatibility purposes,
1114 =head4 Deprecated low-level validation functions
1116 Low-level validation functions such as L<DH_check(3)> have been informally
1117 discouraged from use for a long time. Applications should instead use the high-level
1123 =head4 Deprecated low-level key exchange functions
1125 Many low-level functions have been informally discouraged from use for a long
1127 See L<EVP_KEYEXCH-DH(7)>, L<EVP_KEYEXCH-ECDH(7)> and L<EVP_KEYEXCH-X25519(7)>.
1129 =head4 Deprecated low-level key generation functions
1131 Many low-level functions have been informally discouraged from use for a long
1133 L<EVP_PKEY_generate(3)> as described in L<EVP_PKEY-DSA(7)>, L<EVP_PKEY-DH(7)>,
1134 L<EVP_PKEY-RSA(7)>, L<EVP_PKEY-EC(7)> and L<EVP_PKEY-X25519(7)>.
1135 The 'quick' one-shot function L<EVP_PKEY_Q_keygen(3)> and macros for the most
1138 =head4 Deprecated low-level key reading and writing functions
1140 Use of low-level objects (such as DSA) has been informally discouraged from use
1141 for a long time. Functions to read and write these low-level objects (such as
1145 =head4 Deprecated low-level key printing functions
1147 Use of low-level objects (such as DSA) has been informally discouraged from use
1148 for a long time. Functions to print these low-level objects such as
1149 DSA_print() should be replaced with the equivalent EVP_PKEY functions.
1158 The following functions have been deprecated in 3.0.
1166 There is no replacement for the IGE functions. New code should not use these modes.
1167 These undocumented functions were never integrated into the EVP layer.
1169 Bi-directional IGE mode. These modes were never formally standardised and
1170 usage of these functions is believed to be very small. In particular
1185 See L</Deprecated low-level encryption functions>
1197 There are no replacements. These old functions are not used, and could be
1206 previously passed in pointer.
1213 See L</Deprecated low-level encryption functions>.
1226 Use the respective non-deprecated _ex() functions.
1233 64 rounds of the Miller-Rabin primality test.
1245 There are no replacements for these low-level functions. They were used internally
1256 See L</Deprecated low-level encryption functions>.
1263 See L</Deprecated low-level encryption functions>.
1271 See L</Deprecated low-level MAC functions>.
1277 See L</Deprecated low-level MAC functions>.
1286 Memory-leak checking has been deprecated in favor of more modern development
1296 Use the higher level functions EVP_CipherInit_ex2(), EVP_CipherUpdate() and
1298 See the "cts_mode" parameter in
1300 See L<EVP_EncryptInit(3)/EXAMPLES> for a AES-256-CBC-CTS example.
1314 See L</Deprecated i2d and d2i functions for low-level key types>
1321 See L</Deprecated low-level key parameter setters>
1335 See L</Deprecated low-level encryption functions>.
1336 Algorithms for "DESX-CBC", "DES-ECB", "DES-CBC", "DES-OFB", "DES-CFB",
1337 "DES-CFB1" and "DES-CFB8" have been moved to the L<Legacy Provider|/Legacy Algorithms>.
1351 See L</Deprecated low-level validation functions>
1366 See L</Deprecated low-level key exchange functions>.
1372 See L</Deprecated low-level object creation>
1378 See L</Deprecated low-level key generation functions>.
1385 See L</Deprecated low-level key parameter getters>
1391 Applications should instead set the B<OSSL_PKEY_PARAM_GROUP_NAME> as specified in
1392 L<EVP_PKEY-DH(7)/DH parameters>) to one of "dh_1024_160", "dh_2048_224" or
1407 See L</Providers are a replacement for engines and low-level method overrides>
1413 See L</Deprecated low-level key printing functions>
1419 See L</Deprecated low-level key parameter setters>
1439 See L</Deprecated low-level key generation functions>.
1447 See L</Providers are a replacement for engines and low-level method overrides>.
1454 See L</Deprecated low-level key parameter getters>.
1460 See L</Deprecated low-level object creation>
1473 See L</Deprecated low-level key printing functions>
1479 See L</Deprecated low-level key parameter setters>
1491 See L</Deprecated low-level signing functions>.
1497 See L</Deprecated low-level key exchange functions>.
1505 "kdf-type" as shown in L<EVP_KEYEXCH-ECDH(7)/EXAMPLES>
1512 See L</Deprecated low-level signing functions>.
1526 There are no replacements for these functions. Applications should rely on the
1548 These functions are not widely used. Applications should instead switch to
1555 EC_METHOD is now an internal-only concept and a suitable EC_METHOD is assigned
1569 See L</Deprecated low-level validation functions>
1575 See L<EVP_PKEY-EC(7)/Common EC parameters> which handles flags as separate
1580 See also L<EVP_PKEY-EC(7)/EXAMPLES>
1599 See L</Deprecated low-level key generation functions>.
1606 See L</Deprecated low-level key parameter getters>.
1615 See L</Providers are a replacement for engines and low-level method overrides>
1622 See L</Providers are a replacement for engines and low-level method overrides>
1635 See L</Deprecated low-level object creation>
1641 See L</Deprecated low-level key printing functions>
1647 See L</Deprecated low-level key parameter setters>.
1654 See L</Deprecated low-level key parameter setters>.
1661 See L</Deprecated low-level key printing functions>
1667 These functions were not particularly useful, since EC point serialization
1668 formats are not individual big-endian integers.
1682 These functions are not widely used. Applications should instead use the
1684 functions.
1690 There is no replacement. These functions were not widely used, and OpenSSL
1710 All engine functions are deprecated. An engine should be rewritten as a provider.
1711 See L</Providers are a replacement for engines and low-level method overrides>.
1718 OpenSSL now loads error strings automatically so these functions are not needed.
1724 The new functions are L<ERR_peek_error_func(3)>, L<ERR_peek_last_error_func(3)>,
1728 with ERR_peek functions and finish off with getting the error code by using
1745 See L</Providers are a replacement for engines and low-level method overrides>.
1761 See the "kdf-ukm" item in L<EVP_KEYEXCH-DH(7)/DH key exchange parameters> and
1762 L<EVP_KEYEXCH-ECDH(7)/ECDH Key Exchange parameters>.
1763 These functions are obsolete and should not be required.
1797 See L</Functions that return an internal key should be treated as read only>.
1803 See L</Providers are a replacement for engines and low-level method overrides>.
1809 See L</Deprecated low-level MAC functions>.
1816 See L</Deprecated low-level key object getters and setters>
1822 These functions were previously used by libssl to set or get an encoded public
1824 generic functions L<EVP_PKEY_set1_encoded_public_key(3)> and
1827 new functions.
1833 See L</Providers are a replacement for engines and low-level method overrides>.
1846 See L</Deprecated low-level MAC functions>.
1853 See L</Deprecated low-level MAC functions>.
1859 See L</Deprecated low-level key reading and writing functions>
1868 See L</Deprecated low-level key reading and writing functions>
1877 See L</Deprecated low-level key reading and writing functions>
1885 See L</Deprecated low-level key parameter getters>
1893 See L</Deprecated low-level key reading and writing functions>
1902 See L</Deprecated low-level encryption functions>.
1915 See L</Deprecated low-level encryption functions>.
1928 See L</Deprecated low-level encryption functions>.
1935 See L</Deprecated low-level encryption functions>.
1942 See L</Deprecated low-level encryption functions>.
1959 B<OCSP_REQ_CTX> type and B<OCSP_REQ_CTX_*()> functions
1963 type is B<OSSL_HTTP_REQ_CTX>, and the deprecated functions are replaced
1971 There is no replacement for these functions. These pthread fork support methods
1986 These functions helped applications and engines create loaders for
1987 schemes they supported.  These are all deprecated and discouraged in favour of
1988 provider implementations, see L<provider-storemgmt(7)>.
2009 See L</Deprecated low-level key reading and writing functions>
2015 See L</Deprecated low-level encryption functions>.
2034 See L</Deprecated low-level encryption functions>.
2042 See L</Deprecated low-level digest functions>.
2056 See L</Deprecated low-level validation functions>
2073 See L</Deprecated low-level key generation functions>.
2079 See L</Providers are a replacement for engines and low-level method overrides>
2089 See L</Deprecated low-level key parameter getters>
2095 See L</Deprecated low-level object creation>.
2101 See L</Providers are a replacement for engines and low-level method overrides>.
2113 See L</Providers are a replacement for engines and low-level method overrides>.
2119 See L</Deprecated low-level signing functions> and
2120 L</Deprecated low-level encryption functions>.
2126 See L</Deprecated low-level key printing functions>
2132 See L</Deprecated low-level encryption functions>
2139 mode of none). See L</Deprecated low-level signing functions>.
2151 See L</Deprecated low-level key reading and writing functions>
2158 See L</Deprecated low-level key parameter setters>.
2164 See L</Providers are a replacement for engines and low-level method overrides>
2172 See L</Deprecated low-level signing functions>.
2178 There are no replacements for these functions.
2179 X931 padding can be set using L<EVP_SIGNATURE-RSA(7)/Signature Parameters>.
2187 See L</Deprecated low-level encryption functions>.
2198 See L</Deprecated low-level digest functions>.
2209 There are no replacements for the SRP functions.
2216 These are used to set the Diffie-Hellman (DH) parameters that are to be used by
2218 the built-in DH parameters that are available by calling L<SSL_CTX_set_dh_auto(3)>
2220 use the alternative functions L<SSL_CTX_set0_tmp_dh_pkey(3)> and
2222 functions. The callback was originally useful in order to have different
2223 parameters for export and non-export ciphersuites. Export ciphersuites are no
2224 longer supported by OpenSSL. Use of the callback functions should be replaced
2238 See L</Deprecated low-level digest functions>.
2258 The following functions for NID (numeric id) handling have changed semantics.
2270 L<EVP_PKEY_get_id(3)> might now also return the value -1
2278 =head2 Using the FIPS Module in applications
2280 See L<fips_module(7)> and L<OSSL_PROVIDER-FIPS(7)> for details.
2286 L<B<openssl kdf>|openssl-kdf(1)> uses the new L<EVP_KDF(3)> API.
2287 L<B<openssl kdf>|openssl-mac(1)> uses the new L<EVP_MAC(3)> API.
2291 B<-provider_path> and B<-provider> are available to all apps and can be used
2294 specified if required. The B<-provider_path> must be specified before the
2295 B<-provider> option.
2297 The B<list> app has many new options. See L<openssl-list(1)> for more
2300 B<-crl_lastupdate> and B<-crl_nextupdate> used by B<openssl ca> allows
2301 explicit setting of fields in the generated CRL.
2307 The B<-crypt> option used by B<openssl passwd>.
2308 The B<-c> option used by B<openssl x509>, B<openssl dhparam>,
2314 These are primarily changes in capitalisation and white space.  However, in some
2325 B<openssl speed> no longer uses low-level API calls.
2343 now in maintenance mode and no new features will be added to them.
2367 The signatures of the functions to get and set options on SSL and
2371 to use the B<SSL_OP_> macro values in preprocessor C<#if> conditions.
2381 These functions now take IP literal addresses as well as actual hostnames.
2394 Client-initiated renegotiation is disabled by default.
2396 To allow it, use the B<-client_renegotiation> option,
2412 Combining the Configure options no-ec and no-dh no longer disables TLSv1.3
2417 implementations even where there are no built-in ones. Attempting to create
2418 TLS connections in such a build without also disabling TLSv1.3 at run time or
2419 using third party provider groups may result in handshake failures. TLSv1.3
2420 can be disabled at compile time using the "no-tls1_3" Configure option.
2434 in the "other" parameter. In most places this is what is passed. All these
2451 The security strength of SHA1 and MD5 based signatures in TLS has been reduced.
2453 This results in SSL 3, TLS 1.0, TLS 1.1 and DTLS 1.0 no longer
2458 then the handshake will fail in TLS 1.2 at security level 1. This is because,
2467 In TLS/SSL the default security level is 1. It can be set either using the cipher
2469 leaf certificate is signed with SHA-1, a call to L<SSL_CTX_use_certificate(3)>
2471 Outside TLS/SSL, the default security level is -1 (effectively 0). It can
2472 be set using L<X509_VERIFY_PARAM_set_auth_level(3)> or using the B<-auth_level>
2487 Copyright 2021-2024 The OpenSSL Project Authors. All Rights Reserved.
2490 this file except in compliance with the License.  You can obtain a copy
2491 in the file LICENSE in the source distribution or at