Lines Matching refs:new
14 This guide details the changes required to migrate to new versions of OpenSSL.
48 order to work with the new version. It is the intention that the large majority
52 applications need to take advantage of some of the new features available in
143 using the new Provider API and avoiding deprecated methods.
170 The OpenSSL versioning scheme has changed with the OpenSSL 3.0 release. The new
178 change in the second (MINOR) number indicates that new features may have been
184 =head3 Other major new features
198 This simplifies the process of adding new KDF and PRF implementations.
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.
354 A new generic trace API has been added which provides support for enabling
383 The new L<EVP_RAND(3)> is a partial replacement: the DRBG callback framework is
384 absent. The RAND_DRBG API did not fit well into the new provider concept as
389 These functions are legacy APIs that are not applicable to the new provider
562 As OpenSSL 3.0 provides a brand new Encoder/Decoder mechanism for working with
650 some of the new features that OpenSSL 3.0 makes available. In order to do that
651 you need to understand some new concepts introduced in OpenSSL 3.0.
1075 new keys from user provided key data. Keys should be immutable once they are
1124 Applications should instead use the new L<EVP_MAC(3)> interface, using
1745 The new functions are L<ERR_peek_error_func(3)>, L<ERR_peek_last_error_func(3)>,
1848 new functions.
2252 Use the new L<SSL_CTX_set_tlsext_ticket_key_evp_cb(3)> function instead.
2290 of L<provider(7)>s EVP_PKEY_id() or its new equivalent
2307 L<B<openssl kdf>|openssl-kdf(1)> uses the new L<EVP_KDF(3)> API.
2308 L<B<openssl kdf>|openssl-mac(1)> uses the new L<EVP_MAC(3)> API.
2318 The B<list> app has many new options. See L<openssl-list(1)> for more
2364 now in maintenance mode and no new features will be added to them.
