git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trekie <trekie@sinister.cz>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [RFC] adding support for md5
Date: Fri, 18 Aug 2006 13:27:18 +0200	[thread overview]
Message-ID: <44E5A416.9040709@sinister.cz> (raw)
In-Reply-To: <Pine.LNX.4.63.0608181255060.28360@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin wrote:
> SHA1 has been broken (collisions have been found):
> 
> http://www.schneier.com/blog/archives/2005/02/sha1_broken.html

I don't think you're right. That blog just says, that Wang can find

"collisions in the the full SHA-1 in 2**69 hash operations, much less
than the brute-force attack of 2**80 operations based on the hash length."

That doesn't mean any collision has been found. In academic
cryptography, any attack that has less computational complexity than the
expected time needed for brute force is considered a break.

In a document (http://www.rsasecurity.com/rsalabs/node.asp?id=2927) that
has been released 6 months after that blog post is said a collision can
be found in 2^63 operations.

Well, if someone use the fastest computer today
(http://www.top500.org/system/7747) to get a collision it would take a
day to found one.

The point is why use MD5 if anyone can compute a collision?

David Brodsky

  reply	other threads:[~2006-08-18 11:23 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-18  6:01 [RFC] adding support for md5 David Rientjes
2006-08-18  9:59 ` Nguyễn Thái Ngọc Duy
2006-08-18 10:21 ` Johannes Schindelin
2006-08-18 12:31   ` Petr Baudis
2006-08-18 20:35   ` David Rientjes
2006-08-18 10:52 ` Trekie
2006-08-18 10:56   ` Johannes Schindelin
2006-08-18 11:27     ` Trekie [this message]
2006-08-18 11:37       ` Johannes Schindelin
2006-08-18 21:52 ` Jon Smirl
2006-08-19  2:35   ` Johannes Schindelin
2006-08-19 20:50 ` Linus Torvalds
2006-08-21 20:44   ` Chris Wedgwood
2006-08-22  6:18     ` Junio C Hamano
2006-08-23  4:14       ` Shawn Pearce
2006-08-23  4:46         ` Junio C Hamano
2006-08-23  6:49           ` Shawn Pearce
2006-08-24  7:36             ` Junio C Hamano
2006-08-24  8:08               ` Shawn Pearce
2006-08-24 10:34                 ` Junio C Hamano
  -- strict thread matches above, loose matches on Subject: below --
2006-08-19  3:19 linux
2006-08-19 22:30 ` Petr Baudis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44E5A416.9040709@sinister.cz \
    --to=trekie@sinister.cz \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).