RFC 2437: PKCS #1: RSA Cryptography Specifications Version 2.0
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3447.
Current document in this lineage: RFC 8017 — PKCS #1: RSA Cryptography Specifications Version 2.2
In plain English — editorial summary, not part of the RFC
This memo is the successor to RFC 2313. This document provides recommendations for the implementation of public-key cryptography based on the RSA algorithm. This memo provides information for the Internet community.
Document record
- Document ID
- RFC2437
- Published
- October 1998
- Authors
- B. Kaliski; J. Staddon
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 39
- Also known as
- —
Topics
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 2313 (1998)
- RFC 2437 (1998)
- RFC 3447 (2003)
- RFC 8017 (2016) ✓
Read the full history of PKCS #1: RSA Cryptography Specifications Version 2.2 →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2314PKCS #10: Certification Request Syntax Version 1.5Obsoleted
March 1998
- RFC 2986PKCS #10: Certification Request Syntax Specification Version 1.7Updated
November 2000
- RFC 2994A Description of the MISTY1 Encryption AlgorithmCurrent
November 2000
- RFC 1620Internet Architecture Extensions for Shared MediaCurrent
May 1994
- RFC 2469A Caution On The Canonical Ordering Of Link-Layer AddressesCurrent
December 1998
- RFC 2315PKCS #7: Cryptographic Message Syntax Version 1.5Current
March 1998
- RFC 2204ODETTE File Transfer ProtocolObsoleted
September 1997
- RFC 2756Hyper Text Caching Protocol (HTCP/0.0)Current
January 2000
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?