Re: [Acme] Add badPublicKey error

"Salz, Rich" <rsalz@akamai.com> Thu, 24 January 2019 16:19 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: acme@ietfa.amsl.com
Delivered-To: acme@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 19860130F65 for <acme@ietfa.amsl.com>; Thu, 24 Jan 2019 08:19:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.253
X-Spam-Level:
X-Spam-Status: No, score=-5.253 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-4.553, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, KHOP_DYNAMIC=2, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
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 j72Qbp4mOvoo for <acme@ietfa.amsl.com>; Thu, 24 Jan 2019 08:19:30 -0800 (PST)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C5839130F62 for <acme@ietf.org>; Thu, 24 Jan 2019 08:19:30 -0800 (PST)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x0OGGuNG001539; Thu, 24 Jan 2019 16:19:30 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=rR4C7ogO9K34MnIssAfC3M5OU5s25VaDJBVltm//N5w=; b=iMqbgAvtWsFDF3T/hiEjLh+g5kDUGpydb2Lzx7yN4V3orzwKVLTeqmbJblIumzuvRrpi JL2AUtS4hV9upzwHBE+dg+r/pROLUgZ7P85DKb59JhRlj0AeKOOW96uFF3we1vsQRrZM yJRvKMZ2sYoFmVXO6tZqs4Y0Bs/dhUYT5Kv3kbprPuKwGT3j3nLuKBTDL/uhw5JS64qP NYO3gFKOqhDMWhZGQpVZsPiByDgFQZt7ruJfaqP5Jk1R5JGDygZ30l9Lmn1KbHz1fpBS SK4c+HNU81Vx1CPopqzIY5A6Reg92N69O0WRGwxjSEV/Rtjbg2aubBJ7cZ9+8yJGKHWM Vw==
Received: from prod-mail-ppoint4 (a96-6-114-87.deploy.static.akamaitechnologies.com [96.6.114.87] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2q77a51pas-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 24 Jan 2019 16:19:30 +0000
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x0OGHOwk006844; Thu, 24 Jan 2019 11:19:29 -0500
Received: from email.msg.corp.akamai.com ([172.27.27.25]) by prod-mail-ppoint4.akamai.com with ESMTP id 2q4j1fj8ux-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 24 Jan 2019 11:19:28 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.27.101) by ustx2ex-dag1mb6.msg.corp.akamai.com (172.27.27.107) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 24 Jan 2019 08:18:49 -0800
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.6.131]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.6.131]) with mapi id 15.00.1365.000; Thu, 24 Jan 2019 10:18:49 -0600
From: "Salz, Rich" <rsalz@akamai.com>
To: Richard Barnes <rlb@ipv.sx>
CC: Rob Stradling <rob@sectigo.com>, IETF ACME <acme@ietf.org>
Thread-Topic: [Acme] Add badPublicKey error
Thread-Index: AQHUs/yhXjpTc1TqLUWb5bD5FlAzZqW++uKA//+u4AA=
Date: Thu, 24 Jan 2019 16:18:48 +0000
Message-ID: <5ACA2147-4AD4-46D9-8C34-9B28FF0FB9B1@akamai.com>
References: <D39A5FF3-5D2F-4C3D-9741-BB14A51E1744@akamai.com> <CAL02cgQP1g-oBLp7F=p0OMmE1Dv_fkZ5MK-ju2LmbRc_QHScHA@mail.gmail.com>
In-Reply-To: <CAL02cgQP1g-oBLp7F=p0OMmE1Dv_fkZ5MK-ju2LmbRc_QHScHA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.15.0.190115
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.43.77]
Content-Type: multipart/alternative; boundary="_000_5ACA21474AD446D98C349B28FF0FB9B1akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-01-24_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=683 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1901240114
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-01-24_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=678 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1901240114
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/LThr3zmq_D3M1z9MmEHIVeBvwyI>
Subject: Re: [Acme] Add badPublicKey error
X-BeenThere: acme@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Jan 2019 16:19:33 -0000

  *   Note that since the registration policy is "specification required", doing this in an extension spec instead would not require the consent of the IESG.

Right, which is how I prefer to see this move forward.  Putting it into the ACME doc, however, *does* require IESG approval.


  *   I think you're confused here, Rich.  This error code relates to *account keys*, not keys that are certified by the CA.

Not really, which is why I chose the example I did.