RFC 8933: Update to the Cryptographic Message Syntax (CMS) for Algorithm Identifier Protection
In plain English — editorial summary, not part of the RFC
This document updates the Cryptographic Message Syntax (CMS) specified in RFC 5652 to ensure that algorithm identifiers in signed-data and authenticated-data content types are adequately protected.
Document record
- Document ID
- RFC8933
- Published
- October 2020
- Authors
- R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 8
- Also known as
- —
- Updates:
- RFC 5652
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4853Cryptographic Message Syntax (CMS) Multiple Signer ClarificationCurrent
April 2007
- RFC 3852Cryptographic Message Syntax (CMS)Obsoleted
July 2004
- RFC 3370Cryptographic Message Syntax (CMS) AlgorithmsUpdated
September 2002
- RFC 3369Cryptographic Message Syntax (CMS)Obsoleted
September 2002
- RFC 8437IMAP UNAUTHENTICATE Extension for Connection ReuseCurrent
August 2018
- RFC 8935Push-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8936Poll-Based Security Event Token (SET) Delivery Using HTTPCurrent
November 2020
- RFC 8940Extensible Authentication Protocol (EAP) Session-Id Derivation for EAP Subscriber Identity Module (EAP-SIM), EAP Authentication and Key Agreement (EAP-AKA), and Protected EAP (PEAP)Current
October 2020
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?