Decryption must authenticate
05Recovering candidate plaintext is not enough: the authenticated-encryption check must succeed.
Related RFCs and changes
“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.
DIAGRAM§ 5.2 ↗
RFC 7516 · § 5.2EXAMPLE
3 / 3
03
Release or reject
Release plaintext only after every required check passes.
Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
Read the updated RFC section ↗
The consumer checks algorithm suitability and all required header parameters.
- The consumer checks algorithm suitability and all required header parameters.
- A failed tag must reject the encrypted object.
- Private keys and sensitive plaintext require protection outside the serialized format.
The illustration is schematic. Example values are illustrative; profiles and later security guidance can add requirements.
Read the RFC section ↗Diagrams simplify the RFC. Read the linked sections for complete requirements.
Privacy