Re: [Trans] Reviving Redaction

Rob Stradling <rob.stradling@comodo.com> Mon, 06 March 2017 21:39 UTC

Return-Path: <rob.stradling@comodo.com>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EBE401294A9 for <trans@ietfa.amsl.com>; Mon, 6 Mar 2017 13:39:31 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hrOdTQkdGvSe for <trans@ietfa.amsl.com>; Mon, 6 Mar 2017 13:39:29 -0800 (PST)
Received: from dwdccgokm1.dela.clif.dc.comodo.net (sgomail.comodogroup.com [IPv6:2a02:1788:400:430::d201:8a76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9F2FF129A47 for <trans@ietf.org>; Mon, 6 Mar 2017 13:39:29 -0800 (PST)
Received: (korumail 30140 invoked from network); 6 Mar 2017 21:39:28 -0000
Received: from unknown (HELO maileu.comodo.net) () by 0 with SMTP; 6 Mar 2017 21:39:28 -0000
Received: from [192.168.0.58] ([192.168.0.58]) by maileu.comodo.net (IceWarp 11.4.5.0 DEB8 x64) with ASMTP (SSL) id 201703062139273630; Mon, 06 Mar 2017 21:39:27 +0000
To: Ben Laurie <benl@google.com>
References: <CAK6vND826Sy6hH1Gf0gnP0T8dGUyRQmGe408UPp0oKgnkzfK+w@mail.gmail.com> <af9dc8c9-1ea3-1862-fb6e-0020b3ea4361@comodo.com> <CABrd9SQqdgs-DtcP830tA8wXDekguaET2y8N+3L1PqNc7NTbTQ@mail.gmail.com>
From: Rob Stradling <rob.stradling@comodo.com>
Message-ID: <8acee1f6-2df5-af74-640f-2ed836a81d90@comodo.com>
Date: Mon, 06 Mar 2017 21:39:26 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.7.0
MIME-Version: 1.0
In-Reply-To: <CABrd9SQqdgs-DtcP830tA8wXDekguaET2y8N+3L1PqNc7NTbTQ@mail.gmail.com>
X-SMTP-Filter: Korumail SMTP Filter Engine Korumail 6.5
X-KORUMAIL-Result: Clean (Content eval: 0.000000 points)
X-KORUMAIL-Reason:
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/jXhh5sZnSVbZv1i8tjqYgE3faR8>
Cc: "trans@ietf.org" <trans@ietf.org>, Peter Bowen <pzbowen@gmail.com>
Subject: Re: [Trans] Reviving Redaction
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Public Notary Transparency working group discussion list <trans.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/trans>, <mailto:trans-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/trans/>
List-Post: <mailto:trans@ietf.org>
List-Help: <mailto:trans-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/trans>, <mailto:trans-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 06 Mar 2017 21:39:32 -0000

On 06/03/17 21:22, Ben Laurie wrote:
> I think you can waste a lot of brainpower on redaction, but really the
> answer is: if you don't want to publish your names, then don't use a
> mechanism that requires you to.

I agree that that's the ideal answer, but as we've seen, there is 
resistance to that answer from various participants in the CT ecosystem.

> There are alternatives: name-constrained sub-CAs.

We removed that option from 6962-bis.  It's now in 
draft-strad-trans-redaction, but IIRC the Chrome team hinted that 
they're unlikely to ever support it (at least in its current form).

> Private CAs. You can even have private CT to go along with them.

Private CAs don't suit every use case, AFAIK.

> Why mess up a protocol whose intent is to show everything?

Because Security and Useability aren't always in perfect harmony?

Much as I'd love to stop wasting brainpower on redaction, I think it's a 
conversation that needs to continue for now (although not indefinitely!)

> On 6 March 2017 at 21:16, Rob Stradling wrote:
>
>     On 06/03/17 06:06, Peter Bowen wrote:
>     <snip>
>
>         8) The only way to get the content of a full certificate is to
>         have a
>         full certificate.
>
>         Rationale: An alternative option is to have some sort of escrow key
>         that can "unlock" a precertificate.
>
>
>     In previous iterations of 6962-bis, we proposed a redaction
>     mechanism that envisaged replacing domains labels with ?s in
>     precertificates. That mechanism was deemed problematic by the Chrome
>     team precisely because "The only way to get the content of a full
>     certificate is to have a full certificate".
>     What recourse does a domain owner have when they discover a
>     precertificate for their domain space that they don't recognize?
>     How do they figure out whether the (pre)cert was misissued or
>     whether it was legitimately requested by a different team within
>     their organization?
>
>     The redaction mechanism that's documented in
>     https://tools.ietf.org/html/draft-strad-trans-redaction-01#section-3.3
>     <https://tools.ietf.org/html/draft-strad-trans-redaction-01#section-3.3>
>     attempted to find a solution to this problem of recourse by swapping
>     ?s for a hash of the unredacted domain.  However, this mechanism has
>     also been deemed problematic, because it could be trivial to
>     determine unredacted labels via dictionary attacks.
>
>     I think a "sort of escrow key" may be the only viable way to
>     construct a redaction mechanism that is deemed non-problematic by
>     everyone.
>
>         This quickly turns into 'where do we keep the escrow key?' and
>         'who gets
>         to access the escrow key?'.  If there is no such thing, then these
>         questions don't exist.
>
>
>     I think these questions will need to be both asked and answered,
>     although I'd be delighted to be proved wrong.
>
>         Do others agree that these are true and can be used as givens for
>         reviewing any proposed designs?
>
>
>     Your other points all LGTM.
>
>     --
>     Rob Stradling
>     Senior Research & Development Scientist
>     COMODO - Creating Trust Online
>
>
>     _______________________________________________
>     Trans mailing list
>     Trans@ietf.org <mailto:Trans@ietf.org>
>     https://www.ietf.org/mailman/listinfo/trans
>     <https://www.ietf.org/mailman/listinfo/trans>
>
>

-- 
Rob Stradling
Senior Research & Development Scientist
COMODO - Creating Trust Online
Office Tel: +44.(0)1274.730505
Office Fax: +44.(0)1274.730909
www.comodo.com

COMODO CA Limited, Registered in England No. 04058690
Registered Office:
   3rd Floor, 26 Office Village, Exchange Quay,
   Trafford Road, Salford, Manchester M5 3EQ

This e-mail and any files transmitted with it are confidential and 
intended solely for the use of the individual or entity to whom they are 
addressed.  If you have received this email in error please notify the 
sender by replying to the e-mail containing this attachment. Replies to 
this email may be monitored by COMODO for operational or business 
reasons. Whilst every endeavour is taken to ensure that e-mails are free 
from viruses, no liability can be accepted and the recipient is 
requested to use their own virus checking software.