From: Patrick J. LoPresti Date: Tue, 17 Dec 2024 23:46:04 +0000 (-0800) Subject: doc: Correctly reflect parameter constraints in EVP_DecryptUpdate() X-Git-Tag: openssl-3.5.0-alpha1~814 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=982a9b8bee3ee715cb5c7f160b14bd2122af0388;p=thirdparty%2Fopenssl.git doc: Correctly reflect parameter constraints in EVP_DecryptUpdate() Fixes #26169 CLA: trivial Reviewed-by: Paul Dale Reviewed-by: Tomas Mraz (Merged from https://github.com/openssl/openssl/pull/26202) --- diff --git a/doc/man3/EVP_EncryptInit.pod b/doc/man3/EVP_EncryptInit.pod index f388a0a9c3d..1a1e4cf1e43 100644 --- a/doc/man3/EVP_EncryptInit.pod +++ b/doc/man3/EVP_EncryptInit.pod @@ -439,10 +439,7 @@ and EVP_DecryptFinal_ex() These functions are the corresponding decryption operations. EVP_DecryptFinal() will return an error code if padding is enabled and the final block is not correctly formatted. The parameters and restrictions are -identical to the encryption operations except that if padding is enabled the -decrypted data buffer I passed to EVP_DecryptUpdate() should have -sufficient room for (I + cipher_block_size) bytes unless the cipher block -size is 1 in which case I bytes is sufficient. I B be NULL. +identical to the encryption operations. I B be NULL. =item EVP_CipherInit_ex2(), EVP_CipherInit_ex(), EVP_CipherUpdate() and EVP_CipherFinal_ex()