From a4aa977d3a8049d5386dc583e16c17727c712eaa Mon Sep 17 00:00:00 2001 From: Viktor Dukhovni Date: Tue, 24 Jan 2023 14:40:57 +0100 Subject: [PATCH] Clarify the change of enc -S behavior in 3.0 Fixes #19730 Reviewed-by: Paul Dale Reviewed-by: Shane Lontis Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/19732) --- doc/man1/openssl-enc.pod.in | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/doc/man1/openssl-enc.pod.in b/doc/man1/openssl-enc.pod.in index cc04bf2d204..be66d07f5d5 100644 --- a/doc/man1/openssl-enc.pod.in +++ b/doc/man1/openssl-enc.pod.in @@ -256,6 +256,19 @@ All RC2 ciphers have the same key and effective key length. Blowfish and RC5 algorithms use a 128 bit key. +Please note that OpenSSL 3.0 changed the effect of the B<-S> option. +Any explicit salt value specified via this option is no longer prepended to the +ciphertext when encrypting, and must again be explicitly provided when decrypting. +Conversely, when the B<-S> option is used during decryption, the ciphertext +is expected to not have a prepended salt value. + +When using OpenSSL 3.0 or later to decrypt data that was encrypted with an +explicit salt under OpenSSL 1.1.1 do not use the B<-S> option, the salt will +then be read from the ciphertext. +To generate ciphertext that can be decrypted with OpenSSL 1.1.1 do not use +the B<-S> option, the salt will be then be generated randomly and prepended +to the output. + =head1 SUPPORTED CIPHERS Note that some of these ciphers can be disabled at compile time -- 2.47.2