From: Jules Merit <jules.merit.eurocorp.us@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] SHA-1 collision and venti
Date: Sun, 26 Feb 2017 09:30:55 -0800 [thread overview]
Message-ID: <CAEVxPTPzbEkCHG4hcgLq_Hz+j4oX6E4uyL2o0hHwHVK6C7LsSg@mail.gmail.com> (raw)
In-Reply-To: <8D987F97-4760-4243-A9E7-F2F3BA9C63E3@bitblocks.com>
[-- Attachment #1: Type: text/plain, Size: 629 bytes --]
there is a backdoor when a score of 4, what data produces it i have no idea.
On Sun, Feb 26, 2017 at 9:25 AM, Bakul Shah <bakul@bitblocks.com> wrote:
> https://arstechnica.com/security/2017/02/watershed-
> sha1-collision-just-broke-the-webkit-repository-others-may-follow/
>
> https://shattered.io/static/shattered.pdf
>
> Venti is similarly corruptible, right? Since the checksum is over just the
> content. If you downloaded https://shattered.io/static/shattered-1.pdf
> <https://shattered.io/static/shattered-2.pdf> and
> https://shattered.io/static/shattered-2.pdf, venti would lose the
> contents of one.
>
[-- Attachment #2: Type: text/html, Size: 1336 bytes --]
next prev parent reply other threads:[~2017-02-26 17:30 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 [this message]
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
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=CAEVxPTPzbEkCHG4hcgLq_Hz+j4oX6E4uyL2o0hHwHVK6C7LsSg@mail.gmail.com \
--to=jules.merit.eurocorp.us@gmail.com \
--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).