All of lore.kernel.org
 help / color / mirror / Atom feed
From: Edward Shishkin <edward@namesys.com>
To: Hans Reiser <reiser@namesys.com>
Cc: "Grzegorz Jaśkiewicz" <gryzman@gmail.com>,
	"Matthias Andree" <ma@dt.e-technik.uni-dortmund.de>,
	hihone@bigpond.net.au, reiserfs-list@namesys.com
Subject: Re: Congratulations! we have got hash function screwed up
Date: Thu, 20 Jan 2005 16:18:40 +0300	[thread overview]
Message-ID: <41EFAFB0.2000606@namesys.com> (raw)
In-Reply-To: <41EE859D.3020305@namesys.com>

Hans Reiser wrote:

> Grzegorz Jaśkiewicz wrote:
>
>> On Thu, 30 Dec 2004 08:40:51 -0800, Hans Reiser <reiser@namesys.com> 
>> wrote:
>>  
>>
>>> Fixing hash collisions in V3 to do them the way V4 does them would
>>> create more bugs and user disruption than the current bug we have all
>>> lived with for 5 years until now.  If someone thinks it is a small
>>> change to fix it, send me a patch.  Better by far to fix bugs in V4,
>>> which is pretty stable these days.
>>>   
>>
>>
>> As I understeand, tea hash is based on tea (tiny encryption aglo),
>> which was the cause of xbox-linux sucess, and few others.
>> Pleas consider updating it to use xxtea algo. I know, it won't be
>> backward compatbile, but well.
>> Where is about all the others, I don't use them, and for me tea is the
>> only resonable hash to use on systems where I have very much great
>> number of files per directory (to name it, Maildirs).
>> Never had such problem myself, every hash function has a weaknes.
>> Nothing new. But providing another, much stronger hash, or correct tea
>> hash to use xxtea, would be something good indeed.
>>
>>  
>>
> Edward, please look into whether we should use xxtea in Reiser4, and 
> make a recommendation to me.  We aren't changing V3, it is stable and 
> I want to leave it that way.
>
> Hans
>
>
I found that:
1. xxtea is a correction to the Blocktea algorithm against the attack 
not related to the original tea or xtea.
2. xtea is an upgrade of tea algo which eliminates two minor weakness of 
the last one related to key attacks,
and not related to the collisions of tea hash (for each name tea hash 
uses ciphering by the key constructed
by  this name).
So imho it doesn't make sense to upgrade the core rounds used in tea 
hash. Any objections?

Edward.

  parent reply	other threads:[~2005-01-20 13:18 UTC|newest]

Thread overview: 67+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30 11:52 Congratulations! we have got hash function screwed up 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 [this message]
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
  -- strict thread matches above, loose matches on Subject: below --
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
2004-12-30 17:22 Yiannis Mavroukakis
2004-12-30 13:24 Yiannis Mavroukakis
2004-12-30 14:11 ` Matthias Andree
2004-12-28 22:12 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-06 18:55     ` Edward Shishkin
2005-01-07 17:26       ` Lehmann 

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=41EFAFB0.2000606@namesys.com \
    --to=edward@namesys.com \
    --cc=gryzman@gmail.com \
    --cc=hihone@bigpond.net.au \
    --cc=ma@dt.e-technik.uni-dortmund.de \
    --cc=reiser@namesys.com \
    --cc=reiserfs-list@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.