Lines Matching full:applications

25 consequently the property query C<fips=yes> is mandatory for applications that
49 of applications will work unchanged with OpenSSL 3.0 if those applications
52 applications need to take advantage of some of the new features available in
93 L</Using the FIPS Module in applications>.
110 your applications, but you may start to see deprecation warnings during
125 Applications using the EVP APIs to access these algorithms should instead use
126 more modern algorithms. If that is not possible then these applications
140 This is particularly relevant for applications written to use the OpenSSL 3.0
202 Existing applications that use KDF algorithms using EVP_PKEY
205 All new applications should use the new L<EVP_KDF(3)> interface.
217 All new applications should use the new L<EVP_MAC(3)> interface.
390 model. Applications should instead use
423 Unlike in previous OpenSSL versions, this means that applications cannot
427 to generate EVP_PKEY_SM2 parameters and keys. Applications must now generate
463 Applications broken by this change should be modified. The preferred solution is
482 B<openssl x509> and B<openssl crl> applications.
519 reason the ERR_GET_FUNC() macro was removed. Applications must resolve
619 This has a number of implications for SSL/TLS applications. See the
648 Applications written to work with OpenSSL 1.1.1 will mostly just work with
1038 Applications using engines should instead use providers.
1047 have been deprecated. Applications should instead use the L<OSSL_DECODER(3)> and
1053 Applications that set or get low-level key objects (such as EVP_PKEY_set1_DH()
1061 deprecated. Applications should use one of:
1079 Applications may also use L<EVP_PKEY_todata(3)> to return all fields.
1084 are now deprecated. Applications should use L<EVP_PKEY_fromdata(3)> to create
1095 L<RSA_up_ref(3)> and L<RSA_free(3)>. Applications should instead use the
1108 have been informally discouraged from use for a long time. Applications should
1116 informally discouraged from use for a long time.  Applications should instead
1126 informally discouraged for a long time. Instead applications should use
1134 Applications should instead use the new L<EVP_MAC(3)> interface, using
1148 discouraged from use for a long time. Applications should instead use the high-level
1157 time. Applications should instead use L<EVP_PKEY_derive(3)>.
1163 time. Applications should instead use L<EVP_PKEY_keygen_init(3)> and
1173 PEM_read_DSA_PUBKEY()) should be replaced. Applications should instead use
1422 Applications should instead set the B<OSSL_PKEY_PARAM_GROUP_NAME> as specified in
1430 Applications should use L<EVP_PKEY_CTX_set_dh_kdf_type(3)> instead.
1463 There is no direct replacement. Applications may use L<EVP_PKEY_copy_parameters(3)>
1497 There is no direct replacement. Applications may use L<EVP_PKEY_copy_parameters(3)>
1534 Applications may either set this using the helper function
1549 Applications should use L<EVP_PKEY_get_size(3)>.
1557 There are no replacements for these functions. Applications should rely on the
1572 Applications should use L<EC_GROUP_get_curve(3)> and L<EC_GROUP_set_curve(3)>.
1579 These functions are not widely used. Applications should instead switch to
1594 Applications should use L<EVP_PKEY_can_sign(3)> instead.
1617 There is no direct replacement. Applications may use L<EVP_PKEY_copy_parameters(3)>
1706 Applications should use L<EC_POINT_get_affine_coordinates(3)> and
1713 These functions are not widely used. Applications should instead use the
1728 Applications should use L<EC_POINT_set_compressed_coordinates(3)> instead.
1734 This function is not widely used. Applications should instead use the
1758 Applications should use L<ERR_get_error_all(3)>, or pick information
1766 Applications should instead use L<EVP_CIPHER_CTX_get_updated_iv(3)>,
1800 Applications should use L<EVP_PKEY_CTX_set1_rsa_keygen_pubexp(3)> instead.
1806 Applications should use L<EVP_PKEY_eq(3)> and L<EVP_PKEY_parameters_eq(3)> instead.
1813 Applications should use L<EVP_PKEY_encrypt_init(3)> and L<EVP_PKEY_encrypt(3)> or
2017 These functions helped applications and engines create loaders for
2053 Applications should instead use L<RAND_set_DRBG_type(3)>,
2176 There is no direct replacement. Applications may use L<EVP_PKEY_dup(3)>.
2248 servers requiring ephemeral DH keys. Instead applications should consider using
2250 or L<SSL_set_dh_auto(3)>. If custom parameters are necessary then applications can
2276 This was an undocumented function. Applications can use L<X509_get0_pubkey(3)>
2309 =head2 Using the FIPS Module in applications
2315 =head3 New applications
2344 The output of Command line applications may have minor changes.
2436 SSL or TLS connections to succeed.  Applications that require the ability