RFC 5035: Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility

In plain English — editorial summary, not part of the RFC

In the original Enhanced Security Services for S/MIME document (RFC 2634), a structure for cryptographically linking the certificate to be used in validation with the signature was introduced; this structure was hardwired to use SHA-1. This document allows for the structure to have algorithm agility and defines a new attribute for this purpose. [STANDARDS-TRACK]

Document record

Document ID

RFC5035

Published

August 2007

Authors

J. Schaad

Status

PROPOSED STANDARD

Stream

IETF

Area

sec

Pages

17

Also known as

—

Updates:

RFC 2634

• Read the full RFC text →
• Plain text version
• IETF Datatracker history
• DOI: 10.17487/RFC5035
• Reported errata exist →

Topics

• validation
• signature
• certificate

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

• RFC 4490Using the GOST 28147-89, GOST R 34.11-94, GOST R 34.10-94, and GOST R 34.10-2001 Algorithms with Cryptographic Message Syntax (CMS)Current

  May 2006

• RFC 3008Domain Name System Security (DNSSEC) Signing AuthorityObsoleted

  November 2000

• RFC 5750Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.2 Certificate HandlingObsoleted

  January 2010

• RFC 3850Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Certificate HandlingObsoleted

  July 2004

• RFC 3779X.509 Extensions for IP Addresses and AS IdentifiersCurrent

  June 2004

• RFC 3125Electronic Signature PoliciesCurrent

  September 2001

• RFC 2875Diffie-Hellman Proof-of-Possession AlgorithmsObsoleted

  July 2000

• RFC 7427Signature Authentication in the Internet Key Exchange Version 2 (IKEv2)Current

  January 2015

Also filed under

• PROPOSED STANDARD
• 2007
• IETF stream
• sec area