IETF Logo Mail Archive

[Acme] Re: Update: draft-geng-acme-public-key-05

Ilari Liusvaara <ilariliusvaara@welho.com> Fri, 24 April 2026 17:17 UTC

Return-Path: <ilariliusvaara@welho.com>
X-Original-To: acme@mail2.ietf.org
Delivered-To: acme@mail2.ietf.org
Received: from localhost (localhost [127.0.0.1]) by mail2.ietf.org (Postfix) with ESMTP id B7430E287337 for <acme@mail2.ietf.org>; Fri, 24 Apr 2026 10:17:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ietf.org; s=ietf1; t=1777051033; bh=zzJBQEmgRisLdDv/MAOlJ3+QCZnvoNZJdMHNd9l1B04=; h=Date:From:To:Subject:References:In-Reply-To; b=KimwbCUu0HVZgD4zeKyLbZstw74/Mu3A2/V2Rq0/JwZmYi/QBJqZq5EdgKrIL80AY 1+g11G6AJMr+wcD/gklC9xYCY7YWR0Dk3i14VI1HTtb1ljKlGRmiAREfsCjsWXD7p7 HqNsLe2kigjlw0I9hNGQ+79hkrloVR7V7bmcGHzg=
X-Virus-Scanned: amavisd-new at ietf.org
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: mail2.ietf.org (amavisd-new); dkim=pass (2048-bit key) header.d=welho.com
Received: from mail2.ietf.org ([166.84.6.31]) by localhost (mail2.ietf.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8PxGzMyfySgn for <acme@mail2.ietf.org>; Fri, 24 Apr 2026 10:17:13 -0700 (PDT)
Received: from smtp.dnamail.fi (sender001.dnamail.fi [83.102.40.178]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-256) server-digest SHA256) (No client certificate requested) by mail2.ietf.org (Postfix) with ESMTPS id B2F38E28723F for <acme@ietf.org>; Fri, 24 Apr 2026 10:16:11 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by smtp.dnamail.fi (Postfix) with ESMTP id 817642113E0F for <acme@ietf.org>; Fri, 24 Apr 2026 20:16:10 +0300 (EEST)
X-Virus-Scanned: X-Virus-Scanned: amavis at smtp.dnamail.fi
Received: from smtp.dnamail.fi ([83.102.40.178]) by localhost (dmail-psmtp01.s.dnaip.fi [127.0.0.1]) (amavis, port 10024) with ESMTP id IAmPhuiGKnOs for <acme@ietf.org>; Fri, 24 Apr 2026 20:16:10 +0300 (EEST)
Received: from LK-Perkele-VII2 (87-92-117-27.bb.dnainternet.fi [87.92.117.27]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) (Authenticated sender: hliusvaa@dnamail.internal) by smtp.dnamail.fi (Postfix) with ESMTPSA id 0060E2113E04 for <acme@ietf.org>; Fri, 24 Apr 2026 20:16:09 +0300 (EEST)
DKIM-Filter: OpenDKIM Filter v2.11.0 smtp.dnamail.fi 0060E2113E04
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=welho.com; s=2025-03; t=1777050970; bh=MiQp5LBqeUPeeK6DW/YmqG+KbgLaab83ciZRxM88G+M=; h=Date:From:To:Subject:References:In-Reply-To:From; b=j/F6VV6v/451AMdjkXc5MN43VT6v5nKcM857JkrKauWjbhGiFZoR48v0xhFLTsO6c hwlQgmuqpkD9r55m6f+8s55LEy+dP+UP6zHgOioCDsYMChz2dGkTy0WdVH8CuyqYUO /7xI8FjpDseh3Y1KvQEg8pRjDYke9Y+IxZ1dNufkP2i7+5+Cuo23w01OkQgoEggFnV R0dadBbUm8SoFYExX1FNLJJ7z5kdkSFlVxdXUQ7M/9eYIZIvBE8KoaT0dbmHoaOYL+ BSKYEVm853YYI7MZEN3x2w4KPudNhEtDsOclDNOIh906S+JVSOg757zvUYLL5hO2J/ 6YMLPcV/Tk/ZA==
Date: Fri, 24 Apr 2026 20:16:09 +0300
From: Ilari Liusvaara <ilariliusvaara@welho.com>
To: IETF ACME <acme@ietf.org>
Message-ID: <aeulWWqlUMVZVrPG@LK-Perkele-VII2.locald>
References: <CAB=Y13dw+m7Oc4JPi+dk77tNZ=xJf05WRefd2fjRdOvz_qJjyA@mail.gmail.com> <ac6pUlXmhEOFYmFB@LK-Perkele-VII2.locald> <CAB=Y13fioUaCzpWJ8OCs=_F3YH7V6h6M4-2X1rDFubnT4JX-gQ@mail.gmail.com> <adn3p_LBRjS8dOSv@LK-Perkele-VII2.locald> <8060EBF4-CC67-44B0-8221-42170B8F0C0A@trustasia.com> <CAKZgXHpvSY=Daz8gqw0D6=A_sHzW+7jtarDKz3Po7ppKz99ZMQ@mail.gmail.com> <aesT_YeilmiR13AW@LK-Perkele-VII2.locald> <tencent_281C0C2590D8B925587F8B172FA297876E08@qq.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <tencent_281C0C2590D8B925587F8B172FA297876E08@qq.com>
Sender: ilariliusvaara@welho.com
Message-ID-Hash: XES7KGO76EYPR3L2XV4ZNJ3Z5OBFC4OQ
X-Message-ID-Hash: XES7KGO76EYPR3L2XV4ZNJ3Z5OBFC4OQ
X-MailFrom: ilariliusvaara@welho.com
X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-acme.ietf.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header
X-Mailman-Version: 3.3.9rc6
Precedence: list
Subject: [Acme] Re: Update: draft-geng-acme-public-key-05
List-Id: Automated Certificate Management Environment <acme.ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/acme/2LqCq8WCy0YSDuQrJJjaSK36-_g>
List-Archive: <https://mailarchive.ietf.org/arch/browse/acme>
List-Help: <mailto:acme-request@ietf.org?subject=help>
List-Owner: <mailto:acme-owner@ietf.org>
List-Post: <mailto:acme@ietf.org>
List-Subscribe: <mailto:acme-join@ietf.org>
List-Unsubscribe: <mailto:acme-leave@ietf.org>

On Fri, Apr 24, 2026 at 04:25:43PM +0800, 皮皮猪 wrote:
> I second this opinion. :-)
> 
> 
> and just one more question:
> for KEM keys, why not directly reuse rfc8555 processes, the server
> encrypt the challenges token by pk, and the client decrypt first then
> compute the keyAuthorization.

- This would not authenticate the request.
- This would require client to do symmetric decryption.
- This would require client to know the key ID (however, client
  likely requires it for other authorizations anyway).




-Ilari

v2.46.0 | Report a Bug | By Email | System Status