From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id DBE9E1FF09F for ; Thu, 03 Sep 2026 01:21:21 +0200 (CEST) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id AE5E321597; Thu, 03 Sep 2026 01:21:21 +0200 (CEST) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Thomas Ellmenreich Subject: applied: [PATCH proxmox-acme v3 1/1] fix #7749: always serialize in same order Date: Thu, 3 Sep 2026 01:21:11 +0200 Message-ID: <178839126712.1135632.9500063983608101469.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260812115128.135004-1-t.ellmenreich@proxmox.com> References: <20260812115128.135004-1-t.ellmenreich@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1788391275376 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.897 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_MED -2.3 Sender listed at https://www.dnswl.org/, medium 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: TMEBZOKHIHWGHQJ7FFGPT3AEWGJ3HTKA X-Message-ID-Hash: TMEBZOKHIHWGHQJ7FFGPT3AEWGJ3HTKA X-MailFrom: t.lamprecht@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: On Wed, 12 Aug 2026 13:51:28 +0200, Thomas Ellmenreich wrote: > All objects are now serialized with "canonical => 1" so that the > resulting bytes are directly comparable. Perls randomized hash key > orders lead to different serialization outputs even with the same input. > > The 'tojs' function also now explicitly overrides the utf8 and canonical > options to make sure that they are always set. > > [...] Applied, thanks! [1/1] fix #7749: always serialize in same order commit: 579d78f9fdd15277f5df0870ddc0bc5e391dd221