Skip to content

Commit

Permalink
doc: clarify authenticity of plaintexts in update
Browse files Browse the repository at this point in the history
PR-URL: #53784
Reviewed-By: Filip Skokan <panva.ip@gmail.com>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Marco Ippolito <marcoippolito54@gmail.com>
  • Loading branch information
tniessen authored Jul 11, 2024
1 parent 096e44a commit 3a3dfbd
Showing 1 changed file with 5 additions and 0 deletions.
5 changes: 5 additions & 0 deletions doc/api/crypto.md
Original file line number Diff line number Diff line change
Expand Up @@ -980,6 +980,11 @@ The `decipher.update()` method can be called multiple times with new data until
[`decipher.final()`][] is called. Calling `decipher.update()` after
[`decipher.final()`][] will result in an error being thrown.

Even if the underlying cipher implements authentication, the authenticity and
integrity of the plaintext returned from this function may be uncertain at this
time. For authenticated encryption algorithms, authenticity is generally only
established when the application calls [`decipher.final()`][].

## Class: `DiffieHellman`

<!-- YAML
Expand Down

0 comments on commit 3a3dfbd

Please sign in to comment.