From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 8168D1FF13A for ; Wed, 22 Jul 2026 17:39:50 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id A1C4A21487; Wed, 22 Jul 2026 17:39:49 +0200 (CEST) Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=UTF-8 Date: Wed, 22 Jul 2026 17:39:45 +0200 Message-Id: From: "Elias Huhsovitz" To: "Thomas Ellmenreich" , Subject: Re: [PATCH proxmox-acme 1/1] fix #7749: always serialize in same order X-Mailer: aerc 0.20.0 References: <20260714090458.87511-1-t.ellmenreich@proxmox.com> <20260714090458.87511-2-t.ellmenreich@proxmox.com> In-Reply-To: <20260714090458.87511-2-t.ellmenreich@proxmox.com> X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1784734756999 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.167 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_LOW -0.7 Sender listed at https://www.dnswl.org/, low trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: JSQKOU6PO3YLCGPTM2YB3XGHZ6KRBVPH X-Message-ID-Hash: JSQKOU6PO3YLCGPTM2YB3XGHZ6KRBVPH X-MailFrom: e.huhsovitz@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Small nit below, otherwise Reviewed-by: Elias Huhsovitz On Tue Jul 14, 2026 at 11:04 AM CEST, Thomas Ellmenreich wrote: > All objects are now serialized with "canonical =3D> 1" so that the > resulting bytes are directly comparable. Perls randomized hash key > orders lead to different serialization outputs even with the same input. > > Signed-off-by: Thomas Ellmenreich > --- > src/PVE/ACME.pm | 8 ++++---- > 1 file changed, 4 insertions(+), 4 deletions(-) > > diff --git a/src/PVE/ACME.pm b/src/PVE/ACME.pm > index e6fb9c2..a5287ac 100644 > --- a/src/PVE/ACME.pm > +++ b/src/PVE/ACME.pm > @@ -64,9 +64,9 @@ sub encode($) { # acme requires 'base64url' encoding > return encode_base64url($_[0]); > } > =20 > -sub tojs($;%) { # shortcut for to_json with utf8=3D>1 > +sub tojs($;%) { # shortcut for to_json with utf8=3D>1 and canonical=3D>1 > my ($data, %data) =3D @_; > - return to_json($data, { utf8 =3D> 1, %data }); > + return to_json($data, { utf8 =3D> 1, canonical =3D> 1, %data }); > } nit: change the ordering to: return to_json($data, { %data, utf8 =3D> 1, canonical =3D> 1 }); To guarantee utf8=3D1, canonical=3D1. Theoretically %data could contain the keys (utf8=3D0, canonical=3D0) overriding your manually set values, due to perls hash expansion. Re-ordering should guarantee consistency. > =20 > sub fromjs($) { > @@ -155,7 +155,7 @@ sub save { > } > # pretty =3D> 1 for readability > # canonical =3D> 1 to reduce churn > - file_set_contents($self->{path}, tojs($o, pretty =3D> 1, canonical = =3D> 1)); > + file_set_contents($self->{path}, tojs($o, pretty =3D> 1)); > } > =20 > # Load serialized account JSON file into $self > @@ -196,7 +196,7 @@ sub jwk { > sub jwk_thumbprint { > my ($self) =3D @_; > my $jwk =3D $self->jwk(1); # $pure =3D 1 > - return encode(sha256(tojs($jwk, canonical =3D> 1))); # canonical sor= ts > + return encode(sha256(tojs($jwk))); > } > =20 > # A key authorization string in acme is a challenge token dot-connected = with