From: Pavel Machek <pavel@ucw.cz>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Bart Samwel <bart@samwel.tk>,
Timothy Miller <miller@techsource.com>,
Valdis.Kletnieks@vt.edu,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [OT] Redundancy eliminating file systems, breaking MD5, donating money to OSDL
Date: Thu, 22 Jan 2004 01:12:59 +0100 [thread overview]
Message-ID: <20040122001259.GA300@elf.ucw.cz> (raw)
In-Reply-To: <20040120192114.GA30755@citd.de>
Hi!
> There is one fundemental braino in the discussion.
>
> Only HALF the bits are for preventing "accidental" collisions. (The
> "birthday" thing). The rest is for preventing to "brute force" an input
> that produces the same MD5.(*)
>
> So MD5 has only 2**64 Bits against accidental collsions
> Btw. I already had (a/the) MD5 collision(*2) in my life.
>
> So you'd need SHA256 or SHA512 to be "really sure(tm)".
>
>
>
> *: AFAIR i read this in the specs of SHA1 (160 bits). So i guess this is
> also true for MD5.
>
> *2: I had a direcory of about 1,5 Million images and "md5sum"med them to
> eliminate doubles. The Log-file, at one point, had the same md5sum as
> one of the pictures.
Do you have a copy? I believe *many* people would like to see that
one.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2004-01-22 0:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 20:22 [OT] Redundancy eliminating file systems, breaking MD5, donating money to OSDL Timothy Miller
2004-01-16 20:37 ` Valdis.Kletnieks
2004-01-16 20:59 ` Timothy Miller
2004-01-17 13:15 ` Bart Samwel
2004-01-20 19:21 ` Matthias Schniedermeyer
2004-01-21 11:46 ` Bart Samwel
2004-01-22 0:12 ` Pavel Machek [this message]
2004-01-22 8:29 ` Matthias Schniedermeyer
2004-01-22 2:36 ` Jamie Lokier
2004-01-22 8:51 ` Matthias Schniedermeyer
-- strict thread matches above, loose matches on Subject: below --
2004-01-20 18:06 Clayton Weaver
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=20040122001259.GA300@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=Valdis.Kletnieks@vt.edu \
--cc=bart@samwel.tk \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--cc=ms@citd.de \
/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