Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:




bugtraq logo Bugtraq mailing list archives

Re: SHA-1 broken
From: Robert Sussland <robert () inkwood org>
Date: Wed, 16 Feb 2005 17:25:06 -0800


On Feb 16, 2005, at 4:56 AM, Gadi Evron wrote:

Now, we've all seen this coming for a while.
http://www.schneier.com/blog/archives/2005/02/sha1_broken.html

Where do we go from here?

We abandon the requirement of collision resistance. This is a strange requirement, and is not supported by experience. Collision resistance is not a "hard" problem in the sense that factoring large numbers or computing discrete logs is hard. Collision resistance in deterministic hash functions smells too much like generating entropy without secrets. I have no reason to believe that careful analysis of *any* publicly known deterministic many-to-one function will not allow me to produce a collision, assuming I control all inputs into the function.

From my point of view, the issue is what weaker assumption do we replace collision resistance with -- how about:

target collision resistance, with the "strength" of resistance equal to the average advantage an attacker would gain in matching a fixed target, as the target is averaged over all possible inputs in a measure space? Then, producing "rare" messages which could be targeted would not weaken the hash, as the probability of such messages occurring would be low.

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]