Re: [Trans] How to redact an entry

Paul Wouters <paul@nohats.ca> Wed, 16 November 2016 11:39 UTC

Return-Path: <paul@nohats.ca>
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 728BE1294E3 for <trans@ietfa.amsl.com>; Wed, 16 Nov 2016 03:39:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.497
X-Spam-Level:
X-Spam-Status: No, score=-3.497 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-1.497] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=nohats.ca
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 mhX92xwQY6_I for <trans@ietfa.amsl.com>; Wed, 16 Nov 2016 03:39:16 -0800 (PST)
Received: from mx.nohats.ca (mx.nohats.ca [IPv6:2a03:6000:1004:1::68]) (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 861AA129495 for <trans@ietf.org>; Wed, 16 Nov 2016 03:39:16 -0800 (PST)
Received: from localhost (localhost [IPv6:::1]) by mx.nohats.ca (Postfix) with ESMTP id 3tJj2n5yP6z2m; Wed, 16 Nov 2016 12:39:13 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1479296353; bh=xn1w2wXqoehQKuY+Bcm27udwPXvv00oOuWB5dBfoU2s=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=JA3qiHMw+MSKycPNc4gLZpURp/zz3tXM2pqYTYAg+9JuHB4I7HvlX4Omqu0ZPy1bz q8VhuTQgt1XyFM7xHSZVbetWYsWc55z6kEosRuwkNLay06D3g70lmG+Q37sJa8/cZQ evS/a6zH0ssLP5uRPVSKxw+prlzbrToMF01uaFrE=
X-Virus-Scanned: amavisd-new at mx.nohats.ca
Received: from mx.nohats.ca ([IPv6:::1]) by localhost (mx.nohats.ca [IPv6:::1]) (amavisd-new, port 10024) with ESMTP id H5VoC6bcZ13B; Wed, 16 Nov 2016 12:39:12 +0100 (CET)
Received: from bofh.nohats.ca (206-248-139-105.dsl.teksavvy.com [206.248.139.105]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx.nohats.ca (Postfix) with ESMTPS; Wed, 16 Nov 2016 12:39:12 +0100 (CET)
Received: by bofh.nohats.ca (Postfix, from userid 1000) id 0AA5A5C83A; Wed, 16 Nov 2016 06:39:12 -0500 (EST)
DKIM-Filter: OpenDKIM Filter v2.10.3 bofh.nohats.ca 0AA5A5C83A
Received: from localhost (localhost [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 0119240DAA4B; Wed, 16 Nov 2016 06:39:11 -0500 (EST)
Date: Wed, 16 Nov 2016 06:39:11 -0500
From: Paul Wouters <paul@nohats.ca>
To: Ben Laurie <benl@google.com>
In-Reply-To: <CABrd9STPBWt=p-eAW5t=QSw2oexuSeW5tbtcbczagA0jx77gQA@mail.gmail.com>
Message-ID: <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>
User-Agent: Alpine 2.20 (LRH 67 2015-01-07)
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/A7H9jGHbpq_KrncGkpawO6WRhVM>
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:39:17 -0000

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.

Paul