Development[edit] One iteration within the SHA-1 compression function: A, B, C, D and E are 32-bit words of the state; F is a nonlinear function that varies; n denotes a left bit rotation by n places; n varies for each operation; Wt is the expanded message word of round t; Kt is the round constant of round t; denotes addition modulo 232. SHA-1 produces a 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. SHA-1 was developed as part of the U.S. Government's Capstone project.[17] The original specification of the algorithm was published in 1993 under the title Secure Hash Standard, FIPS PUB 180, by U.S. government standards agency NIST (National Institute of Standards and Technology).[18][19] This version is now often named SHA-0. It was withdrawn by the NSA shortly after publication and was superseded by the revised version, published in 1995 in FIPS PUB 180-1 and commonly designated SHA-1. SHA-1 differs from SHA-0 only by a single bitwise rotation in the message schedule of its compression function. According to the NSA, this was done to correct a flaw in the original algorithm which reduced its cryptographic security, but they did not provide any further explanation.[citation needed] Publicly available techniques did indeed compromise SHA-0 before SHA-1.[citation needed]

Applications[edit] Cryptography[edit] Further information: Cryptographic hash function § Applications SHA-1 forms part of several widely used security applications and protocols, including TLS and SSL, PGP, SSH, S/MIME, and IPsec. Those applications can also use MD5; both MD5 and SHA-1 are descended from MD4. The algorithm has also been used on Nintendo's Wii gaming console for signature verification when booting, but a significant flaw in the first implementations of the firmware allowed for an attacker to bypass the system's security scheme.[20] SHA-1 and SHA-2 are the 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 180-1 also encouraged adoption and use of SHA-1 by private and commercial organizations. SHA-1 is being retired from most government uses; the U.S. National Institute of Standards and Technology said, "Federal agencies should stop using SHA-1 for...applications that require collision resistance as soon as practical, and must use the SHA-2 family of hash functions for these applications after 2010" (emphasis in original),[21] though that was later relaxed.[22] 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 for the basis of the SHACAL block ciphers. Data integrity[edit] Revision control systems such as Git, Mercurial, and Monotone use SHA-1 not for security but to identify revisions and to ensure that the data has not changed due to accidental corruption. Linus Torvalds said about Git: If you have disk corruption, if you have DRAM corruption, if you have any kind of problems at all, Git will notice them. It's not a question of if, it's a guarantee. You can have people who try to be malicious. They won't succeed. ... Nobody has been able to break SHA-1, but the point is the SHA-1, as far as Git is concerned, isn't even a security feature. It's purely a consistency check. The security parts are elsewhere, so a lot of people assume that since Git uses SHA-1 and SHA-1 is used for cryptographically secure stuff, they think that, Okay, it's a huge security feature. It has nothing at all to do with security, it's just the best hash you can get. ... I guarantee you, if you put your data in Git, you can trust the fact that five years later, after it was converted from your hard disk to DVD to whatever new technology and you copied it along, five years later you can verify that the data you get back out is the exact same data you put in. ... One of the reasons I care is for the kernel, we had a break in on one of the BitKeeper sites where people tried to corrupt the kernel source code repositories.[23] However Git does not require the second preimage resistance of SHA-1 as a security feature, since it will always prefer to keep the earliest version of an object in case of collision, preventing an attacker from surreptitiously overwriting files.[24]

Cryptanalysis and validation[edit] 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 approximately 2L evaluations. This is called a preimage attack and may or may not be practical depending on L and the particular computing environment. However, a collision, consisting of finding two different messages that produce the same message digest, requires on average only about 1.2 × 2L/2 evaluations using a birthday attack. Thus the strength of a hash function is usually compared to a symmetric cipher of half the message digest length. SHA-1, which has a 160-bit message digest, was originally thought to have 80-bit strength. In 2005, cryptographers Xiaoyun Wang, Yiqun Lisa Yin, and Hongbo Yu produced collision pairs for SHA-0 and have found algorithms that should produce SHA-1 collisions in far fewer than the originally expected 280 evaluations.[25] 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 is yet to be seen, but a migration to stronger hashes is believed[by whom?] to be prudent. Some of the applications that use cryptographic hashes, like 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 brute-force 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.[26] Due to the block and iterative structure of the algorithms and the absence of additional final steps, all SHA functions (except SHA-3[27]) are vulnerable to length-extension and partial-message collision attacks.[28] These attacks allow an attacker to forge a message signed only by a keyed hash—SHA(message || key) or SHA(key || message)—by extending the message and recalculating the hash without knowing the key. A simple improvement to prevent these attacks is to hash twice: SHAd(message) = SHA(SHA(0b || message)) (the length of 0b, zero block, is equal to the block size of the hash function). Attacks[edit] In early 2005, Rijmen and Oswald published an attack on a reduced version of SHA-1—53 out of 80 rounds—which finds collisions with a computational effort of fewer than 280 operations.[29] In February 2005, an attack by Xiaoyun Wang, Yiqun Lisa Yin, and Hongbo Yu was announced.[30] The attacks can find collisions in the full version of SHA-1, requiring fewer than 269 operations. (A brute-force search would require 280 operations.) The authors write: "In particular, our analysis is built upon the original differential attack on SHA-0, the near collision attack on SHA-0, the multiblock collision techniques, as well as the message modification techniques used in the collision search attack on MD5. Breaking SHA-1 would not be possible without these powerful analytical techniques."[31] The authors have presented a collision for 58-round SHA-1, found with 233 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."[32] On 17 August 2005, an improvement on the SHA-1 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 SHA-1 to 263.[33] On 18 December 2007 the details of this result were explained and verified by Martin Cochran.[34] Christophe De Cannière and Christian Rechberger further improved the attack on SHA-1 in "Finding SHA-1 Characteristics: General Results and Applications,"[35] receiving the Best Paper Award at ASIACRYPT 2006. A two-block collision for 64-round SHA-1 was presented, found using unoptimized methods with 235 compression function evaluations. Since this attack requires the equivalent of about 235 evaluations, it is considered to be a significant theoretical break.[36] Their attack was extended further to 73 rounds (of 80) in 2010 by Grechnikov.[37] In order to find an actual collision in the full 80 rounds of the hash function, however, tremendous amounts of computer time are required. To that end, a collision search for SHA-1 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.[38] At the Rump Session of CRYPTO 2006, Christian Rechberger and Christophe De Cannière claimed to have discovered a collision attack on SHA-1 that would allow an attacker to select at least parts of the message.[39][40] In 2008, an attack methodology by Stéphane Manuel reported hash collisions with an estimated theoretical complexity of 251 to 257 operations.[41] However he later retracted that claim after finding that local collision paths were not actually independent, and finally quoting for the most efficient a collision vector that was already known before this work.[42] Cameron McDonald, Philip Hawkes and Josef Pieprzyk presented a hash collision attack with claimed complexity 252 at the Rump Session of Eurocrypt 2009.[43] However, the accompanying paper, "Differential Path for SHA-1 with complexity O(252)" has been withdrawn due to the authors' discovery that their estimate was incorrect.[44] One attack against SHA-1 was Marc Stevens[45] with an estimated cost of $2.77M to break a single hash value by renting CPU power from cloud servers.[46] Stevens developed this attack in a project called HashClash,[47] implementing a differential path attack. On 8 November 2010, he claimed he had a fully working near-collision attack against full SHA-1 working with an estimated complexity equivalent to 257.5 SHA-1 compressions. He estimated this attack could be extended to a full collision with a complexity around 261. The SHAppening[edit] On 8 October 2015, Marc Stevens, Pierre Karpman, and Thomas Peyrin published a freestart collision attack on SHA-1's compression function that requires only 257 SHA-1 evaluations. This does not directly translate into a collision on the full SHA-1 hash function (where an attacker is not able to freely choose the initial internal state), but undermines the security claims for SHA-1. In particular, it was the first time that an attack on full SHA-1 had been demonstrated; all earlier attacks were too expensive for their authors to carry them out. The authors named this significant breakthrough in the cryptanalysis of SHA-1 The SHAppening.[6] The method was based on their earlier work, as well as the auxiliary paths (or boomerangs) speed-up technique from Joux and Peyrin, and using high performance/cost efficient GPU cards from NVIDIA. The collision was found on a 16-node cluster with a total of 64 graphics cards. The authors estimated that a similar collision could be found by buying US$2,000 of GPU time on EC2.[6] The authors estimated that the cost of renting enough of EC2 CPU/GPU time to generate a full collision for SHA-1 at the time of publication was between US$75K–120K, and noted that was well within the budget of criminal organizations, not to mention national intelligence agencies. As such, the authors recommended that SHA-1 be deprecated as quickly as possible.[6] SHAttered – first public collision[edit] On 23 February 2017, the CWI (Centrum Wiskunde & Informatica) and Google announced the SHAttered attack, in which they generated two different PDF files with the same SHA-1 hash in roughly 263.1 SHA-1 evaluations. This attack is about 100,000 times faster than brute forcing a SHA-1 collision with a birthday attack, which was estimated to take 280 SHA-1 evaluations. The attack required "the equivalent processing power as 6,500 years of single-CPU computations and 110 years of single-GPU computations".[2][16] SHA-0[edit] At CRYPTO 98, two French researchers, Florent Chabaud and Antoine Joux, presented an attack on SHA-0: collisions can be found with complexity 261, fewer than the 280 for an ideal hash function of the same size.[48] In 2004, Biham and Chen found near-collisions for SHA-0—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 SHA-0 reduced to 62 out of its 80 rounds.[49] Subsequently, on 12 August 2004, a collision for the full SHA-0 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 251 and took about 80,000 processor-hours on a supercomputer with 256 Itanium 2 processors (equivalent to 13 days of full-time 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, SHA-0 and other hash functions. The complexity of their attack on SHA-0 is 240, significantly better than the attack by Joux et al.[50][51] In February 2005, an attack by Xiaoyun Wang, Yiqun Lisa Yin, and Hongbo Yu was announced which could find collisions in SHA-0 in 239 operations.[30][52] Another attack in 2008 applying the boomerang attack brought the complexity of finding collisions down to 233.6, which is estimated to take 1 hour on an average PC.[53] In light of the results for SHA-0, some experts[who?] suggested that plans for the use of SHA-1 in new cryptosystems should be reconsidered. After the CRYPTO 2004 results were published, NIST announced that they planned to phase out the use of SHA-1 by 2010 in favor of the SHA-2 variants.[54] Official validation[edit] Main article: Cryptographic Module Validation Program Implementations of all FIPS-approved 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 the formal CMVP validation, which is required by law for certain applications. As of December 2013[update], there are over 2000 validated implementations of SHA-1, with 14 of them capable of handling messages with a length in bits not a multiple of eight (see SHS Validation List).

Examples and pseudocode[edit] Example hashes[edit] These are examples of SHA-1 message digests in hexadecimal and in Base64 binary to ASCII text encoding. SHA1("The quick brown fox jumps over the lazy dog") gives hexadecimal: 2fd4e1c67a2d28fced849ee1bb76e7391b93eb12 gives Base64 binary to ASCII text encoding: L9ThxnotKPzthJ7hu3bnORuT6xI= Even a small change in the message will, with overwhelming probability, result in many bits changing 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") gives hexadecimal: de9f2c7fd25e1b3afad3e85a0bd17d9b100db4b3 gives Base64 binary to ASCII text encoding: 3p8sf9JeGzr60+haC9F9mxANtLM= The hash of the zero-length string is: SHA1("") gives hexadecimal: da39a3ee5e6b4b0d3255bfef95601890afd80709 gives Base64 binary to ASCII text encoding: 2jmj7l5rSw0yVb/vlWAYkK/YBwk= SHA-1 pseudocode[edit] Pseudocode for the SHA-1 algorithm follows: Note 1: All variables are unsigned 32-bit quantities and wrap modulo 232 when calculating, except for ml, the message length, which is a 64-bit quantity, and hh, the message digest, which is a 160-bit quantity. 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 ml = message length in bits (always a multiple of the number of bits in a character). Pre-processing: append the bit '1' to the message e.g. by adding 0x80 if message length is a multiple of 8 bits. append 0 ≤ k < 512 bits '0', such that the resulting message length in bits is congruent to −64 ≡ 448 (mod 512) append ml, the original message length, as a 64-bit big-endian integer. Thus, the total length is a multiple of 512 bits. Process the message in successive 512-bit chunks: break message into 512-bit chunks for each chunk break chunk into sixteen 32-bit big-endian words w[i], 0 ≤ i ≤ 15 Extend the sixteen 32-bit words into eighty 32-bit words: for i from 16 to 79 w[i] = (w[i-3] xor w[i-8] xor w[i-14] xor w[i-16]) leftrotate 1 Initialize hash value for this chunk: a = h0 b = h1 c = h2 d = h3 e = h4 Main loop:[3][55] 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 (big-endian) as a 160-bit number: hh = (h0 leftshift 128) or (h1 leftshift 96) or (h2 leftshift 64) or (h3 leftshift 32) or h4 The number hh is the message digest, which can be written in hexadecimal (base 16), but is often written using Base64 binary to ASCII text encoding. The constant values used are chosen to be nothing up my sleeve numbers: The four round constants k are 230 times the square roots of 2, 3, 5 and 10. The first four starting values for h0 through h3 are the same with the MD5 algorithm, and the fifth (for h4) is similar. Instead of the formulation from the original FIPS PUB 180-1 shown, the following equivalent expressions may be used to compute f in the main loop above: Bitwise choice between c and d, controlled by b. (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) Bitwise majority function. (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) (40 ≤ i ≤ 59): f = vec_sel(c, b, c xor d) (alternative 5) It was also shown[56] that for the rounds 32–79 the computation of: w[i] = (w[i-3] xor w[i-8] xor w[i-14] xor w[i-16]) leftrotate 1 can be replaced with: w[i] = (w[i-6] xor w[i-16] xor w[i-28] xor w[i-32]) leftrotate 2 This transformation keeps all operands 64-bit aligned and, by removing the dependency of w[i] on w[i-3], allows efficient SIMD implementation with a vector length of 4 like x86 SSE instructions.

Comparison of SHA functions[edit] In the table below, internal state means the "internal hash sum" after each compression of a data block. Further information: Merkle–Damgård construction Note that performance will vary not only between algorithms, but also with the specific implementation and hardware used. The OpenSSL tool has a built-in "speed" command that benchmarks the various algorithms on the user's system. view talk edit Comparison of SHA functions Algorithm and variant Output size (bits) Internal state size (bits) Block size (bits) Max message size (bits) Rounds Operations Security bits (Info) Capacity against length extension attacks Performance on Skylake (median cpb)[57] First Published long messages 8 bytes MD5 (as reference) 128 128 (4 × 32) 512 Unlimited[58] 64 And, Xor, Rot, Add (mod 232), Or <64 (collisions found) 0 4.99 55.00 1992 SHA-0 160 160 (5 × 32) 512 264 − 1 80 And, Xor, Rot, Add (mod 232), Or <34 (collisions found) 0 ≈ SHA-1 ≈ SHA-1 1993 SHA-1 <63 (collisions found[59]) 3.47 52.00 1995 SHA-2 SHA-224 SHA-256 224 256 256 (8 × 32) 512 264 − 1 64 And, Xor, Rot, Add (mod 232), Or, Shr 112 128 32 0 7.62 7.63 84.50 85.25 2004 2001 SHA-384 SHA-512 384 512 512 (8 × 64) 1024 2128 − 1 80 And, Xor, Rot, Add (mod 264), Or, Shr 192 256 128 (≤ 384) 0 5.12 5.06 135.75 135.50 SHA-512/224 SHA-512/256 224 256 112 128 288 256 ≈ SHA-384 ≈ SHA-384 SHA-3 SHA3-224 SHA3-256 SHA3-384 SHA3-512 224 256 384 512 1600 (5 × 5 × 64) 1152 1088 832 576 Unlimited[60] 24[61] And, Xor, Rot, Not 112 128 192 256 448 512 768 1024 8.12 8.59 11.06 15.88 154.25 155.50 164.00 164.00 2015 SHAKE128 SHAKE256 d (arbitrary) d (arbitrary) 1344 1088 min(d/2, 128) min(d/2, 256) 256 512 7.08 8.59 155.25 155.50

See also[edit] Collision (computer science) Comparison of cryptographic hash functions cryptlib Crypto++ Hash function security summary Hashcash International Association for Cryptologic Research Libgcrypt mbed TLS md5deep OpenSSL RIPEMD Secure Hash Standard sha1sum Tiger (cryptography) Trusted timestamping Whirlpool (cryptography)

Notes[edit] ^ Stevens, Marc (19 June 2012). "Attacks on Hash Functions and Applications" (PDF). PhD thesis. ^ a b Stevens, Marc; Bursztein, Elie; Karpman, Pierre; Albertini, Ange; Markov, Yarik. "The first collision for full SHA-1" (PDF). Shattered IO. Retrieved 23 February 2017. ^ a b http://csrc.nist.gov/publications/fips/fips180-4/fips-180-4.pdf ^ Schneier, Bruce (February 18, 2005). "Schneier on Security: Cryptanalysis of SHA-1". ^ "NIST.gov – Computer Security Division – Computer Security Resource Center". ^ a b c d Stevens1, Marc; Karpman, Pierre; Peyrin, Thomas. "The SHAppening: freestart collisions for SHA-1". Retrieved 2015-10-09. ^ Schneier, Bruce (8 October 2015). "SHA-1 Freestart Collision". Schneier on Security. ^ "Windows Enforcement of Authenticode Code Signing and Timestamping". Microsoft. 2015-09-24. Retrieved 2016-08-07. ^ "Intent to Deprecate: SHA-1 certificates". Google. 2014-09-03. Retrieved 2014-09-04. ^ "Safari and WebKit ending support for SHA-1 certificates – Apple Support". Apple Inc. 2017-01-24. Retrieved 2017-02-04. ^ "Bug 942515 – stop accepting SHA-1-based SSL certificates with notBefore >= 2014-03-01 and notAfter >= 2017-01-01, or any SHA-1-based SSL certificates after 2017-01-01". Mozilla. Retrieved 2014-09-04. ^ "CA:Problematic Practices – MozillaWiki". Mozilla. Retrieved 2014-09-09. ^ "Phasing Out Certificates with SHA-1 based Signature Algorithms | Mozilla Security Blog". Mozilla. 2014-09-23. Retrieved 2014-09-24. ^ "CWI, Google announce first collision for Industry Security Standard SHA-1". Retrieved 2017-02-23. ^ "Announcing the first SHA1 collision". Google Online Security Blog. 2017-02-23. ^ a b "SHAttered". Retrieved 2017-02-23. ^ RSA FAQ on Capstone ^ Selvarani, R.; Aswatha, Kumar; T V Suresh, Kumar (2012). Proceedings of International Conference on Advances in Computing. Springer Science & Business Media. p. 551. ISBN 978-81-322-0740-5. ^ Secure Hash Standard, Federal Information Processing Standards Publication FIPS PUB 180, National Institute of Standards and Technology, 11 May 1993 ^ Domke, Felix aka "tmbinc" (2008-04-24). "Thank you, Datel". Retrieved 2014-10-05. For verifying 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 SHA1-hash, up to 152 bits are thrown away. ^ National Institute on Standards and Technology Computer Security Resource Center, NIST's March 2006 Policy on Hash Functions, accessed September 28, 2012. ^ National Institute on Standards and Technology Computer Security Resource Center, NIST's Policy on Hash Functions, accessed September 28, 2012. ^ "Tech Talk: Linus Torvalds on git". Retrieved November 13, 2013. ^ Torvalds, Linus. "Re: Starting to think about sha-256?". marc.info. Retrieved 30 May 2016. ^ Wang, Xiaoyun; Yin, Yiqun Lisa; Yu, Hongbo (2005-08-14). "Finding Collisions in the Full SHA-1". Advances in Cryptology – CRYPTO 2005. Springer, Berlin, Heidelberg: 17–36. doi:10.1007/11535218_2. ^ Sotirov, Alexander; Stevens, Marc; Appelbaum, Jacob; Lenstra, Arjen; Molnar, David; Osvik, Dag Arne; de Weger, Benne (December 30, 2008). "MD5 considered harmful today: Creating a rogue CA certificate". Retrieved March 29, 2009. ^ "Strengths of Keccak – Design and security". The Keccak sponge function family. Keccak team. Retrieved 20 September 2015. Unlike SHA-1 and SHA-2, Keccak does not have the length-extension weakness, hence does not need the HMAC nested construction. Instead, MAC computation can be performed by simply prepending the message with the key. ^ Niels Ferguson, Bruce Schneier, and Tadayoshi Kohno, Cryptography Engineering, John Wiley & Sons, 2010. ISBN 978-0-470-47424-2 ^ "Cryptology ePrint Archive: Report 2005/010". ^ a b "SHA-1 Broken – Schneier on Security". ^ MIT.edu, Massachusetts Institute of Technology ^ Lemos, Robert. "Fixing a hole in security". ZDNet. ^ "New Cryptanalytic Results Against SHA-1 – Schneier on Security". ^ Notes on the Wang et al. 263 SHA-1 Differential Path ^ De Cannière, Christophe; Rechberger, Christian (2006-11-15). "Finding SHA-1 Characteristics: General Results and Applications". ^ "IAIK Krypto Group — Description of SHA-1 Collision Search Project". Retrieved 2009-06-30. ^ "Collisions for 72-step and 73-step SHA-1: Improvements in the Method of Characteristics". Retrieved 2010-07-24. ^ "SHA-1 Collision Search Graz". Retrieved 2009-06-30. ^ "heise online – IT-News, Nachrichten und Hintergründe". heise online. ^ "Crypto 2006 Rump Schedule". ^ Manuel, Stéphane. "Classification and Generation of Disturbance Vectors for Collision Attacks against SHA-1" (PDF). Retrieved 2011-05-19. ^ Manuel, Stéphane. "Classification and Generation of Disturbance Vectors for Collision Attacks against SHA-1". Retrieved 2012-10-04. the most efficient disturbance vector is Codeword2 first reported by Jutla and Patthak ^ SHA-1 collisions now 2^52 ^ "Cryptology ePrint Archive: Report 2009/259". ^ Cryptanalysis of MD5 & SHA-1 ^ "When Will We See Collisions for SHA-1? – Schneier on Security". ^ "Google Project Hosting". ^ Chabaud, Florent; Joux, Antoine (1998). Differential Collisions in SHA-0 (PDF). CRYPTO '98. ^ Biham, Eli; Chen, Rafi. "Near-Collisions of SHA-0" (PDF). ^ "Report from Crypto 2004". ^ Grieu, Francois (18 August 2004). "Re: Any advance news from the crypto rump session?". Newsgroup: sci.crypt. Event occurs at 05:06:02 +0200. Usenet: fgrieu-05A994.05060218082004@individual.net. ^ (in Chinese) Sdu.edu.cn, Shandong University ^ Manuel, Stéphane; Peyrin, Thomas (2008-02-11). "Collisions on SHA-0 in One Hour". ^ National Institute of Standards and Technology ^ "RFC 3174 – US Secure Hash Algorithm 1 (SHA1)". ^ Locktyukhin, Max; Farrel, Kathy (2010-03-31), "Improving the Performance of the Secure Hash Algorithm (SHA-1)", Intel Software Knowledge Base, Intel, retrieved 2010-04-02 ^ http://bench.cr.yp.to/results-hash.html#amd64-skylake ^ "The MD5 Message-Digest Algorithm". Retrieved 2016-04-18. In the unlikely event that b is greater than 2^64, then only the low-order 64 bits of b are used. ^ "Announcing the first SHA1 collision". Retrieved 2017-02-23. ^ "The Sponge Functions Corner". Retrieved 2016-01-27. ^ "The Keccak sponge function family". Retrieved 2016-01-27.

References[edit] Florent Chabaud, Antoine Joux: Differential Collisions in SHA-0. CRYPTO 1998. pp56–71 Eli Biham, Rafi Chen, Near-Collisions of SHA-0, 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 SHA-0, CRYPTO 2005, CMU.edu Xiaoyun Wang, Yiqun Lisa Yin and Hongbo Yu, Finding Collisions in the Full SHA-1, Crypto 2005 MIT.edu Henri Gilbert, Helena Handschuh: Security Analysis of SHA-256 and Sisters. Selected Areas in Cryptography 2003: pp175–193 unixwiz.net "Proposed Revision of Federal Information Processing Standard (FIPS) 180, Secure Hash Standard". Federal Register. 59 (131): 35317–35318. 1994-07-11. Retrieved 2007-04-26. A. Cilardo, L. Esposito, A. Veniero, A. Mazzeo, V. Beltran, E. Ayugadé, A CellBE-based HPC application for the analysis of vulnerabilities in cryptographic hash functions, High Performance Computing and Communication international conference, August 2010

External links[edit] CSRC Cryptographic Toolkit – Official NIST site for the Secure Hash Standard FIPS 180-4: Secure Hash Standard (SHS) RFC 3174 (with sample C implementation) Interview with Yiqun Lisa Yin concerning the attack on SHA-1 Explanation of the successful attacks on SHA-1 (3 pages, 2006) Cryptography Research – Hash Collision Q&A Hash Project Web Site: software- and hardware-based cryptanalysis of SHA-1 SHA-1 at Curlie (based on DMOZ) Lecture on SHA-1 on YouTube by Christof Paar v t e Cryptographic hash functions & message authentication codes List Comparison Known attacks Common functions MD5 SHA-1 SHA-2 SHA-3 BLAKE2 SHA-3 finalists BLAKE Grøstl JH Skein Keccak (winner) Other functions CubeHash ECOH FSB GOST HAS-160 HAVAL Kupyna LM hash MD2 MD4 MD6 MDC-2 N-Hash RIPEMD RadioGatún SWIFFT Snefru Streebog Tiger VSH Whirlpool Key derivation functions Argon2 bcrypt crypt Lyra2 PBKDF2 scrypt MAC functions DAA CBC-MAC HMAC NMAC OMAC/CMAC PMAC VMAC UMAC Poly1305 SipHash Authenticated encryption modes CCM CWC EAX GCM IAPM OCB Attacks Collision attack Preimage attack Birthday attack Brute-force attack Rainbow table Side-channel attack Length extension attack Design Avalanche effect Hash collision Merkle–Damgård construction Sponge function HAIFA construction Unique Block Iteration Standardization CRYPTREC NESSIE NIST hash function competition Utilization Hash-based cryptography Key stretching Merkle tree Message authentication Proof of work Salt Pepper v t e Cryptography History of cryptography Cryptanalysis Outline of cryptography Symmetric-key algorithm Block cipher Stream cipher Public-key cryptography Cryptographic hash function Message authentication code Random numbers Steganography Crypto-shredding Category Portal WikiProject Retrieved from "https://en.wikipedia.org/w/index.php?title=SHA-1&oldid=831323719" Categories: Cryptographic hash functionsBroken hash functionsChecksum algorithmsNational Security Agency cryptographyHidden categories: Articles with Chinese-language external linksAll articles with unsourced statementsArticles with unsourced statements from March 2016Articles with unsourced statements from April 2017Articles with specifically marked weasel-worded phrases from March 2017All articles with specifically marked weasel-worded phrasesArticles with specifically marked weasel-worded phrases from September 2015Articles containing potentially dated statements from 2013All articles containing potentially dated statementsArticles with Curlie linksArticles with example pseudocodePages using RFC magic links

Navigation menu Personal tools Not logged inTalkContributionsCreate accountLog in Namespaces ArticleTalk Variants Views ReadEditView history More Search Navigation Main pageContentsFeatured contentCurrent eventsRandom articleDonate to WikipediaWikipedia store Interaction HelpAbout WikipediaCommunity portalRecent changesContact page Tools What links hereRelated changesUpload fileSpecial pagesPermanent linkPage informationWikidata itemCite this page Print/export Create a bookDownload as PDFPrintable version Languages বাংলাБългарскиDeutschEspañolفارسیFrançaisHrvatskiLatviešuമലയാളം日本語PolskiPortuguêsРусскийSrpskohrvatski / српскохрватскиSvenskaTürkçeУкраїнська中文 Edit links This page was last edited on 20 March 2018, at 00:27. Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. By using this site, you agree to the Terms of Use and Privacy Policy. Wikipedia® is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization. Privacy policy About Wikipedia Disclaimers Contact Wikipedia Developers Cookie statement Mobile view (window.RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgPageParseReport":{"limitreport":{"cputime":"0.816","walltime":"1.228","ppvisitednodes":{"value":4619,"limit":1000000},"ppgeneratednodes":{"value":0,"limit":1500000},"postexpandincludesize":{"value":171948,"limit":2097152},"templateargumentsize":{"value":6087,"limit":2097152},"expansiondepth":{"value":16,"limit":40},"expensivefunctioncount":{"value":6,"limit":500},"unstrip-depth":{"value":0,"limit":20},"unstrip-size":{"value":53178,"limit":5000000},"entityaccesscount":{"value":0,"limit":400},"timingprofile":["100.00% 1127.149 1 -total"," 37.12% 418.417 1 Template:Reflist"," 35.31% 397.941 2 Template:Infobox"," 31.30% 352.849 1 Template:SHA-box"," 15.69% 176.826 36 Template:Cite_web"," 6.92% 78.054 7 Template:Cite_journal"," 6.79% 76.501 4 Template:Fix"," 5.89% 66.427 4 Template:Navbox"," 5.68% 63.987 1 Template:Infobox_encryption_method"," 5.63% 63.511 2 Template:Citation_needed"]},"scribunto":{"limitreport-timeusage":{"value":"0.423","limit":"10.000"},"limitreport-memusage":{"value":6685847,"limit":52428800}},"cachereport":{"origin":"mw1345","timestamp":"20180320002653","ttl":1900800,"transientcontent":false}}});});(window.RLQ=window.RLQ||[]).push(function(){mw.config.set({"wgBackendResponseTime":72,"wgHostname":"mw1253"});});

view link view link view link view link view link |