public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eric Rannaud <Eric.Rannaud@ens.fr>
To: Pedro Larroy <piotr@larroy.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Call to atention about using hash functions as content indexers (SCM saga)
Date: Tue, 12 Apr 2005 18:35:49 +0200	[thread overview]
Message-ID: <20050412163549.GA7379@clipper.ens.fr> (raw)
In-Reply-To: <20050411224021.GA25106@larroy.com>


Simply put, the best known attack of SHA-1 takes 2^69 hash operations.
( http://www.schneier.com/blog/archives/2005/02/sha1_broken.html )
The attack is still only an unpublished paper and has not yet been
implemented. An attack is: you try as hard as you can to find a collision
between two arbitrary messages (i.e. two arbitrary --and nonsensical--
source files).
In the context of git, a better estimation would be the number of hash
operations needed to find a message that has the same hash than a given
fixed message (e.g. mm/memory.c). This is more like 2^100 hash
operations. And if a collision is found, this is very likely using a
message that *doesn't* look like a C source file...

Moreover, no example of collision is known, AFAIK.

In other words: this won't happen.

Best,
   /er.

  parent reply	other threads:[~2005-04-12 16:42 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-11 22:40 Call to atention about using hash functions as content indexers (SCM saga) Pedro Larroy
2005-04-11 22:51 ` Petr Baudis
2005-04-11 23:23   ` Magnus Damm
2005-04-12 10:02     ` Catalin Marinas
2005-04-12  9:59   ` Barry K. Nathan
2005-04-12 12:10   ` Richard B. Johnson
2005-04-12 15:29 ` Theodore Ts'o
2005-04-14 15:54   ` Eric D. Mudama
2005-04-12 16:35 ` Eric Rannaud [this message]
2005-04-14  8:30   ` Andy Isaacson
2005-04-14 13:35     ` Eric Rannaud

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=20050412163549.GA7379@clipper.ens.fr \
    --to=eric.rannaud@ens.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=piotr@larroy.com \
    /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