[Acme] Clarification on usage of account key pair with regards to certificate issuance
"Peter Panburana (pepanbur)" <pepanbur@cisco.com> Thu, 18 February 2016 21:05 UTC
Return-Path: <pepanbur@cisco.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DCB091B357B for <acme@ietfa.amsl.com>; Thu, 18 Feb 2016 13:05:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.506
X-Spam-Level:
X-Spam-Status: No, score=-14.506 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.006, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] 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 BrkAkA5AjVOc for <acme@ietfa.amsl.com>; Thu, 18 Feb 2016 13:05:23 -0800 (PST)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 134B31B3556 for <acme@ietf.org>; Thu, 18 Feb 2016 13:04:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=3475; q=dns/txt; s=iport; t=1455829496; x=1457039096; h=from:to:subject:date:message-id:mime-version; bh=LI03pC+TB2xgAR6t9IglubD0fRMTHRss4CLUd+dTZx0=; b=HDWMUyaJOSQ/7xRGGLY7Lw0dgX1zg64nbiHQpIm1PKoqHuCE0HNXM5jG I0r3UPiN4N/PkHQdJGbMHI1xiUtks2nnEKp+/uFwWGykBMqnwPkKD/nO8 Hkkn1ALnw0TQ/9HRCS959KKBw7wJQAeWqSJUD0795GSrvwGaQfU++woa7 A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0BPBQC6McZW/4QNJK1egm5MUnO1DIUUAQ2BZ4d4OBQBAQEBAQEBZBwLhEgtXgEMKUsmAQQbDIgGnUyebAEBAQEGAQEBARyGEokvg3sFlwUBjVKOemcEjVsBHgEBQoNjiQ0BewEBAQ
X-IronPort-AV: E=Sophos;i="5.22,467,1449532800"; d="scan'208,217";a="240169794"
Received: from alln-core-10.cisco.com ([173.36.13.132]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 18 Feb 2016 21:04:45 +0000
Received: from XCH-RCD-002.cisco.com (xch-rcd-002.cisco.com [173.37.102.12]) by alln-core-10.cisco.com (8.14.5/8.14.5) with ESMTP id u1IL4jND027382 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <acme@ietf.org>; Thu, 18 Feb 2016 21:04:45 GMT
Received: from xch-aln-005.cisco.com (173.36.7.15) by XCH-RCD-002.cisco.com (173.37.102.12) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Thu, 18 Feb 2016 15:04:46 -0600
Received: from xch-aln-005.cisco.com ([173.36.7.15]) by XCH-ALN-005.cisco.com ([173.36.7.15]) with mapi id 15.00.1104.009; Thu, 18 Feb 2016 15:04:44 -0600
From: "Peter Panburana (pepanbur)" <pepanbur@cisco.com>
To: "acme@ietf.org" <acme@ietf.org>
Thread-Topic: Clarification on usage of account key pair with regards to certificate issuance
Thread-Index: AdFqjiI+xCo2wTk+S5SdpK5MAyd3ig==
Date: Thu, 18 Feb 2016 21:04:44 +0000
Message-ID: <89bd35285eec45c2976a99c962df4f8d@XCH-ALN-005.cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [64.102.57.106]
Content-Type: multipart/alternative; boundary="_000_89bd35285eec45c2976a99c962df4f8dXCHALN005ciscocom_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/acme/l7F2vvpBRa_dKuPDhFIsB5YdrYM>
Subject: [Acme] Clarification on usage of account key pair with regards to certificate issuance
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Automated Certificate Management Environment <acme.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/acme>, <mailto:acme-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme/>
List-Post: <mailto:acme@ietf.org>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/acme>, <mailto:acme-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 18 Feb 2016 21:05:30 -0000
Hello, I was browsing through the Let's Encrypt community support forum I saw a discussion regarding the usage of an ACME account key pair and the creation of a CSR for enrollment. The replies in that thread indicated that account keys cannot be used to create that a CSR that an ACME client wishes to enroll. I would like to know if a normative statement should be included in the draft, possibly in the certificate issuance section, stating that a client MUST enroll CSRs with a private key that is different than the ACME account private key. Thank you, Peter
- [Acme] Clarification on usage of account key pair… Peter Panburana (pepanbur)