Lines Matching full:applications

81 consequently the property query \f(CW\*(C`fips=yes\*(C'\fR is mandatory for applications that
103 of applications will work unchanged with OpenSSL 3.0 if those applications
106 applications need to take advantage of some of the new features available in
149 "Using the FIPS Module in applications".
167 your applications, but you may start to see deprecation warnings during
183 Applications using the EVP APIs to access these algorithms should instead use
184 more modern algorithms. If that is not possible then these applications
199 This is particularly relevant for applications written to use the OpenSSL 3.0
267 Existing applications that use KDF algorithms using EVP_PKEY
270 All new applications should use the new \fBEVP_KDF\fR\|(3) interface.
283 All new applications should use the new \fBEVP_MAC\fR\|(3) interface.
442 model. Applications should instead use
479 Unlike in previous OpenSSL versions, this means that applications cannot
483 to generate EVP_PKEY_SM2 parameters and keys. Applications must now generate
521 Applications broken by this change should be modified. The preferred solution is
542 \&\fBopenssl x509\fR and \fBopenssl crl\fR applications.
585 reason the \fBERR_GET_FUNC()\fR macro was removed. Applications must resolve
670 This has a number of implications for SSL/TLS applications. See the
696 Applications written to work with OpenSSL 1.1.1 will mostly just work with
944 Applications using engines should instead use providers.
954 have been deprecated. Applications should instead use the \fBOSSL_DECODER\fR\|(3) and
961 Applications that set or get low-level key objects (such as \fBEVP_PKEY_set1_DH()\fR
970 deprecated. Applications should use one of:
988 Applications may also use \fBEVP_PKEY_todata\fR\|(3) to return all fields.
994 are now deprecated. Applications should use \fBEVP_PKEY_fromdata\fR\|(3) to create
1006 \&\fBRSA_up_ref\fR\|(3) and \fBRSA_free\fR\|(3). Applications should instead use the
1020 have been informally discouraged from use for a long time. Applications should
1029 informally discouraged from use for a long time.  Applications should instead
1040 informally discouraged for a long time. Instead applications should use
1049 Applications should instead use the new \fBEVP_MAC\fR\|(3) interface, using
1064 discouraged from use for a long time. Applications should instead use the high-level
1074 time. Applications should instead use \fBEVP_PKEY_derive\fR\|(3).
1081 time. Applications should instead use \fBEVP_PKEY_keygen_init\fR\|(3) and
1092 \&\fBPEM_read_DSA_PUBKEY()\fR) should be replaced. Applications should instead use
1283 Applications should instead set the \fBOSSL_PKEY_PARAM_GROUP_NAME\fR as specified in
1289 Applications should use \fBEVP_PKEY_CTX_set_dh_kdf_type\fR\|(3) instead.
1312 There is no direct replacement. Applications may use \fBEVP_PKEY_copy_parameters\fR\|(3)
1336 There is no direct replacement. Applications may use \fBEVP_PKEY_copy_parameters\fR\|(3)
1361 Applications may either set this using the helper function
1372 Applications should use \fBEVP_PKEY_get_size\fR\|(3).
1378 There are no replacements for these functions. Applications should rely on the
1389 Applications should use \fBEC_GROUP_get_curve\fR\|(3) and \fBEC_GROUP_set_curve\fR\|(3).
1394 These functions are not widely used. Applications should instead switch to
1405 Applications should use \fBEVP_PKEY_can_sign\fR\|(3) instead.
1422 There is no direct replacement. Applications may use \fBEVP_PKEY_copy_parameters\fR\|(3)
1485 Applications should use \fBEC_POINT_get_affine_coordinates\fR\|(3) and
1490 These functions are not widely used. Applications should instead use the
1501 Applications should use \fBEC_POINT_set_compressed_coordinates\fR\|(3) instead.
1505 This function is not widely used. Applications should instead use the
1523 Applications should use \fBERR_get_error_all\fR\|(3), or pick information
1529 Applications should instead use \fBEVP_CIPHER_CTX_get_updated_iv\fR\|(3),
1555 Applications should use \fBEVP_PKEY_CTX_set1_rsa_keygen_pubexp\fR\|(3) instead.
1559 Applications should use \fBEVP_PKEY_eq\fR\|(3) and \fBEVP_PKEY_parameters_eq\fR\|(3) instead.
1564 Applications should use \fBEVP_PKEY_encrypt_init\fR\|(3) and \fBEVP_PKEY_encrypt\fR\|(3) or
1714 These functions helped applications and engines create loaders for
1744 Applications should instead use \fBRAND_set_DRBG_type\fR\|(3),
1833 There is no direct replacement. Applications may use \fBEVP_PKEY_dup\fR\|(3).
1887 servers requiring ephemeral DH keys. Instead applications should consider using
1889 or \fBSSL_set_dh_auto\fR\|(3). If custom parameters are necessary then applications can
1909 This was an undocumented function. Applications can use \fBX509_get0_pubkey\fR\|(3)
1932 .SS "Using the FIPS Module in applications"
1933 .IX Subsection "Using the FIPS Module in applications"
1937 \fINew applications\fR
1938 .IX Subsection "New applications"
1970 The output of Command line applications may have minor changes.
2048 SSL or TLS connections to succeed.  Applications that require the ability