diff options
| author | Enji Cooper <ngie@FreeBSD.org> | 2025-03-14 06:40:59 +0000 |
|---|---|---|
| committer | Philip Paeps <philip@FreeBSD.org> | 2025-04-10 14:38:58 +0000 |
| commit | 862cd6b8fa9df7057bad47d01ccaf36a959e9166 (patch) | |
| tree | 35bd6034ae1e5396fb6420037f2f8ba1b19ef588 /crypto/openssl/doc/man3/EVP_EncryptInit.pod | |
| parent | 4651d400f1000834365a21c59d6803da4474c63e (diff) | |
openssl: Import OpenSSL 3.0.16
This release incorporates the following bug fixes and mitigations:
- [CVE-2024-13176](https://www.openssl.org/news/vulnerabilities.html#CVE-2024-13176
- [CVE-2024-9143](https://www.openssl.org/news/vulnerabilities.html#CVE-2024-9143)
Release notes can be found at:
https://openssl-library.org/news/openssl-3.0-notes/index.html
Approved by: so
Security: FreeBSD-EN-25:07.openssl
Differential Revision: https://reviews.freebsd.org/D49296
Differential Revision: https://reviews.freebsd.org/D49297
(cherry picked from commit 0d0c8621fd181e507f0fb50ffcca606faf66a8c2)
(cherry picked from commit cb29db243bd09d16604435639ae43ef7af0ea254)
(cherry picked from commit d2a55e6a9348bb55038dbc6b727ab041085f22db)
(cherry picked from commit 0d61082e3c64a43f52ec5f1bf3d85671d97d9514)
Diffstat (limited to 'crypto/openssl/doc/man3/EVP_EncryptInit.pod')
| -rw-r--r-- | crypto/openssl/doc/man3/EVP_EncryptInit.pod | 16 |
1 files changed, 12 insertions, 4 deletions
diff --git a/crypto/openssl/doc/man3/EVP_EncryptInit.pod b/crypto/openssl/doc/man3/EVP_EncryptInit.pod index f037d135c9da..a4635f994c2f 100644 --- a/crypto/openssl/doc/man3/EVP_EncryptInit.pod +++ b/crypto/openssl/doc/man3/EVP_EncryptInit.pod @@ -1284,6 +1284,15 @@ indicates whether the operation was successful. If it does not indicate success, the authentication operation has failed and any output data B<MUST NOT> be used as it is corrupted. +Please note that the number of authenticated bytes returned by +EVP_CipherUpdate() depends on the cipher used. Stream ciphers, such as ChaCha20 +or ciphers in GCM mode, can handle 1 byte at a time, resulting in an effective +"block" size of 1. Conversely, ciphers in OCB mode must process data one block +at a time, and the block size is returned. + +Regardless of the returned size, it is safe to pass unpadded data to an +EVP_CipherUpdate() call in a single operation. + =head2 GCM and OCB Modes The following I<ctrl>s are supported in GCM and OCB modes. @@ -1319,10 +1328,9 @@ For GCM, this call is only valid when decrypting data. For OCB, this call is valid when decrypting data to set the expected tag, and when encrypting to set the desired tag length. -In OCB mode, calling this when encrypting with C<tag> set to C<NULL> sets the -tag length. The tag length can only be set before specifying an IV. If this is -not called prior to setting the IV during encryption, then a default tag length -is used. +In OCB mode, calling this with C<tag> set to C<NULL> sets the tag length. +The tag length can only be set before specifying an IV. If this is not called +prior to setting the IV, then a default tag length is used. For OCB AES, the default tag length is 16 (i.e. 128 bits). It is also the maximum tag length for OCB. |
