Template:Infobox cryptographic hash function In cryptography, SHA1 is a cryptographic hash function designed by the National Security Agency (NSA) and published by the NIST as a U.S. Federal Information Processing Standard. SHA stands for Secure Hash Algorithm. The three SHA algorithms are structured differently and are distinguished as SHA0, SHA1, and SHA2. SHA1 is very similar to SHA0, but corrects an error in the original SHA hash specification that led to significant weaknesses. The SHA0 algorithm was not adopted by many applications. SHA2 on the other hand significantly differs from the SHA1 hash function.
SHA1 is the most widely used of the existing SHA hash functions, and is employed in several widelyused security applications and protocols. In 2005, security flaws were identified in SHA1, namely that a mathematical weakness might exist, indicating that a stronger hash function would be desirable.^{[1]} Although no successful attacks have yet been reported on the SHA2 variants, they are algorithmically similar to SHA1 and so efforts are underway to develop improved alternatives.^{[2]}^{[3]} A new hash standard, SHA3, is currently under development — an ongoing NIST hash function competition is scheduled to end with the selection of a winning function in 2012.
The SHA1 hash function[]
SHA1 produces a 160bit message digest based on principles similar to those used by Ronald L. Rivest of MIT in the design of the MD4 and MD5 message digest algorithms, but has a more conservative design.
The original specification of the algorithm was published in 1993 as the Secure Hash Standard, FIPS PUB 180, by US government standards agency NIST (National Institute of Standards and Technology). This version is now often referred to as SHA0. It was withdrawn by NSA shortly after publication and was superseded by the revised version, published in 1995 in FIPS PUB 1801 and commonly referred to as SHA1. SHA1 differs from SHA0 only by a single bitwise rotation in the message schedule of its compression function; this was done, according to NSA, to correct a flaw in the original algorithm which reduced its cryptographic security. However, NSA did not provide any further explanation or identify the flaw that was corrected. Weaknesses have subsequently been reported in both SHA0 and SHA1. SHA1 appears to provide greater resistance to attacks, supporting the NSA’s assertion that the change increased the security.
Template:
Comparison of SHA functions[]
In the table below, internal state means the “internal hash sum” after each compression of a data block. Template:See
Algorithm and variant  Output size (bits) 
Internal state size (bits) 
Block size (bits) 
Max message size (bits) 
Word size (bits) 
Rounds  Operations  Collisions found?  

SHA0  160  160  512  2^{64} − 1  32  80  +,and,or,xor,rot  Yes  
SHA1  No ^{[4]}  
SHA2  SHA256/224  256/224  256  512  2^{64} − 1  32  64  +,and,or,xor,shr,rot  No 
SHA512/384  512/384  512  1024  2^{128} − 1  64  80 
Applications[]
Template:Details SHA1 forms part of several widelyused security applications and protocols, including TLS and SSL, PGP, SSH, S/MIME, and IPsec. Those applications can also use MD5; both MD5 and SHA1 are descended from MD4. SHA1 hashing is also used in distributed revision control systems such as Git, Mercurial, and Monotone to identify revisions, and to detect data corruption or tampering. The algorithm has also been used on Nintendo console Wii for signature verification during boot but a significant implementation flaw allowed an attacker to bypass the security scheme.^{[5]}
SHA1 and SHA2 are the secure hash algorithms required by law for use in certain U.S. Government applications, including use within other cryptographic algorithms and protocols, for the protection of sensitive unclassified information. FIPS PUB 1801 also encouraged adoption and use of SHA1 by private and commercial organizations. SHA1 is being retired for most government uses; the U.S. National Institute of Standards and Technology says, "Federal agencies should stop using SHA1 for...applications that require collision resistance as soon as practical, and must use the SHA2 family of hash functions for these applications after 2010" (emphasis in original).^{[6]}
A prime motivation for the publication of the Secure Hash Algorithm was the Digital Signature Standard, in which it is incorporated.
The SHA hash functions have been used as the basis for the SHACAL block ciphers.
Cryptanalysis and validation[]
For a hash function for which L is the number of bits in the message digest, finding a message that corresponds to a given message digest can always be done using a brute force search in 2^{L} evaluations. This is called a preimage attack and may or may not be practical depending on L and the particular computing environment. The second criterion, finding two different messages that produce the same message digest, known as a collision, requires on average only 2^{L/2} evaluations using a birthday attack. For the latter reason the strength of a hash function is usually compared to a symmetric cipher of half the message digest length. Thus SHA1 was originally thought to have 80bit strength.
Cryptographers have produced collision pairs for SHA0 and have found algorithms that should produce SHA1 collisions in far fewer than the originally expected 2^{80} evaluations.
In terms of practical security, a major concern about these new attacks is that they might pave the way to more efficient ones. Whether this is the case has yet to be seen, but a migration to stronger hashes is believed to be prudent. Some of the applications that use cryptographic hashes, such as password storage, are only minimally affected by a collision attack. Constructing a password that works for a given account requires a preimage attack, as well as access to the hash of the original password, which may or may not be trivial. Reversing password encryption (e.g. to obtain a password to try against a user's account elsewhere) is not made possible by the attacks. (However, even a secure password hash can't prevent bruteforce attacks on weak passwords.)
In the case of document signing, an attacker could not simply fake a signature from an existing document—the attacker would have to produce a pair of documents, one innocuous and one damaging, and get the private key holder to sign the innocuous document. There are practical circumstances in which this is possible; until the end of 2008, it was possible to create forged SSL certificates using an MD5 collision.^{[7]}
SHA0[]
At CRYPTO 98, two French researchers, Florent Chabaud and Antoine Joux, presented an attack on SHA0 (Chabaud and Joux, 1998): collisions can be found with complexity 2^{61}, fewer than the 2^{80} for an ideal hash function of the same size.
In 2004, Biham and Chen found nearcollisions for SHA0—two messages that hash to nearly the same value; in this case, 142 out of the 160 bits are equal. They also found full collisions of SHA0 reduced to 62 out of its 80 rounds.
Subsequently, on 12 August 2004, a collision for the full SHA0 algorithm was announced by Joux, Carribault, Lemuet, and Jalby. This was done by using a generalization of the Chabaud and Joux attack. Finding the collision had complexity 2^{51} and took about 80,000 CPU hours on a supercomputer with 256 Itanium 2 processors. (Equivalent to 13 days of fulltime use of the computer.)
On 17 August 2004, at the Rump Session of CRYPTO 2004, preliminary results were announced by Wang, Feng, Lai, and Yu, about an attack on MD5, SHA0 and other hash functions. The complexity of their attack on SHA0 is 2^{40}, significantly better than the attack by Joux et al. ^{[8]}^{[9]}
In February 2005, an attack by Xiaoyun Wang, Yiqun Lisa Yin, and Hongbo Yu was announced which could find collisions in SHA0 in 2^{39} operations.^{[10]}^{[11]}
SHA1[]
In light of the results for SHA0, some experts suggested that plans for the use of SHA1 in new cryptosystems should be reconsidered. After the CRYPTO 2004 results were published, NIST announced that they planned to phase out the use of SHA1 by 2010 in favor of the SHA2 variants.^{[12]}
In early 2005, Rijmen and Oswald published an attack on a reduced version of SHA1—53 out of 80 rounds—which finds collisions with a computational effort of fewer than 2^{80} operations.^{[13]}
In February 2005, an attack by Xiaoyun Wang, Yiqun Lisa Yin, Bayarjargal, and Hongbo Yu was announced.^{[10]} The attacks can find collisions in the full version of SHA1, requiring fewer than 2^{69} operations. (A bruteforce search would require 2^{80} operations.)
The authors write: "In particular, our analysis is built upon the original differential attack on SHA0 [sic], the near collision attack on SHA0, the multiblock collision techniques, as well as the message modification techniques used in the collision search attack on MD5. Breaking SHA1 would not be possible without these powerful analytical techniques."^{[14]} The authors have presented a collision for 58round SHA1, found with 2^{33} hash operations. The paper with the full attack description was published in August 2005 at the CRYPTO conference.
In an interview, Yin states that, "Roughly, we exploit the following two weaknesses: One is that the file preprocessing step is not complicated enough; another is that certain math operations in the first 20 rounds have unexpected security problems."^{[15]}
On 17 August 2005, an improvement on the SHA1 attack was announced on behalf of Xiaoyun Wang, Andrew Yao and Frances Yao at the CRYPTO 2005 rump session, lowering the complexity required for finding a collision in SHA1 to 2^{63}.^{[16]} On 18 December 2007 the details of this result were explained and verified by Martin Cochran.^{[17]}
Christophe De Cannière and Christian Rechberger further improved the attack on SHA1 in "Finding SHA1 Characteristics: General Results and Applications,"^{[18]} receiving the Best Paper Award at ASIACRYPT 2006. A twoblock collision for 64round SHA1 was presented, found using unoptimized methods with 2^{35} compression function evaluations. As this attack requires the equivalent of about 2^{35} evaluations, it is considered to be a significant theoretical break.^{[19]} Their attack was extended further to 73 rounds (of 80) in 2010 by Grechnikov.^{[20]} In order to find an actual collision in the full 80 rounds of the hash function, however, massive amounts of computer time are required. To that end, a collision search for SHA1 using the distributed computing platform BOINC began August 8, 2007, organized by the Graz University of Technology. The effort was abandoned May 12, 2009 due to lack of progress.^{[21]}
At the Rump Session of CRYPTO 2006, Christian Rechberger and Christophe De Cannière claimed to have discovered a collision attack on SHA1 that would allow an attacker to select at least parts of the message.^{[22]}^{[23]}
Cameron McDonald, Philip Hawkes and Josef Pieprzyk presented a hash collision attack with claimed complexity 2^{52} at the Rump session of Eurocrypt 2009.^{[24]} However, the accompanying paper, "Differential Path for SHA1 with complexity O(2^{52})" has been withdrawn due to the authors' discovery that their estimate was incorrect.^{[25]}
Official validation[]
 Main article: CMVP
Implementations of all FIPSapproved security functions can be officially validated through the CMVP program, jointly run by the National Institute of Standards and Technology (NIST) and the Communications Security Establishment (CSE). For informal verification, a package to generate a high number of test vectors is made available for download on the NIST site; the resulting verification however does not replace in any way the formal CMVP validation, which is required by law for certain applications.
As of 2006 , there are more than 500 validated implementations of SHA1, with fewer than ten of them capable of handling messages with a length in bits not a multiple of eight (see SHS Validation List).
Examples and pseudocode[]
Example hashes[]
 Main article: Examples of SHA digests
The following is an example of SHA1 digests. ASCII encoding is assumed for all messages.
SHA1("The quick brown fox jumps over the lazy dog")
= 2fd4e1c6 7a2d28fc ed849ee1 bb76e739 1b93eb12
Even a small change in the message will, with overwhelming probability, result in a completely different hash due to the avalanche effect. For example, changing dog
to cog
produces a hash with different values for 81 of the 160 bits:
SHA1("The quick brown fox jumps over the lazy cog") = de9f2c7f d25e1b3a fad3e85a 0bd17d9b 100db4b3
SHA1 pseudocode[]
Pseudocode for the SHA1 algorithm follows:
Note 1: All variables are unsigned 32 bits and wrap modulo 2^{32} when calculating Note 2: All constants in this pseudo code are in big endian. Within each word, the most significant byte is stored in the leftmost byte position Initialize variables: h0 = 0x67452301 h1 = 0xEFCDAB89 h2 = 0x98BADCFE h3 = 0x10325476 h4 = 0xC3D2E1F0 Preprocessing: append the bit '1' to the message append 0 ≤ k < 512 bits '0', so that the resulting message length (in bits) is congruent to 448 ≡ −64 (mod 512) append length of message (before preprocessing), in bits, as 64bit bigendian integer Process the message in successive 512bit chunks: break message into 512bit chunks for each chunk break chunk into sixteen 32bit bigendian words w[i], 0 ≤ i ≤ 15 Extend the sixteen 32bit words into eighty 32bit words: for i from 16 to 79 w[i] = (w[i3] xor w[i8] xor w[i14] xor w[i16]) leftrotate 1 Initialize hash value for this chunk: a = h0 b = h1 c = h2 d = h3 e = h4 Main loop: ^{[26]} for i from 0 to 79 if 0 ≤ i ≤ 19 then f = (b and c) or ((not b) and d) k = 0x5A827999 else if 20 ≤ i ≤ 39 f = b xor c xor d k = 0x6ED9EBA1 else if 40 ≤ i ≤ 59 f = (b and c) or (b and d) or (c and d) k = 0x8F1BBCDC else if 60 ≤ i ≤ 79 f = b xor c xor d k = 0xCA62C1D6 temp = (a leftrotate 5) + f + e + k + w[i] e = d d = c c = b leftrotate 30 b = a a = temp Add this chunk's hash to result so far: h0 = h0 + a h1 = h1 + b h2 = h2 + c h3 = h3 + d h4 = h4 + e Produce the final hash value (bigendian): digest = hash = h0 append h1 append h2 append h3 append h4
The constant values used are chosen as nothing up my sleeve numbers: the four round constants k
are 2^{30} times the square roots of 2, 3, 5 and 10 The first four starting values for h0
through h3
are the same as the MD5 algorithm, and the fifth (for h4
) is similar.
Instead of the formulation from the original FIPS PUB 1801 shown, the following equivalent expressions may be used to compute f
in the main loop above:
(0 ≤ i ≤ 19): f = d xor (b and (c xor d)) (alternative 1) (0 ≤ i ≤ 19): f = (b and c) xor ((not b) and d) (alternative 2) (0 ≤ i ≤ 19): f = (b and c) + ((not b) and d) (alternative 3) (0 ≤ i ≤ 19): f = vec_sel(d, c, b) (alternative 4) (40 ≤ i ≤ 59): f = (b and c) or (d and (b or c)) (alternative 1) (40 ≤ i ≤ 59): f = (b and c) or (d and (b xor c)) (alternative 2) (40 ≤ i ≤ 59): f = (b and c) + (d and (b xor c)) (alternative 3) (40 ≤ i ≤ 59): f = (b and c) xor (b and d) xor (c and d) (alternative 4)
Max Locktyukhin has also shown^{[27]} that that for the rounds 32–79 the computation of:
w[i] = (w[i3] xor w[i8] xor w[i14] xor w[i16]) leftrotate 1
can be replaced with:
w[i] = (w[i6] xor w[i16] xor w[i28] xor w[i32]) leftrotate 2
This transformation keeps all operands 64bit aligned and, by removing the dependency of w[i]
on w[i3]
, allows efficient SIMD implementation with a vector length of 4 such as x86 SSE instructions.
See also[]
 Comparison of cryptographic hash functions
 Digital timestamping
 Hash collision
 Hashcash
 International Association for Cryptologic Research (IACR)
 RIPEMD160
 Secure Hash Standard
 sha1sum
 Tiger
 Whirlpool
References[]
Template:Refbegin
 ↑ Schneier on Security: Cryptanalysis of SHA1
 ↑ Schneier on Security: NIST Hash Workshop Liveblogging (5)
 ↑ Hash cracked – heise Security
 ↑ Classification and Generation of Disturbance Vectors for Collision Attacks against SHA1
 ↑ http://debugmo.de/?p=61 Debugmo.de "For verifiying the hash (which is the only thing they verify in the signature), they have chosen to use a function (strncmp) which stops on the first nullbyte – with a positive result. Out of the 160 bits of the SHA1hash, up to 152 bits are thrown away."
 ↑ National Institute on Standards and Technology Computer Security Resource Center, NIST's Policy on Hash Functions, accessed March 29, 2009.
 ↑ Alexander Sotirov, Marc Stevens, Jacob Appelbaum, Arjen Lenstra, David Molnar, Dag Arne Osvik, Benne de Weger, MD5 considered harmful today: Creating a rogue CA certificate, accessed March 29, 2009
 ↑ Freedom to Tinker » Blog Archive » Report from Crypto 2004
 ↑ Google.com
 ↑ ^{10.0} ^{10.1} Schneier on Security: SHA1 Broken
 ↑ Template:Zh icon Sdu.edu.cn, Shandong University
 ↑ National Institute of Standards and Technology
 ↑ Cryptology ePrint Archive
 ↑ MIT.edu, Massachusetts Institute of Technology
 ↑ Fixing a hole in security  Tech News on ZDNet
 ↑ Schneier on Security: New Cryptanalytic Results Against SHA1
 ↑ Notes on the Wang et al. $2^{63}$ SHA1 Differential Path
 ↑ Template:Cite journal
 ↑ Template:Cite web
 ↑ Template:Cite web
 ↑ Template:Cite web
 ↑ SHA1 hash function under pressure – heise Security
 ↑ Crypto 2006 Rump Schedule
 ↑ SHA1 collisions now 2^52
 ↑ International Association for Cryptologic Research
 ↑ http://www.faqs.org/rfcs/rfc3174.html
 ↑ Template:Citation
 Florent Chabaud, Antoine Joux: Differential Collisions in SHA0. CRYPTO 1998. pp56–71
 Eli Biham, Rafi Chen, NearCollisions of SHA0, Cryptology ePrint Archive, Report 2004/146, 2004 (appeared on CRYPTO 2004), IACR.org
 Xiaoyun Wang, Hongbo Yu and Yiqun Lisa Yin, Efficient Collision Search Attacks on SHA0, CRYPTO 2005, CMU.edu
 Xiaoyun Wang, Yiqun Lisa Yin and Hongbo Yu, Finding Collisions in the Full SHA1, Crypto 2005 MIT.edu
 Henri Gilbert, Helena Handschuh: Security Analysis of SHA256 and Sisters. Selected Areas in Cryptography 2003: pp175–193
 Template:Cite journal
Template:Refend
External links[]
Standards: SHA1, SHA2[]
 Specifications for a Secure Hash Standard (SHS) – Draft for proposed SHS (SHA0)
 Secure Hash Standard (SHS) – Proposed SHS (SHA0)
 CSRC Cryptographic Toolkit – Official NIST site for the Secure Hash Standard
 FIPS 1802: Secure Hash Standard (SHS) (PDF, 236 kB) – Current version of the Secure Hash Standard (SHA1, SHA224, SHA256, SHA384, and SHA512), 1 August 2002, amended 25 February 2004
 RFC 3174 (with sample C implementation)
Cryptanalysis[]
 Interview with Yiqun Lisa Yin concerning the attack on SHA1
 Lenstra's Summary of impact of the February 2005 cryptanalytic results
 Explanation of the successful attacks on SHA1 (3 pages, 2006)
 Cryptography Research – Hash Collision Q&A
 Online SHA1 hash crack using Rainbow tables
 Hash Project Web Site: software and hardwarebased cryptanalysis of SHA1
Implementations[]
 Libgcrypt
 A general purpose cryptographic library based on the code from GNU Privacy Guard.
 OpenSSL
 The widely used OpenSSL
crypto
library includes free, opensource – implementations of SHA1, SHA224, SHA256, SHA384, and SHA512  Crypto++
 A public domain C++ class library of cryptographic schemes, including implementations of the SHA1, SHA224, SHA256, SHA384, and SHA512 algorithms.
 Bouncy Castle
 The Bouncy Castle Library is a free Java and C# class library that contains implementations of the SHA1, SHA224, SHA256, SHA384 and SHA512 algorithms as well as other algorithms like Whirlpool, Tiger, RIPEMD, GOST3411, MD2, MD4 and MD5.
 jsSHA
 A crossbrowser JavaScript library for clientside calculation of SHA digests, despite the fact that JavaScript does not natively support the 64bit operations required for SHA384 and SHA512.
 LibTomCrypt
 A portable ISO C cryptographic toolkit, Public Domain.
 Intel
 Fast implementation of SHA1 using Intel Supplemental SSE3 extensions, free for commercial or noncommercial use.
 md5deep
 A set of programs to compute MD5, SHA1, SHA256, Tiger, or Whirlpool cryptographic message digests on an arbitrary number of files. It is used in computer security, system administration and computer forensics communities for purposes of running large numbers of files through any of several different cryptographic digests. It is similar to the md5sum.

bg:SHA cs:Secure Hash Algorithm da:SHA de:Secure Hash Algorithm es:Secure Hash Algorithm fr:SHA1 ko:SHA hr:SHA1 it:Secure Hash Algorithm he:SHA lt:SHA nl:SHAfamilie ja:SHA no:SHA Sjekksum Funksjoner pl:SHA1 pt:SHA1 ru:SHA1 simple:SHA hash functions sk:Secure Hash Algorithm sr:SHA fi:SHA sv:SHA1 tr:SHA1 vi:SHA zh:SHA家族