Lines Matching full:applications

28 of applications will work unchanged with OpenSSL 3.0 if those applications
31 applications need to take advantage of some of the new features available in
72 L</Using the FIPS Module in applications>.
89 your applications, but you may start to see deprecation warnings during
104 Applications using the EVP APIs to access these algorithms should instead use
105 more modern algorithms. If that is not possible then these applications
119 This is particularly relevant for applications written to use the OpenSSL 3.0
181 Existing applications that use KDF algorithms using EVP_PKEY
184 All new applications should use the new L<EVP_KDF(3)> interface.
196 All new applications should use the new L<EVP_MAC(3)> interface.
369 model. Applications should instead use
402 Unlike in previous OpenSSL versions, this means that applications cannot
406 to generate EVP_PKEY_SM2 parameters and keys. Applications must now generate
442 Applications broken by this change should be modified. The preferred solution is
461 B<openssl x509> and B<openssl crl> applications.
498 reason the ERR_GET_FUNC() macro was removed. Applications must resolve
598 This has a number of implications for SSL/TLS applications. See the
627 Applications written to work with OpenSSL 1.1.1 will mostly just work with
1017 Applications using engines should instead use providers.
1026 have been deprecated. Applications should instead use the L<OSSL_DECODER(3)> and
1032 Applications that set or get low-level key objects (such as EVP_PKEY_set1_DH()
1040 deprecated. Applications should use one of L<EVP_PKEY_get_bn_param(3)>,
1048 Applications may also use L<EVP_PKEY_todata(3)> to return all fields.
1053 are now deprecated. Applications should use L<EVP_PKEY_fromdata(3)> to create
1064 L<RSA_up_ref(3)> and L<RSA_free(3)>. Applications should instead use the
1077 have been informally discouraged from use for a long time. Applications should
1085 informally discouraged from use for a long time.  Applications should instead
1095 informally discouraged for a long time. Instead applications should use
1103 Applications should instead use the new L<EVP_MAC(3)> interface, using
1117 discouraged from use for a long time. Applications should instead use the high-level
1126 time. Applications should instead use L<EVP_PKEY_derive(3)>.
1132 time. Applications should instead use L<EVP_PKEY_keygen_init(3)> and
1142 PEM_read_DSA_PUBKEY()) should be replaced. Applications should instead use
1391 Applications should instead set the B<OSSL_PKEY_PARAM_GROUP_NAME> as specified in
1399 Applications should use L<EVP_PKEY_CTX_set_dh_kdf_type(3)> instead.
1432 There is no direct replacement. Applications may use L<EVP_PKEY_copy_parameters(3)>
1466 There is no direct replacement. Applications may use L<EVP_PKEY_copy_parameters(3)>
1503 Applications may either set this using the helper function
1518 Applications should use L<EVP_PKEY_get_size(3)>.
1526 There are no replacements for these functions. Applications should rely on the
1541 Applications should use L<EC_GROUP_get_curve(3)> and L<EC_GROUP_set_curve(3)>.
1548 These functions are not widely used. Applications should instead switch to
1563 Applications should use L<EVP_PKEY_can_sign(3)> instead.
1586 There is no direct replacement. Applications may use L<EVP_PKEY_copy_parameters(3)>
1675 Applications should use L<EC_POINT_get_affine_coordinates(3)> and
1682 These functions are not widely used. Applications should instead use the
1697 Applications should use L<EC_POINT_set_compressed_coordinates(3)> instead.
1703 This function is not widely used. Applications should instead use the
1727 Applications should use L<ERR_get_error_all(3)>, or pick information
1735 Applications should instead use L<EVP_CIPHER_CTX_get_updated_iv(3)>,
1769 Applications should use L<EVP_PKEY_CTX_set1_rsa_keygen_pubexp(3)> instead.
1775 Applications should use L<EVP_PKEY_eq(3)> and L<EVP_PKEY_parameters_eq(3)> instead.
1782 Applications should use L<EVP_PKEY_encrypt_init(3)> and L<EVP_PKEY_encrypt(3)> or
1986 These functions helped applications and engines create loaders for
2022 Applications should instead use L<RAND_set_DRBG_type(3)>,
2145 There is no direct replacement. Applications may use L<EVP_PKEY_dup(3)>.
2217 servers requiring ephemeral DH keys. Instead applications should consider using
2219 or L<SSL_set_dh_auto(3)>. If custom parameters are necessary then applications can
2245 This was an undocumented function. Applications can use L<X509_get0_pubkey(3)>
2278 =head2 Using the FIPS Module in applications
2284 =head3 New applications
2313 The output of Command line applications may have minor changes.
2405 SSL or TLS connections to succeed.  Applications that require the ability