From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] SHA-1 collision and venti
Date: Wed, 1 Mar 2017 04:21:23 -0800 [thread overview]
Message-ID: <709dd5d94812538d1d9809559ba2eeb3@mule> (raw)
In-Reply-To: <CAOw7k5jZ9Kvf-gu7k=sOwON66G9fqX5PJN7A7_amdK2biN-R4w@mail.gmail.com>
On Mon Feb 27 14:17:49 PST 2017, charles.forsyth@gmail.com wrote:
> I think venti could deal with it: Rwrite returns a score, Tread provides a
> score, and the caller typically uses it as an opaque value. If not, whether
> a different sha1 is returned or a new algorithm is used, the caller could
> still not rely on sha1(block)=score.
>
> In any case, fossil needs a fix to cope with venti returning "score
> collision", to prevent it failing to archive once it hits a shattered file,
> or rather the first venti-sized block of them.
i believe that rsc worked this out in some work he did based on venti.
sadly i don't remember the name of the project.
a modest proposal. since p(collison) is calculated for a random collison,
why not just store encrypted blocks.
- erik
next prev parent reply other threads:[~2017-03-01 12:21 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-26 17:25 Bakul Shah
2017-02-26 17:30 ` Jules Merit
2017-02-26 18:29 ` Charles Forsyth
2017-02-26 18:16 ` Charles Forsyth
2017-02-26 18:25 ` Charles Forsyth
2017-02-26 19:46 ` Bakul Shah
2017-02-26 21:02 ` Kim Shrier
2017-02-27 15:46 ` Dave MacFarlane
2017-02-27 16:47 ` Charles Forsyth
2017-02-27 17:07 ` Charles Forsyth
2017-02-27 17:28 ` Bakul Shah
2017-02-27 18:14 ` hiro
2017-02-27 18:20 ` Bakul Shah
2017-02-27 18:30 ` Charles Forsyth
2017-02-27 19:02 ` Charles Forsyth
2017-02-27 20:05 ` cinap_lenrek
2017-02-27 20:14 ` Bakul Shah
2017-02-27 21:12 ` Riddler
2017-02-27 22:20 ` Charles Forsyth
2017-03-01 12:21 ` erik quanstrom [this message]
2017-03-01 12:35 ` David du Colombier
2017-02-27 19:34 ` Skip Tavakkolian
2017-02-26 18:48 ` Bakul Shah
2017-02-26 19:57 ` Charles Forsyth
2017-02-26 20:06 ` Jadon Bennett
2017-02-26 20:16 ` Bakul Shah
2017-02-28 15:47 Darren Wise
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=709dd5d94812538d1d9809559ba2eeb3@mule \
--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).