RFC 4270: Attacks on Cryptographic Hashes in Internet Protocols
In plain English — editorial summary, not part of the RFC
Recent announcements of better-than-expected collision attacks in popular hash algorithms have caused some people to question whether common Internet protocols need to be changed, and if so, how. This document summarizes the use of hashes in many protocols, discusses how the collision attacks affect and do not affect the protocols, shows how to thwart known attacks on digital certificates, and discusses future directions for protocol designers. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4270
- Published
- December 2005
- Authors
- P. Hoffman; B. Schneier
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 12
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 4293Management Information Base for the Internet Protocol (IP)Current
April 2006
- RFC 4301Security Architecture for the Internet ProtocolUpdated
December 2005
- RFC 4113Management Information Base for the User Datagram Protocol (UDP)Current
June 2005
- RFC 4460Stream Control Transmission Protocol (SCTP) Specification Errata and IssuesObsoleted
April 2006
- RFC 4019RObust Header Compression (ROHC): Profiles for User Datagram Protocol (UDP) LiteUpdated
April 2005
- RFC 3986Uniform Resource Identifier (URI): Generic SyntaxUpdated
January 2005
- RFC 4570Session Description Protocol (SDP) Source FiltersCurrent
July 2006
- RFC 4608Source-Specific Protocol Independent Multicast in 232/8Current
August 2006
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?