From: <pcg( Marc)@goof(A.).(Lehmann )com>
To: Edward Shishkin <edward@namesys.com>
Cc: Alex Zarochentsev <zam@namesys.com>,
reiserfs-list@namesys.com, stefan@hello-penguin.com
Subject: Re: Congratulations! we have got hash function screwed up
Date: Fri, 7 Jan 2005 18:26:48 +0100 [thread overview]
Message-ID: <20050107172648.GB18191@schmorp.de> (raw)
In-Reply-To: <41DD8998.3070604@namesys.com>
On Thu, Jan 06, 2005 at 09:55:20PM +0300, Edward Shishkin <edward@namesys.com> wrote:
> >On Thu, Jan 06, 2005 at 03:45:06PM +0300, Alex Zarochentsev
> ><zam@namesys.com> wrote:
> >>>
> >>Tea hash is designed to be more resistant.
> >>
> >>
>
> Actually this can not be more resistant as it use the same 32-bit output
> size.
Sure it can, filenames are not randomly distributed, so your argument doesn't
suffice to show that tea cannot be more resistent, as it could be more
resistent for other reasons.
That's why I originally wrote "nicely-looking", which (if it wasn't clear)
was meant to say that filenames with somewhat similar names do collide
even with tea, which suppossedly was chosen to avoid this case.
> So to find a collision you just need to find hashes of 2^16 = 65536
> random documents.
True. It's even worse if these collisions happen to filenames occuring in
practise.
(I also agree to the rest of your mail)
--
The choice of a
-----==- _GNU_
----==-- _ generation Marc Lehmann
---==---(_)__ __ ____ __ pcg@goof.com
--==---/ / _ \/ // /\ \/ / http://schmorp.de/
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE
next prev parent reply other threads:[~2005-01-07 17:26 UTC|newest]
Thread overview: 72+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-28 22:12 Congratulations! we have got hash function screwed up Lehmann
2004-12-29 18:55 ` Stefan Traby
2004-12-29 21:04 ` Lehmann
2004-12-29 21:05 ` Hans Reiser
2004-12-29 21:43 ` Lehmann
2004-12-29 21:46 ` Christian Iversen
2004-12-29 22:27 ` Lehmann
2004-12-30 2:05 ` Hans Reiser
2004-12-30 10:22 ` Matthias Andree
2004-12-30 17:02 ` Lehmann
2005-01-06 12:45 ` Alex Zarochentsev
2005-01-06 14:27 ` Lehmann
2005-01-06 15:56 ` Hans Reiser
2005-01-06 16:13 ` Spam
2005-01-06 16:26 ` Chris Dukes
2005-01-06 16:29 ` Spam
2005-01-06 16:56 ` Chris Dukes
2005-01-07 17:22 ` Hans Reiser
2005-01-07 17:28 ` Chris Dukes
2005-01-07 23:27 ` flush earlier? (was Re: Congratulations! we have got hash function screwed up) David Masover
2005-01-07 23:52 ` Hans Reiser
2005-01-08 5:03 ` David Masover
2005-01-08 20:48 ` Hans Reiser
2005-01-09 23:26 ` David Masover
2005-01-06 18:55 ` Congratulations! we have got hash function screwed up Edward Shishkin
2005-01-07 17:26 ` Lehmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-30 11:52 Yiannis Mavroukakis
2004-12-30 12:40 ` Matthias Andree
2004-12-30 12:59 ` Cal
2004-12-30 14:18 ` Matthias Andree
2004-12-30 16:40 ` Hans Reiser
2004-12-30 16:51 ` Matthias Andree
2005-01-18 21:17 ` Grzegorz Jaśkiewicz
2005-01-19 16:06 ` Hans Reiser
2005-01-19 22:41 ` David Masover
2005-01-20 13:18 ` Edward Shishkin
2005-01-20 23:43 ` Grzegorz Jaśkiewicz
2005-01-21 9:31 ` Edward Shishkin
2004-12-30 17:07 ` Esben Stien
2004-12-30 17:15 ` Christian Iversen
2004-12-30 17:47 ` Sander
2004-12-30 17:59 ` Esben Stien
2004-12-30 18:30 ` Sander
2004-12-30 18:46 ` Esben Stien
2004-12-30 18:49 ` Chris Dukes
2004-12-30 19:21 ` Sander
2004-12-30 19:29 ` Esben Stien
2004-12-30 18:16 ` Esben Stien
2004-12-30 18:26 ` Spam
2004-12-30 20:41 ` Tom Vier
2004-12-30 23:14 ` Matthias Andree
2004-12-30 23:25 ` Spam
2004-12-31 4:11 ` Hans Reiser
2004-12-31 8:36 ` Matthias Andree
2004-12-30 20:08 ` Hans Reiser
2004-12-30 21:55 ` Esben Stien
2004-12-31 4:05 ` David Masover
2004-12-31 4:26 ` Hans Reiser
2004-12-31 5:59 ` David Masover
2004-12-30 20:57 ` Adrian Ulrich
2004-12-30 21:01 ` Stefan Traby
2004-12-30 21:20 ` brianmas
2004-12-30 17:09 ` Lehmann
2004-12-30 20:11 ` Hans Reiser
2004-12-30 13:24 Yiannis Mavroukakis
2004-12-30 14:11 ` Matthias Andree
2004-12-30 17:22 Yiannis Mavroukakis
2004-12-30 18:16 Burnes, James
2004-12-30 18:36 ` Esben Stien
2004-12-30 19:26 ` Matthias Andree
2004-12-30 19:24 ` Matthias Andree
2004-12-30 20:25 ` Hans Reiser
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=20050107172648.GB18191@schmorp.de \
--to=pcg@goof.com \
--cc=edward@namesys.com \
--cc=reiserfs-list@namesys.com \
--cc=stefan@hello-penguin.com \
--cc=zam@namesys.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.