Re: [Trans] WGLC started for draft-ietf-trans-threat-analysis

"David A. Cooper" <david.cooper@nist.gov> Thu, 10 May 2018 18:47 UTC

Return-Path: <david.cooper@nist.gov>
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 BB77112EB82 for <trans@ietfa.amsl.com>; Thu, 10 May 2018 11:47:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.477
X-Spam-Level:
X-Spam-Status: No, score=-3.477 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_HTML_ONLY=0.723, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-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 itC_PzWhMSZp for <trans@ietfa.amsl.com>; Thu, 10 May 2018 11:47:20 -0700 (PDT)
Received: from wsget1.nist.gov (wsget1.nist.gov [IPv6:2610:20:6005:13::150]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 597BD127077 for <trans@ietf.org>; Thu, 10 May 2018 11:47:20 -0700 (PDT)
Received: from WSGHUB2.xchange.nist.gov (129.6.42.35) by wsget1.nist.gov (129.6.13.150) with Microsoft SMTP Server (TLS) id 14.3.389.1; Thu, 10 May 2018 14:48:32 -0400
Received: from postmark.nist.gov (129.6.16.94) by mail-g.nist.gov (129.6.42.33) with Microsoft SMTP Server id 14.3.389.1; Thu, 10 May 2018 14:47:18 -0400
Received: from [129.6.105.183] (cooper-optiplex-9010.campus.nist.gov [129.6.105.183]) by postmark.nist.gov (8.13.8/8.13.1) with ESMTP id w4AIkJNP006336; Thu, 10 May 2018 14:46:19 -0400
To: Stephen Kent <s@zerho.info>
CC: Paul Wouters <paul@nohats.ca>, Melinda Shore <melinda.shore@gmail.com>, Trans <trans@ietf.org>
References: <alpine.LRH.2.21.1804161658150.17034@bofh.nohats.ca> <cf3fd01c-a1f2-0cd0-d1a2-cda7b9558986@nist.gov> <IUUXIbDImicbov7jLKxe4l9QVrF_cCO0F1_mY4LpATYvr-Eag7fAJwnwqnviKXU3drx1vKgpuE6hkehmUMBq2QzPSKNKaMdM3D6LIMv2Gig=@zerho.info>
From: "David A. Cooper" <david.cooper@nist.gov>
Message-ID: <ae377620-e14b-8b36-11dd-a686677cf929@nist.gov>
Date: Thu, 10 May 2018 14:46:20 -0400
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <IUUXIbDImicbov7jLKxe4l9QVrF_cCO0F1_mY4LpATYvr-Eag7fAJwnwqnviKXU3drx1vKgpuE6hkehmUMBq2QzPSKNKaMdM3D6LIMv2Gig=@zerho.info>
Content-Type: text/html; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-NIST-MailScanner-Information:
Archived-At: <https://mailarchive.ietf.org/arch/msg/trans/RWqHKhUGbB_xXVURtG4Jplk7jzI>
Subject: Re: [Trans] WGLC started for draft-ietf-trans-threat-analysis
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: Thu, 10 May 2018 18:47:23 -0000

I have been unable to find anywhere in my comments where I suggested that syntactic mis-issuance should not be discussed in the document. The "responses" you provided have nothing to do with my comments.

On 05/09/2018 08:49 AM, Stephen Kent wrote:
  1. Section 4.2.2 says "However, even if errors are detected and reported to the CA, a malicious/conspiring CA may do nothing to fix the problem or may delay action." As noted previously, no explanation is provided as to why this is a threat or attack. If the Subject knows that there are errors in the certificate, then the Subject can just get another certificate (from a different CA, if necessary). It doesn't matter whether the CA revokes the erroneous certificate or not.

See previous comment on why syntactic mis-issuance is included in this document.

  1. Section 5.6, paragraph 5 says "If a Monitor is compromised by, or conspires with, an attacker, it will fail to alert a Subject to a bogus or erroneous certificate targeting that Subject, as noted above." As noted previously, this document needs to explain how an attacker can "target" a Subject with an erroneous certificate.

As noted above, Ben insisted that syntactically erroneous certificates were considered mis-issued, and hence motivated inclusion of the text in Section 4.