1 files changed, 10 insertions, 2 deletions
diff --git a/upstream/archlinux/man7/ossl-guide-migration.7ssl b/upstream/archlinux/man7/ossl-guide-migration.7ssl
index 26c05d89..68b370e8 100644
--- a/upstream/archlinux/man7/ossl-guide-migration.7ssl
+++ b/upstream/archlinux/man7/ossl-guide-migration.7ssl
@@ -55,7 +55,7 @@
 .\" ========================================================================
 .\"
 .IX Title "OSSL-GUIDE-MIGRATION 7ssl"
-.TH OSSL-GUIDE-MIGRATION 7ssl 2024-01-30 3.2.1 OpenSSL
+.TH OSSL-GUIDE-MIGRATION 7ssl 2024-04-28 3.3.0 OpenSSL
 .\" For nroff, turn off justification.  Always turn off hyphenation; it makes
 .\" way too many mistakes in technical documents.
 .if n .ad l
@@ -217,6 +217,14 @@ To ensure the future compatibility, the engines should be turned to providers.
 To prefer the provider-based hardware offload, you can specify the default
 properties to prefer your provider.
 .PP
+Setting engine-based or application-based default low-level crypto method such
+as \fBRSA_METHOD\fR or \fBEC_KEY_METHOD\fR is still possible and keys inside the
+default provider will use the engine-based implementation for the crypto
+operations. However \fBEVP_PKEY\fRs created by decoding by using \fBOSSL_DECODER\fR,
+\&\fBPEM_\fR or \fBd2i_\fR APIs will be provider-based. To create a fully legacy
+\&\fBEVP_PKEY\fRs \fBEVP_PKEY_set1_RSA\fR\|(3), \fBEVP_PKEY_set1_EC_KEY\fR\|(3) or similar
+functions must be used.
+.PP
 \fIVersioning Scheme\fR
 .IX Subsection "Versioning Scheme"
 .PP
@@ -2082,7 +2090,7 @@ options of the commands.
 The migration guide was created for OpenSSL 3.0.
 .SH COPYRIGHT
 .IX Header "COPYRIGHT"
-Copyright 2021\-2023 The OpenSSL Project Authors. All Rights Reserved.
+Copyright 2021\-2024 The OpenSSL Project Authors. All Rights Reserved.
 .PP
 Licensed under the Apache License 2.0 (the "License").  You may not use
 this file except in compliance with the License.  You can obtain a copy