RFC 4853: Cryptographic Message Syntax (CMS) Multiple Signer Clarification
In plain English — editorial summary, not part of the RFC
This document updates the Cryptographic Message Syntax (CMS), which is published in RFC 3852. This document clarifies the proper handling of the SignedData protected content type when more than one digital signature is present. [STANDARDS-TRACK]
Document record
- Document ID
- RFC4853
- Published
- April 2007
- Authors
- R. Housley
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 5
- Also known as
- —
- Updates:
- RFC 3852
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3370Cryptographic Message Syntax (CMS) AlgorithmsUpdated
September 2002
- RFC 3369Cryptographic Message Syntax (CMS)Obsoleted
September 2002
- RFC 8933Update to the Cryptographic Message Syntax (CMS) for Algorithm Identifier ProtectionCurrent
October 2020
- RFC 5752Multiple Signatures in Cryptographic Message Syntax (CMS)Current
January 2010
- RFC 9788Header Protection for Cryptographically Protected EmailCurrent
August 2025
- RFC 4049BinaryTime: An Alternate Format for Representing Date and Time in ASN.1Obsoleted
April 2005
- RFC 6019BinaryTime: An Alternate Format for Representing Date and Time in ASN.1Current
September 2010
- RFC 8437IMAP UNAUTHENTICATE Extension for Connection ReuseCurrent
August 2018
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?