Re: compare-by-hash (was Re: sharing /etc/passwd)

From: Jacques A. Vidrine (nectar_at_FreeBSD.org)
Date: 09/28/04

  • Next message: David Schultz: "Re: compare-by-hash (was Re: sharing /etc/passwd)"
    Date: Tue, 28 Sep 2004 10:15:41 -0500
    To: Giorgos Keramidas <keramida@linux.gr>
    
    

    On Tue, Sep 28, 2004 at 12:14:05PM +0300, Giorgos Keramidas wrote:
    > There is one difference between ``looking for collisions'' and being
    > bitten by undetected collisions though.
    >
    > If the probability of a collision just happening with random user data
    > is 1/(2^128) we can't be sure that it will necessarily take the
    > transfer of an average number of 2^127 blocks before a collision
    > happens. You might get one at the very first pair of blocks and then
    > no collisions ever after until the Sun burns out.
    >
    > Using two different hashes for the same set of input data, which David
    > G. Andersen proposed, seems like a nice idea though.

    If you buy the "logic" of the paper, this would not make much
    difference. After all, composing two hashes just gives you another
    hash with a longer bit length.

    This paper needs a lot more peer review, although I'm not sure that
    many take it seriously enough to bother.

    Cheers,

    -- 
    Jacques A Vidrine / NTT/Verio
    nectar@celabo.org / jvidrine@verio.net / nectar@FreeBSD.org
    _______________________________________________
    freebsd-security@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-security
    To unsubscribe, send any mail to "freebsd-security-unsubscribe@freebsd.org"
    

  • Next message: David Schultz: "Re: compare-by-hash (was Re: sharing /etc/passwd)"

    Relevant Pages

    • Re: Reducing hashing collision
      ... Of course he was simply pointing out that if one assumes a 128 bit hash, ... up more storage than exists in the whole world today) or that collisions ... or 256-bit hashes. ...
      (sci.crypt)
    • Re: compare-by-hash (was Re: sharing /etc/passwd)
      ... >> infinite number of inputs, you are guaranteed an infinite number of ... > If the probability of a collision just happening with random user data ... > no collisions ever after until the Sun burns out. ... > Using two different hashes for the same set of input data, ...
      (FreeBSD-Security)
    • Re: Reducing hashing collision
      ... Of course he was simply pointing out that if one assumes a 128 bit hash, ... up more storage than exists in the whole world today) or that collisions ... or 256-bit hashes. ... That would require more storage than is available in all of the hard ...
      (sci.crypt)
    • Re: SHA-1 collisions
      ... > Chinese guys successfully got collisions against the SHA-1 hash algorithm. ... 2^80 hashes. ...
      (sci.crypt)
    • Re: compare-by-hash (was Re: sharing /etc/passwd)
      ... > infinite number of inputs, you are guaranteed an infinite number of ... bitten by undetected collisions though. ... If the probability of a collision just happening with random user data ...
      (FreeBSD-Security)