From: Timothy Miller <miller@techsource.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [OT] Redundancy eliminating file systems, breaking MD5, donating money to OSDL
Date: Fri, 16 Jan 2004 15:22:39 -0500 [thread overview]
Message-ID: <4008480F.70206@techsource.com> (raw)
Recently, I saw a slashdot article that pointed to a site dedicated to
breaking MD5. That is, so far, no one has found any two differing
string which have the same MD5 cksum. Logically, however, there WILL be
collisions for any strings longer than the MD5 cksum itself -- we just
haven't found any. Well, there's some sort of contest where you can win
money for breaking MD5 (I think).
Even further back, there was an LKML discussion about various sorts of
compressing file systems. One of the subthreads discussed identifying
identical blocks (using MD5) and pointing them at the same physical
block on disk. Naturally, if there WERE two blocks with the same MD5,
we'd want to check the raw data, just to be sure that there wasn't a
false positive.
Think about it! If we had a filesystem that actually DID this, and it
was in the Linux kernel, it would spread far and wide. It's bound to
happen that someone will identify a collision. We then report that to
the committee offering the reward and then donate it to OSDL to help
Linux development.
Yeah, I know... I'm a dork.
next reply other threads:[~2004-01-16 20:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 20:22 Timothy Miller [this message]
2004-01-16 20:37 ` [OT] Redundancy eliminating file systems, breaking MD5, donating money to OSDL 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
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=4008480F.70206@techsource.com \
--to=miller@techsource.com \
--cc=linux-kernel@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