Re: [Trans] Mutability of Certificate Signatures

Andrew Ayer <agwa@andrewayer.name> Mon, 03 July 2017 17:02 UTC

Return-Path: <agwa@andrewayer.name>
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 BA6AB129A92 for <trans@ietfa.amsl.com>; Mon, 3 Jul 2017 10:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.102
X-Spam-Level:
X-Spam-Status: No, score=-0.102 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=andrewayer.name
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 XIShKxgLIIR8 for <trans@ietfa.amsl.com>; Mon, 3 Jul 2017 10:02:43 -0700 (PDT)
Received: from alcazar.beanwood.com (alcazar.beanwood.com [70.85.129.230]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3661C126BF6 for <trans@ietf.org>; Mon, 3 Jul 2017 10:02:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=andrewayer.name; s=beanwood20160511; t=1499101362; bh=te0DxPm97wG8am5+iPu9Sk1M3j5OTkXyzuwhjQdqs6Y=; h=Date:From:To:Subject:In-Reply-To:References; b=MFi6b6EIGVdcNe20p5Ov5BoTM7tK9K8YIMdLpGavqTyvAGZIig1+z75IEO9LNIIoC ChEkMni/bJw/OMJtimAB8X/NKQhHzn55iVCDJakXLspp30XxDK1h6loXkiav4Wnk3z TMWKN5qhXaT/71QP1eqV5AXoy1FAkH98g4mNoQHT8WQkJUKQWIdH1gMuh/yEZaHPTi Sx1w563iqCYMbYr5H3egGW2O9/UYvOJLShf4/hCNWiC+YNp7tVA//PGIEQx9h5FDQB 7N3tg4CGYDlhbIM5NG/ZxOZA7lihDlpYNv9nqjlZA267T+UHkBaa4zVqIopDgjLpNb 0CK2Jnw6xzo2g==
Date: Mon, 03 Jul 2017 10:02:41 -0700
From: Andrew Ayer <agwa@andrewayer.name>
To: trans@ietf.org
Message-Id: <20170703100241.9dd63b867d0181bae69a3999@andrewayer.name>
In-Reply-To: <20170528191028.20f285073eea33a3f23b6b5a@andrewayer.name>
References: <20170528191028.20f285073eea33a3f23b6b5a@andrewayer.name>
Mime-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/0crTTYwW1XP3In18L4vdhukVj-s>
Subject: Re: [Trans] Mutability of Certificate Signatures
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.22
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, 03 Jul 2017 17:02:45 -0000

To get the ball rolling again on fixing this issue, I've submitted a PR
which:

1. Changes issuer_key_hash to issuer_key.

2. Adds language to the Monitor section describing what checks a
monitor should do to detect signature mutation.

https://github.com/google/certificate-transparency-rfcs/pull/270

Regards,
Andrew