From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= Subject: Re: Congratulations! we have got hash function screwed up Date: Fri, 21 Jan 2005 00:43:56 +0100 Message-ID: <2f4958ff050120154330188420@mail.gmail.com> References: <77912E9FD42896419D1CEF15E1C397A58AFCF1@london.jaguarfreightservices.local> <20041230235911.4911a20c.hihone@bigpond.net.au> <41D42F93.9060107@namesys.com> <2f4958ff050118131714f5411c@mail.gmail.com> <41EE859D.3020305@namesys.com> <41EFAFB0.2000606@namesys.com> Reply-To: =?UTF-8?Q?Grzegorz_Ja=C5=9Bkiewicz?= Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: list-help: list-unsubscribe: list-post: Errors-To: flx@namesys.com In-Reply-To: <41EFAFB0.2000606@namesys.com> List-Id: Content-Type: text/plain; charset="us-ascii" To: Edward Shishkin Cc: Hans Reiser , Matthias Andree , hihone@bigpond.net.au, reiserfs-list@namesys.com All I know is that xxtea is fixed tea algo. If that fixes weakness in crypto algo, than so it should make hashing better. No doubt there is no ideal hash algo, but if base algo has weaknes, using fixed one only can be better, Right ? -- GJ