Re: [Trans] [trans] #80 (rfc6962-bis): Re-introduce the issuer key hash into the Precertificate
"trans issue tracker" <trac+trans@tools.ietf.org> Wed, 01 July 2015 13:31 UTC
Return-Path: <trac+trans@tools.ietf.org>
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 DEE6C1A88C8 for <trans@ietfa.amsl.com>; Wed, 1 Jul 2015 06:31:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level:
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 cyTqtA5McsGM for <trans@ietfa.amsl.com>; Wed, 1 Jul 2015 06:31:53 -0700 (PDT)
Received: from zinfandel.tools.ietf.org (zinfandel.tools.ietf.org [IPv6:2001:1890:123a::1:2a]) (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 509AD1A88BA for <trans@ietf.org>; Wed, 1 Jul 2015 06:31:52 -0700 (PDT)
Received: from localhost ([::1]:48311 helo=zinfandel.tools.ietf.org) by zinfandel.tools.ietf.org with esmtp (Exim 4.82_1-5b7a7c0-XX) (envelope-from <trac+trans@tools.ietf.org>) id 1ZAI78-0004R6-2v; Wed, 01 Jul 2015 06:31:46 -0700
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: trans issue tracker <trac+trans@tools.ietf.org>
X-Trac-Version: 0.12.3
Precedence: bulk
Auto-Submitted: auto-generated
X-Mailer: Trac 0.12.3, by Edgewall Software
To: rob.stradling@comodo.com, benl@google.com
X-Trac-Project: trans
Date: Wed, 01 Jul 2015 13:31:46 -0000
X-URL: http://tools.ietf.org/trans/
X-Trac-Ticket-URL: http://trac.tools.ietf.org/wg/trans/trac/ticket/80#comment:2
Message-ID: <071.c81f364e44d1309a40428e9c5ce00b63@tools.ietf.org>
References: <056.7955c32a9fd14002205eaf236136fda6@tools.ietf.org>
X-Trac-Ticket-ID: 80
In-Reply-To: <056.7955c32a9fd14002205eaf236136fda6@tools.ietf.org>
X-SA-Exim-Connect-IP: ::1
X-SA-Exim-Rcpt-To: rob.stradling@comodo.com, benl@google.com, trans@ietf.org
X-SA-Exim-Mail-From: trac+trans@tools.ietf.org
X-SA-Exim-Scanned: No (on zinfandel.tools.ietf.org); SAEximRunCond expanded to false
Archived-At: <http://mailarchive.ietf.org/arch/msg/trans/E50nPUG-XpyyNb94RbsSmgzYEgA>
Cc: trans@ietf.org
Subject: Re: [Trans] [trans] #80 (rfc6962-bis): Re-introduce the issuer key hash into the Precertificate
X-BeenThere: trans@ietf.org
X-Mailman-Version: 2.1.15
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, 01 Jul 2015 13:31:59 -0000
#80: Re-introduce the issuer key hash into the Precertificate Comment (by benl@google.com): I don't understand this problem. The I-D says "SignedData.signerInfos MUST contain a signature from the same (root or intermediate) CA that will ultimately issue the certificate." signerInfos includes "SignerIdentifier ::= CHOICE { issuerAndSerialNumber IssuerAndSerialNumber, subjectKeyIdentifier [0] SubjectKeyIdentifier }" Surely this is sufficient to identify the issuer? -- ------------------------------+--------------------------------------- Reporter: eranm@google.com | Owner: rob.stradling@comodo.com Type: defect | Status: assigned Priority: major | Milestone: Component: rfc6962-bis | Version: Severity: - | Resolution: Keywords: | ------------------------------+--------------------------------------- Ticket URL: <http://trac.tools.ietf.org/wg/trans/trac/ticket/80#comment:2> trans <http://tools.ietf.org/trans/>
- [Trans] [trans] #80 (client-behavior): Re-introdu… trans issue tracker
- Re: [Trans] [trans] #80 (rfc6962-bis): Re-introdu… trans issue tracker
- Re: [Trans] [trans] #80 (rfc6962-bis): Re-introdu… trans issue tracker
- Re: [Trans] [trans] #80 (rfc6962-bis): Re-introdu… trans issue tracker
- Re: [Trans] [trans] #80 (rfc6962-bis): Re-introdu… trans issue tracker
- Re: [Trans] [trans] #80 (rfc6962-bis): Re-introdu… trans issue tracker
- Re: [Trans] [trans] #80 (rfc6962-bis): Re-introdu… Stephen Kent
- Re: [Trans] [trans] #80 (rfc6962-bis): Re-introdu… Rob Stradling
- Re: [Trans] [trans] #80 (rfc6962-bis): Re-introdu… trans issue tracker
- Re: [Trans] [trans] #80 (rfc6962-bis): Re-introdu… trans issue tracker
- Re: [Trans] [trans] #80 (rfc6962-bis): Re-introdu… trans issue tracker