Lines Matching full:apis

71 "high level" APIs (for example those functions prefixed with C<EVP>). They cannot
72 be accessed using the L</Low Level APIs>.
95 =head3 Low Level APIs
97 OpenSSL has historically provided two sets of APIs for invoking cryptographic
98 algorithms: the "high level" APIs (such as the C<EVP> APIs) and the "low level"
99 APIs. The high level APIs are typically designed to work across all algorithm
100 types. The "low level" APIs are targeted at a specific algorithm implementation.
101 For example, the EVP APIs provide the functions L<EVP_EncryptInit_ex(3)>,
104 On the other hand, to do AES encryption using the low level APIs you would have
107 Use of the low level APIs has been informally discouraged by the OpenSSL
109 formal. All such low level APIs have been deprecated. You may still use them in
111 compilation (dependent on compiler support for this). Deprecated APIs may be
113 your code to use the high level APIs instead.
120 the EVP APIs are now considered legacy and their use is strongly discouraged.
125 Applications using the EVP APIs to access these algorithms should instead use
131 =head3 Engines and "METHOD" APIs
133 The refactoring to support Providers conflicts internally with the APIs used to
138 OpenSSL 3.0, and users of these APIs should know that their use can likely
164 B<PEM_> or B<d2i_> APIs will be provider-based. To create a fully legacy
319 Added enhanced PKCS#12 APIs which accept a library context B<OSSL_LIB_CTX>
320 and (where relevant) a property query. Other APIs which handle PKCS#7 and
333 As part of this change the EVP_PBE_xxx APIs can also accept a library
389 These functions are legacy APIs that are not applicable to the new provider
540 is if you have used low level APIs in your code (as discussed above). In that
556 Remove your usage of the low level APIs. In this case you will need to rewrite your code to use the…
1030 A significant number of APIs have been deprecated in OpenSSL 3.0.
1048 L<OSSL_ENCODER(3)> APIs to read and write files.
1056 APIs, or alternatively use L<EVP_PKEY_fromdata(3)> or L<EVP_PKEY_todata(3)>.
1096 high-level EVP_PKEY APIs, e.g. L<EVP_PKEY_new(3)>, L<EVP_PKEY_up_ref(3)> and
1109 instead use the high level EVP APIs L<EVP_EncryptInit_ex(3)>,
1117 use the high level EVP APIs L<EVP_DigestInit_ex(3)>, L<EVP_DigestUpdate(3)>
1149 EVP_PKEY APIs such as L<EVP_PKEY_check(3)>, L<EVP_PKEY_param_check(3)>,
2362 B<openssl genrsa> and B<openssl rsa> have been modified to use PKEY APIs.