Lines Matching full:these

144 the requested algorithm is not available, these functions will fail.
179 These legacy EVP algorithms are still available in OpenSSL 3.0 but not by
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
196 \&\fBEC_KEY_METHOD_new\fR\|(3), etc.). These functions are being deprecated in
197 OpenSSL 3.0, and users of these APIs should know that their use can likely
378 derivation function which supports these parameters. This includes
441 These functions are legacy APIs that are not applicable to the new provider
462 For backwards compatibility these checks are disabled by default in the
507 provider. Calling these functions will only return a handle on the internal key
511 Where the EVP_PKEY holds a provider managed key, then these functions now return
517 For the above reasons the keys returned from these functions should typically be
522 to refactor the code to avoid the use of these deprecated functions. Failing
558 Previously (in 1.1.1) these conflicting parameters were allowed, but will now
624 it's worth testing these scenarios and processing the newly relevant codes.
938 that refer to these categories.
947 used by algorithms. All these methods such as \fBRSA_new_method()\fR and \fBRSA_meth_new()\fR
1091 for a long time. Functions to read and write these low-level objects (such as
1099 for a long time. Functions to print these low-level objects such as
1104 \&\fBEVP_PKEY_print_params_fp\fR\|(3). Note that internally these use
1114 There is no replacement for the IGE functions. New code should not use these modes.
1115 These undocumented functions were never integrated into the EVP layer.
1117 Bi-directional IGE mode. These modes were never formally standardised and
1118 usage of these functions is believed to be very small. In particular
1137 There are no replacements. These old functions are not used, and could be
1171 There are no replacements for these low-level functions. They were used internally
1262 There is no replacement for setting these flags.
1378 There are no replacements for these functions. Applications should rely on the
1394 These functions are not widely used. Applications should instead switch to
1453 There are no replacements for these.
1479 These functions were not particularly useful, since EC point serialization
1490 These functions are not widely used. Applications should instead use the
1496 There is no replacement. These functions were not widely used, and OpenSSL
1516 OpenSSL now loads error strings automatically so these functions are not needed.
1543 These control operations are not invoked by the OpenSSL library anymore and
1551 These functions are obsolete and should not be required.
1592 These functions were previously used by libssl to set or get an encoded public
1593 key into/from an EVP_PKEY object. With OpenSSL 3.0 these are replaced by the more
1693 These methods were used to collect all necessary data to form a HTTP request,
1701 There is no replacement for these functions. These pthread fork support methods
1714 These functions helped applications and engines create loaders for
1715 schemes they supported.  These are all deprecated and discouraged in favour of
1775 All of these RSA flags have been deprecated without replacement:
1856 There are no replacements for these functions.
1886 These are used to set the Diffie-Hellman (DH) parameters that are to be used by
1971 These are primarily changes in capitalisation and white space.  However, in some
2023 However it is still possible to test whether these macros are defined or not.
2030 These functions now take IP literal addresses as well as actual hostnames.
2071 in the "other" parameter. In most places this is what is passed. All these