RFC 5752: Multiple Signatures in Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
Cryptographic Message Syntax (CMS) SignedData includes the SignerInfo structure to convey per-signer information. SignedData supports multiple signers and multiple signature algorithms per signer with multiple SignerInfo structures. If a signer attaches more than one SignerInfo, there are concerns that an attacker could perform a downgrade attack by removing the SignerInfo(s) with the \'strong' algorithm(s). This document defines the multiple-signatures attribute, its generation rules, and its processing rules to allow signers to convey multiple SignerInfo objects while protecting against downgrade attacks. Additionally, this attribute may assist during periods of algorithm migration. [STANDARDS-TRACK]
Document record
- Document ID
- RFC5752
- Published
- January 2010
- Authors
- S. Turner; J. Schaad
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 17
- Also known as
- —
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 6019BinaryTime: An Alternate Format for Representing Date and Time in ASN.1Current
September 2010
- RFC 4049BinaryTime: An Alternate Format for Representing Date and Time in ASN.1Obsoleted
April 2005
- RFC 5753Use of Elliptic Curve Cryptography (ECC) Algorithms in Cryptographic Message Syntax (CMS)Current
January 2010
- RFC 5751Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Message SpecificationObsoleted
January 2010
- RFC 5754Using SHA2 Algorithms with Cryptographic Message SyntaxCurrent
January 2010
- RFC 5750Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate HandlingObsoleted
January 2010
- RFC 5749Distribution of EAP-Based Keys for Handover and Re-AuthenticationCurrent
March 2010
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?