From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] In case anyone worries about block hash collision in venti
Date: Tue, 9 Feb 2010 09:54:25 -0500 [thread overview]
Message-ID: <499ca953b8167a8bd777b0785a696bba@ladd.quanstro.net> (raw)
In-Reply-To: <13426df11002090550x73f75e99i8983be3c6596deba@mail.gmail.com>
> > If you are really paranoid and don't want any collisions in the next
> > 10 years: don't let strangers in your venti.
>
> Which, to close the circle, as Tim points out, you are always doing,
> each time you receive an email :-)
not all email is from strangers.
in mbox format, messages are concatinated. for a block
size of b, the size of the existing mailbox is 0 ... b-1 mod b.
therefore, there is a 1/b chance of the attack succeeding, even
if the attacker knows the block size and pads to the next
block. i suppose that this is a fair assumption, since we're
given that the attacker is attacking venti.
this is esentially the same reason that mbox format will eat alot
of storage, even if you're using venti.
- erik
next prev parent reply other threads:[~2010-02-09 14:54 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 [this message]
2010-02-07 20:03 ` Tim Newsham
2010-02-08 21:58 ` Georg Lehner
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=499ca953b8167a8bd777b0785a696bba@ladd.quanstro.net \
--to=quanstro@quanstro.net \
--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).