Re: [Trans] Certificate verification

Paul Wouters <paul@nohats.ca> Mon, 20 October 2014 17:45 UTC

Return-Path: <paul@nohats.ca>
X-Original-To: trans@ietfa.amsl.com
Delivered-To: trans@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 627CF1A88C2 for <trans@ietfa.amsl.com>; Mon, 20 Oct 2014 10:45:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level:
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 HN76UIKILP4O for <trans@ietfa.amsl.com>; Mon, 20 Oct 2014 10:45:00 -0700 (PDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [76.10.157.69]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54C3C1A88F3 for <trans@ietf.org>; Mon, 20 Oct 2014 10:44:59 -0700 (PDT)
Received: from bofh.nohats.ca (bofh.nohats.ca [127.0.0.1]) by bofh.nohats.ca (Postfix) with ESMTP id 5874080055; Mon, 20 Oct 2014 13:44:58 -0400 (EDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nohats.ca; s=default; t=1413827098; bh=AweHjXYTE8Ti/v/4gjE3+mdV/HQTn/JFlrPrtcnIjto=; h=Date:From:To:cc:Subject:In-Reply-To:References; b=DqfrebdCwAKkiyip3z62WugXZG14IhNQq+kSIkrKCBBLRtXlb7UVZBNFIqYXJB9Iw O0Uyid8T1VsfZukSRUJWE03xRwLRdy42oMkiMf68fiznNFMBc6kOUM1r+oxNz6lTzr SrihnFPW6M6fo8BTXpxHiyTJVpzS29XCdtpmKUig=
Received: from localhost (paul@localhost) by bofh.nohats.ca (8.14.7/8.14.7/Submit) with ESMTP id s9KHivhA005785; Mon, 20 Oct 2014 13:44:58 -0400
X-Authentication-Warning: bofh.nohats.ca: paul owned process doing -bs
Date: Mon, 20 Oct 2014 13:44:57 -0400
From: Paul Wouters <paul@nohats.ca>
To: Linus Nordberg <linus@nordu.net>
In-Reply-To: <87ppdmhqg7.fsf@nordberg.se>
Message-ID: <alpine.LFD.2.10.1410201340380.1071@bofh.nohats.ca>
References: <871tq6uaf1.fsf@nordberg.se> <CABrd9STBA9jh6oHXBzEgUD73rWDRbgrFZc69H5tHOzD4Cw=WHg@mail.gmail.com> <87ppdmhqg7.fsf@nordberg.se>
User-Agent: Alpine 2.10 (LFD 1266 2009-07-14)
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: http://mailarchive.ietf.org/arch/msg/trans/-Xcd5635tqSIZqBjZ6Up8s_LXmA
Cc: trans@ietf.org
Subject: Re: [Trans] Certificate verification
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 20 Oct 2014 17:45:02 -0000

On Mon, 20 Oct 2014, Linus Nordberg wrote:

as individual without chair hat...

>   Logs MUST verify that the submitted end-entity certificate or

> My intention was to make the specification less restrictive by changing
>
>                               Logs MAY accept certificates that have
>   expired, are not yet valid, have been revoked, or are otherwise not
>   fully valid according to X.509 verification rules in order to
>   accommodate quirks of CA certificate-issuing software.

That seems to bring up the topic a bit too broadly I think? How about:

 	Logs MUST protect themselves against spam. They MAY require a
 	fully validated X.509 certification chain to one of their configured
 	trusted root CA's.

That leaves out the discussion for other checks, that may or may not go
into a separate section or document.

Paul