Cryptography Stack Exchange is a question and answer site for software developers, mathematicians and others interested in cryptography. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I'm searching Why the SHA-1 is collision resistance? Anybody could help me with the proof or say me where I can find this proof?

share|improve this question
1) It isn't 2) Those properties generally don't have a proof. – CodesInChaos Oct 7 '13 at 12:00
@CodesInChaos Is there intuitive proof? For example Why init with the haxadecimals 67452301, 67452301, 98BADCFE, ...? – juaninf Oct 7 '13 at 14:03
Those are essentially random numbers, but created in a way that doesn't allow the algorithm designer to choose them, so called Nothing up my sleeve numbers. I don't remember what SHA-1 chose, probably the first few hex digits of square-root of a small prime. – CodesInChaos Oct 7 '13 at 14:53
@CodesInChaos here "but created in a way that doesn't allow the algorithm designer to choose them", please Could explain me this in more detail, with an example? – juaninf Oct 7 '13 at 14:56
You might be interested to read "When Will We See Collisions for SHA-1?" by Bruce Schneier (published October 5, 2012), which gives you a pretty good answer to your question. Btw: looks like a pretty similar question was asked at StackOverflow and got some good answers that you also might find to be valuable. – e-sushi Oct 7 '13 at 17:56
up vote 6 down vote accepted

There is no such proof, on the contrary it has been proven that SHA-1 does not possess the ideal 80 bit collision resistance. Rather it is down to around 61 bits of resistance, uncomfortably close to being practically exploitable, and even if no further weaknesses are found advances in computing power are almost guaranteed to make it reasonably practical within a decade or two.

This weakness is only to collision attacks, that is attacks where the attacker can construct two different data pieces that has the same hash value, and thereby break some security measure, in some use cases that is relevant and SHA-1 is therefore problematic, in other cases it isn't and we can afford to be a bit more relaxed about the use of SHA-1 as its pre-image resistance doesn't seem likely to drop to a critical level any time soon.

In any case though, for new applications you are best advised to avoid using SHA-1 and earlier, instead use for instance one of the SHA-2 functions.

As for the theoretical foundation, SHA-1 is a Merkle–Damgård construction, such a construction is proven to be a perfect hash given that the one-way compression function it is built on can give some similar guarantees. It was presumably for this reason that Merkle–Damgård constructions became popular, but ultimately it is the one-way compression function that is the critical part, the Merkle–Damgård proof only tells us that the much simpler container format is not borked. You can find loads of cryptanalysis reports for any popular hash function, but unless you are a pretty sharp mathematician with a lot of time to kill they are probably not going to be of any use to you.

share|improve this answer

Great question, I'd love to see more proofs as well. This is pretty cool:

This is a very easy to follow and interesting proof based on the Merkle-Damgard construction (used for SHA1) that if you have a collision resistance function for a short message -> you have a collision resistance function for long messages. (He does this by using the proof by contra positive, by showing that a collision on the big message implies a collision on the short message.)

He then goes on to create collision resistant functions for short messages.

I'm not sure if this completely solves what you're looking for, however it has a lot of easy to digest but detailed introductory information which should help get you on your way / supplement other material you might find.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.