RFC 4634: US Secure Hash Algorithms (SHA and HMAC-SHA)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 6234.
Current version: RFC 6234 — US Secure Hash Algorithms (SHA and SHA-based HMAC and HKDF)
In plain English — editorial summary, not part of the RFC
The United States of America has adopted a suite of Secure Hash Algorithms (SHAs), including four beyond SHA-1, as part of a Federal Information Processing Standard (FIPS), specifically SHA-224 (RFC 3874), SHA-256, SHA-384, and SHA-512. The purpose of this document is to make source code performing these hash functions conveniently available to the Internet community. The sample code supports input strings of arbitrary bit length. SHA-1's sample code from RFC 3174 has also been updated to handle input strings of arbitrary bit length. Most of the text herein was adapted by the authors from FIPS 180-2. Code to perform SHA-based HMACs, with arbitrary bit length text, is also included. This memo provides information for the Internet community.
Document record
- Document ID
- RFC4634
- Published
- August 2006
- Authors
- D. Eastlake 3rd; T. Hansen
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- —
- Pages
- 108
- Also known as
- —
Topics
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 5754Using SHA2 Algorithms with Cryptographic Message SyntaxCurrent
January 2010
- RFC 5702Use of SHA-2 Algorithms with RSA in DNSKEY and RRSIG Resource Records for DNSSECUpdated
October 2009
- RFC 6594Use of the SHA-256 Algorithm with RSA, Digital Signature Algorithm (DSA), and Elliptic Curve DSA (ECDSA) in SSHFP Resource RecordsCurrent
April 2012
- RFC 6605Elliptic Curve Digital Signature Algorithm (DSA) for DNSSECCurrent
April 2012
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?