RFC 3211: Password-based Encryption for CMS
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3369, RFC 3370.
Current document in this lineage: RFC 3370 — Cryptographic Message Syntax (CMS) Algorithms; RFC 5652 — Cryptographic Message Syntax (CMS)
In plain English — editorial summary, not part of the RFC
This document provides a method of encrypting data using user-supplied passwords and, by extension, any form of variable-length keying material which is not necessarily an algorithm-specific fixed-format key. The Cryptographic Message Syntax data format does not currently contain any provisions for password-based data encryption. [STANDARDS-TRACK]
Document record
- Document ID
- RFC3211
- Published
- December 2001
- Authors
- P. Gutmann
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 17
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 6 RFCs, each formally replacing the one before it.
Read the full history of Cryptographic Message Syntax (CMS) →
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3185Reuse of CMS Content Encryption KeysCurrent
October 2001
- RFC 2876Use of the KEA and SKIPJACK Algorithms in CMSCurrent
July 2000
- RFC 3218Preventing the Million Message Attack on Cryptographic Message SyntaxCurrent
January 2002
- RFC 3058Use of the IDEA Encryption Algorithm in CMSCurrent
February 2001
- 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 3259A Message Bus for Local CoordinationCurrent
May 2002
- RFC 6518Keying and Authentication for Routing Protocols (KARP) Design GuidelinesCurrent
February 2012
- RFC 3183Domain Security Services using S/MIMECurrent
October 2001
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?