From: Georg Lehner <jorge-plan9@magma.com.ni>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] In case anyone worries about block hash collision in venti
Date: Mon, 8 Feb 2010 22:58:50 +0100 [thread overview]
Message-ID: <4B70891A.8080508@magma.com.ni> (raw)
In-Reply-To: <Pine.BSI.4.64.1002070956420.5454@malasada.lava.net>
About a year ago i wrote a (kind of vapourware) backup system called Baccus,
based on content addressed storage. Most ideas are stolen from Plan9/venti,
but for the here discussed reasons i used the Salsa family of hashes
from Dan
Bernstein:
http://cr.yp.to/chacha.html
Respectively the Rumba-"compression":
http://cr.yp.to/rumba20.html
I combined hashing and encryption with Salsa/Rumba into one step.
The hash function in Baccus is pluggable, so the user could decide which to use
and would be able to upgrade to a stronger hash.
Maybe pluggability of the hash function would be a nice addition to venti
(if it is not there anyways). Also Salsa should be considered a valuable addition
to Plan9.
Regards,
Jorge-Le�n
P.S.: Here is the link to Baccus: http://wiki.tcl.tk/23064, but beware: it is in a bad
state and style. Didn't have time to improve since then. If you still want to look
at it, start with reading the CREDITS file.
PS2: You need at least eight rounds, else you get lots of hash-collisions.
Tim Newsham wrote:
>> 1. the sender can't control email headers. many
>> transfer agents add a random transfer-id which
>> would confound this attack.
>
> If you know the size of the transfer id, you can pad out
> to the next full block size.
>
>> 2. if the rcpt uses mbox format, the sender can't
>> control how your message is fit into venti blocks.
>> the sender would need to control the entire
>> mail box.
>
> I'm ignorant on this front.
>
>> 3. http://en.wikipedia.org/wiki/SHA_hash_functions
>> says that there have been no SHA1 collisions found.
>
> IIUC there has been significant progress in attacking
> all major hash functions and the cryptographic community
> has low confidence in all major hash functions at the
> moment. Some hash algorithms have more serious attacks
> than others, but once a few weaknesses are found its
> usually an indication that the algorithm will fall soon.
>
> Re: SHA1, it looks like the strenght has been whittled
> down to around 2^52 operations:
> http://www.schneier.com/blog/archives/2009/06/ever_better_cry.html
>
> I'm not saying that there is a viable attack against
> your SHA-indexed venti right now. I'm saying that its
> bunk to evaluate the storage system simply on how likely
> it is for a random collision to occur. The proper analysis
> is how hard it is for a malicious attacker to cause a
> collision now and in the near future.
>
>> - erik
>
> Tim Newsham | www.thenewsh.com/~newsham | thenewsh.blogspot.com
>
next prev parent reply other threads:[~2010-02-08 21:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-06 18:47 maht
2010-02-06 23:42 ` Tim Newsham
2010-02-07 4:47 ` erik quanstrom
2010-02-07 16:54 ` Tim Newsham
2010-02-07 17:44 ` erik quanstrom
2010-02-07 19:12 ` Don Bailey
2010-02-07 19:24 ` Nathaniel W Filardo
2010-02-07 22:08 ` matt
2010-02-08 23:37 ` Nathaniel W Filardo
2010-02-09 13:13 ` hiro
2010-02-09 13:50 ` ron minnich
2010-02-09 14:54 ` erik quanstrom
2010-02-07 20:03 ` Tim Newsham
2010-02-08 21:58 ` Georg Lehner [this message]
2010-02-07 20:21 ` [9fans] In case anyone worries about block hash collision in Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-02-07 20:31 ` erik quanstrom
2010-02-07 20:57 ` Lyndon Nerenberg (VE6BBM/VE7TFX)
2010-02-07 23:25 ` Akshat Kumar
2010-02-08 0:37 ` Russ Cox
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=4B70891A.8080508@magma.com.ni \
--to=jorge-plan9@magma.com.ni \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).