public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
* [PATCH proxmox-acme 0/1] fix #7749: always serialize in same order
@ 2026-07-14  9:04 Thomas Ellmenreich
  2026-07-14  9:04 ` [PATCH proxmox-acme 1/1] " Thomas Ellmenreich
  0 siblings, 1 reply; 2+ messages in thread
From: Thomas Ellmenreich @ 2026-07-14  9:04 UTC (permalink / raw)
  To: pve-devel; +Cc: Thomas Ellmenreich

Serializing acme responses to json, because of perls randomized hash key order,
would lead to unequal serialized responses if they were compared as bytes. By
setting "canonical => 1" the serializations now always have the same order and
can thus be compared bytewise.

I have tested the patch against a local instance of HashiCorp Vault PKI and the
EAB registration works.

It seems that "canonical" can have performance implications when serialising
larger objects, but since the objects produced in our acme client are
relatively small, I consider this acceptable.


proxmox-acme:

Thomas Ellmenreich (1):
  fix #7749: always serialize in same order

 src/PVE/ACME.pm | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)


Summary over all repositories:
  1 files changed, 4 insertions(+), 4 deletions(-)

-- 
Generated by murpp 0.12.0




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2026-07-14  9:05 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-07-14  9:04 [PATCH proxmox-acme 0/1] fix #7749: always serialize in same order Thomas Ellmenreich
2026-07-14  9:04 ` [PATCH proxmox-acme 1/1] " Thomas Ellmenreich

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal