Re: [Trans] How to redact an entry

Ben Laurie <benl@google.com> Wed, 16 November 2016 11:48 UTC

Return-Path: <benl@google.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 BF09C129793 for <trans@ietfa.amsl.com>; Wed, 16 Nov 2016 03:48:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.498
X-Spam-Level:
X-Spam-Status: No, score=-3.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RP_MATCHES_RCVD=-1.497, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
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 Ev-TADq18-mt for <trans@ietfa.amsl.com>; Wed, 16 Nov 2016 03:48:25 -0800 (PST)
Received: from mail-ua0-x232.google.com (mail-ua0-x232.google.com [IPv6:2607:f8b0:400c:c08::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 531BB129494 for <trans@ietf.org>; Wed, 16 Nov 2016 03:48:25 -0800 (PST)
Received: by mail-ua0-x232.google.com with SMTP id 12so111914928uas.2 for <trans@ietf.org>; Wed, 16 Nov 2016 03:48:25 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CQnp/TaHzc1NzV5qhWm1aEMzUuKCMWSNYuJIU+FOJuw=; b=RId74NJ/THsSXviVyN+r9K8bETr+rCBSl0Q+yzP8tMbGPpebsVNPfbXvbeQMH9HL4/ NTVPP7uB2qxT0AwX5JLjqSHKXXDXPol/j3f6piRRR+4+HeMtsK7no07+0mXgWQske/M8 ljc23tjMTbvHIZ87WfxP9KXsFvBYWcmJMRGsuyINQboCjpd3GxDjt9lw1c2DAU3smMqv NsWPrSM/4bUwhAV+iFyOhT6nWbmCgHLt24Jvshc9k5CYfIJwKIBPc0hADOY40bPTGF93 RD9f0yeIv2a0W6PNdS306p1hvBM8PutD60it0TtlAUj+0JiVUFUL4Dzf6vGDAMjADrn0 OaJA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CQnp/TaHzc1NzV5qhWm1aEMzUuKCMWSNYuJIU+FOJuw=; b=g3DXa2yGL6+6Cs0r14P4lMJ6qVWRrJ3umhfMt1S5osupPnzNe2FtZt8XGK0lVg6eP/ cvGpfRnWIfQuDOqIrM6T6r3kkhempCJTisPMPaOk0D3wvA0XioqLtOfWYxYK6bcgpTLe XS7xlZkVUBHyKJekZUhyVD2jQVf7qGoOO7en1P0VSG4G7RQaXpEZbDM7HLZZ1XuqsudS Bi1/7A4dYA94VifASLH2BVDSXd0hU1HSJixnpX0x7c7Ilmi0phTRUccW8siFSZOLAGRb P2XJswNM7qDfRSoISLWwPbJr3TPfunuY1Ac4tJzItwK7/ITHYhzgZv08AnU6YuF2Pmo2 B2ag==
X-Gm-Message-State: ABUngvfKa2XDacNorFHL0uEhvR9BXd9iclCkuz4ObO7I6CxbKN8YP1f2fKNFaxY1BwRI7F45cU/p7UMqYMms6TXc
X-Received: by 10.176.84.66 with SMTP id o2mr1387292uaa.148.1479296904303; Wed, 16 Nov 2016 03:48:24 -0800 (PST)
MIME-Version: 1.0
Received: by 10.31.140.82 with HTTP; Wed, 16 Nov 2016 03:48:19 -0800 (PST)
In-Reply-To: <alpine.LRH.2.20.1611160636020.4488@bofh.nohats.ca>
References: <CABrd9SSeePrsNq8ERjxpbEvUAdyb=yQOGAom0qh9SZMoP=nsMw@mail.gmail.com> <CAMm+LwiZUw+JpEanY5vkxGBOtdrs9HfYzp34cBtwDv34uJCjKw@mail.gmail.com> <4E665C5B-BC28-428E-9BFB-626D3364E05B@nohats.ca> <CABrd9STPBWt=p-eAW5t=QSw2oexuSeW5tbtcbczagA0jx77gQA@mail.gmail.com> <alpine.LRH.2.20.1611160636020.4488@bofh.nohats.ca>
From: Ben Laurie <benl@google.com>
Date: Wed, 16 Nov 2016 11:48:19 +0000
Message-ID: <CABrd9SQjMkWCOv1jPky+DiOE61qCTXej2Ovy9nRVAKs66OtEGA@mail.gmail.com>
To: Paul Wouters <paul@nohats.ca>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/3afKSCSKBFUQRLR38M-03Womsc0>
Cc: Phillip Hallam-Baker <ietf@hallambaker.com>, "trans@ietf.org" <trans@ietf.org>
Subject: Re: [Trans] How to redact an entry
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: Wed, 16 Nov 2016 11:48:27 -0000

On 16 November 2016 at 11:39, Paul Wouters <paul@nohats.ca> wrote:
> On Wed, 16 Nov 2016, Ben Laurie wrote:
>
> (no hats on)
>
>> On 16 November 2016 at 03:46, Paul Wouters <paul@nohats.ca> wrote:
>>>
>>> How can I as log consumer detect the difference between the log removing
>>> illegal content and the log being compelled by a government to hide a
>>> rogue
>>> certificate?
>>
>>
>> Court orders are court orders. That issue is not in the log's domain.
>
>
> It was an example. the core isuse is, how can a consumer determine the
> log censored itself with a valid reason, versus an attack, compromise,
> having been compelled, or for financial gain or any other invalid reason?
>
> Using a hash of a removed cert won't allow anyone to verify the reason
> for removal. And clearly the content cannot remain their either. It's
> a catch22.

This is why the redaction reason entry exists, so that there _is_
something to reason about. If you (a consumer) are unconvinced by the
reason, well, there are public fora where you can voice your concerns.