Lines Matching full:applications

161 of applications will work unchanged with OpenSSL 3.0 if those applications
164 applications need to take advantage of some of the new features available in
207 \&\*(L"Using the \s-1FIPS\s0 Module in applications\*(R".
225 your applications, but you may start to see deprecation warnings during
241 Applications using the \s-1EVP\s0 APIs to access these algorithms should instead use
242 more modern algorithms. If that is not possible then these applications
257 This is particularly relevant for applications written to use the OpenSSL 3.0
317 Existing applications that use \s-1KDF\s0 algorithms using \s-1EVP_PKEY\s0
320 All new applications should use the new \s-1\fBEVP_KDF\s0\fR\|(3) interface.
333 All new applications should use the new \s-1\fBEVP_MAC\s0\fR\|(3) interface.
492 model. Applications should instead use
529 Unlike in previous OpenSSL versions, this means that applications cannot
533 to generate \s-1EVP_PKEY_SM2\s0 parameters and keys. Applications must now generate
571 Applications broken by this change should be modified. The preferred solution is
592 \&\fBopenssl x509\fR and \fBopenssl crl\fR applications.
635 reason the \s-1\fBERR_GET_FUNC\s0()\fR macro was removed. Applications must resolve
720 This has a number of implications for \s-1SSL/TLS\s0 applications. See the
746 Applications written to work with OpenSSL 1.1.1 will mostly just work with
994 Applications using engines should instead use providers.
1004 have been deprecated. Applications should instead use the \s-1\fBOSSL_DECODER\s0\fR\|(3) and
1011 Applications that set or get low-level key objects (such as \fBEVP_PKEY_set1_DH()\fR
1020 deprecated. Applications should use one of \fBEVP_PKEY_get_bn_param\fR\|(3),
1028 Applications may also use \fBEVP_PKEY_todata\fR\|(3) to return all fields.
1034 are now deprecated. Applications should use \fBEVP_PKEY_fromdata\fR\|(3) to create
1046 \&\fBRSA_up_ref\fR\|(3) and \fBRSA_free\fR\|(3). Applications should instead use the
1060 have been informally discouraged from use for a long time. Applications should
1069 informally discouraged from use for a long time.  Applications should instead
1080 informally discouraged for a long time. Instead applications should use
1089 Applications should instead use the new \s-1\fBEVP_MAC\s0\fR\|(3) interface, using
1104 discouraged from use for a long time. Applications should instead use the high-level
1114 time. Applications should instead use \fBEVP_PKEY_derive\fR\|(3).
1121 time. Applications should instead use \fBEVP_PKEY_keygen_init\fR\|(3) and
1132 \&\fBPEM_read_DSA_PUBKEY()\fR) should be replaced. Applications should instead use
1318 Applications should instead set the \fB\s-1OSSL_PKEY_PARAM_GROUP_NAME\s0\fR as specified in
1324 Applications should use \fBEVP_PKEY_CTX_set_dh_kdf_type\fR\|(3) instead.
1347 There is no direct replacement. Applications may use \fBEVP_PKEY_copy_parameters\fR\|(3)
1371 There is no direct replacement. Applications may use \fBEVP_PKEY_copy_parameters\fR\|(3)
1396 Applications may either set this using the helper function
1407 Applications should use \fBEVP_PKEY_get_size\fR\|(3).
1413 There are no replacements for these functions. Applications should rely on the
1424 Applications should use \fBEC_GROUP_get_curve\fR\|(3) and \fBEC_GROUP_set_curve\fR\|(3).
1429 These functions are not widely used. Applications should instead switch to
1440 Applications should use \fBEVP_PKEY_can_sign\fR\|(3) instead.
1457 There is no direct replacement. Applications may use \fBEVP_PKEY_copy_parameters\fR\|(3)
1520 Applications should use \fBEC_POINT_get_affine_coordinates\fR\|(3) and
1525 These functions are not widely used. Applications should instead use the
1536 Applications should use \fBEC_POINT_set_compressed_coordinates\fR\|(3) instead.
1540 This function is not widely used. Applications should instead use the
1558 Applications should use \fBERR_get_error_all\fR\|(3), or pick information
1564 Applications should instead use \fBEVP_CIPHER_CTX_get_updated_iv\fR\|(3),
1590 Applications should use \fBEVP_PKEY_CTX_set1_rsa_keygen_pubexp\fR\|(3) instead.
1594 Applications should use \fBEVP_PKEY_eq\fR\|(3) and \fBEVP_PKEY_parameters_eq\fR\|(3) instead.
1599 Applications should use \fBEVP_PKEY_encrypt_init\fR\|(3) and \fBEVP_PKEY_encrypt\fR\|(3) or
1744 These functions helped applications and engines create loaders for
1774 Applications should instead use \fBRAND_set_DRBG_type\fR\|(3),
1863 There is no direct replacement. Applications may use \fBEVP_PKEY_dup\fR\|(3).
1917 servers requiring ephemeral \s-1DH\s0 keys. Instead applications should consider using
1919 or \fBSSL_set_dh_auto\fR\|(3). If custom parameters are necessary then applications can
1939 This was an undocumented function. Applications can use \fBX509_get0_pubkey\fR\|(3)
1962 .SS "Using the \s-1FIPS\s0 Module in applications"
1963 .IX Subsection "Using the FIPS Module in applications"
1967 \fINew applications\fR
1968 .IX Subsection "New applications"
2000 The output of Command line applications may have minor changes.
2078 \&\s-1SSL\s0 or \s-1TLS\s0 connections to succeed.  Applications that require the ability