public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Fabian Grünbichler" <f.gruenbichler@proxmox.com>
To: pve-devel@lists.proxmox.com,
	Thomas Ellmenreich <t.ellmenreich@proxmox.com>
Subject: applied-series: [PATCH common/proxmox-acme v4 0/3] fix #5978: pem parser: relax parsing of chain entries
Date: Thu, 05 Nov 2026 14:32:00 +0100	[thread overview]
Message-ID: <1793885504.bskbk5fxyp.astroid@yuna.none> (raw)
In-Reply-To: <20260805141114.190477-1-t.ellmenreich@proxmox.com>

with a tiny test follow-up in common

On August 5, 2026 4:11 pm, Thomas Ellmenreich wrote:
> According to RFC 8555, expected certchains should come
> without whitespace or explanatory texts inbetween chain
> entries. These two patches relax our parser to also
> accept text or whitespaces inbetween chain entries.
> 
> To make sure that the acme changes work as expected I
> setup the pebble acme server [1] locally, and worked
> through the acme flow to get a new certificate. I then
> manually modified the final certificate to contain
> descriptive text which worked without issues.
> 
> changes since v3:
> - check_pem was reworked to not be recursive
> 
> - the check_pem tests now also check the erroring version to
>   make sure that an exception is thrown
> 
> - moved the tests to their own commit
> 
> - wrapped the error message produced by check_pem when
>   called in proxmox-acme with chomp to avoid double newlines
> 
> - corrected the capitalization of different acronyms
> 
> changes since v2:
> - cleaner implementation and correction of mistakes in
>   check_pem in pve-common
> 
> - get_certificate in proxmox-acme now correctly calls
>   check_pem with the 'multiple' option enabled
> 
> - removed ambiguity in the error messages of
>   get_certificate
> 
> - correction of tests, to better compare returned value
>   to expected value
> 
> - performed proper end-to-end test with pebble [1]
> 
> - proper formatting (hopefully)
> 
> changes since v1:
> - Where in v1 check_pem was just a wrapper of split_pem,
>   they now perform different functions
> 
> - split_pem now purely splits the PEM chain into separate
>   entries and does no further validation. Returning each
>   entry with its leading text.
> 
> - check_pem retains the original functionality, except
>   when the multiple option is active, in which case it
>   uses split_pem to get single entries and then calls
>   itself recursively
> 
> - On the ACME side, errors are now captured, wrapped,
>   and then rethrown.
> 
> [1] https://github.com/letsencrypt/pebble
> 
> 
> pve-common:
> 
> Thomas Ellmenreich (2):
>   fix #5978: pem parser: relax parsing of chain entries
>   pem parser: add testsuite for check_ and split_pem
> 
>  src/PVE/Certificate.pm |  39 ++++-
>  test/Makefile          |   2 +
>  test/check_pem_test.pl | 365 +++++++++++++++++++++++++++++++++++++++++
>  test/split_pem_test.pl | 279 +++++++++++++++++++++++++++++++
>  4 files changed, 677 insertions(+), 8 deletions(-)
>  create mode 100755 test/check_pem_test.pl
>  create mode 100755 test/split_pem_test.pl
> 
> 
> proxmox-acme:
> 
> Thomas Ellmenreich (1):
>   fix #5978: pem parser: relax parsing of chain entries:
> 
>  src/PVE/ACME.pm | 12 +++++++-----
>  1 file changed, 7 insertions(+), 5 deletions(-)
> 
> 
> Summary over all repositories:
>   5 files changed, 684 insertions(+), 13 deletions(-)
> 
> -- 
> Generated by murpp 0.12.0
> 
> 
> 
> 
> 




      parent reply	other threads:[~2026-11-05 13:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 14:11 [PATCH common/proxmox-acme v4 0/3] fix #5978: pem parser: relax parsing of chain entries Thomas Ellmenreich
2026-08-05 14:11 ` [PATCH common v4 1/3] " Thomas Ellmenreich
2026-08-14 14:26   ` Elias Huhsovitz
2026-08-05 14:11 ` [PATCH common v4 2/3] pem parser: add testsuite for check_ and split_pem Thomas Ellmenreich
2026-08-14 14:30   ` Elias Huhsovitz
2026-08-05 14:11 ` [PATCH common v4 2/3] pem parser: add testsuite for check_pem " Thomas Ellmenreich
2026-08-05 14:23   ` Thomas Ellmenreich
2026-08-05 14:11 ` [PATCH proxmox-acme v4 3/3] fix #5978: pem parser: relax parsing of chain entries: Thomas Ellmenreich
2026-08-14 14:32   ` Elias Huhsovitz
2026-09-23 12:18 ` [PATCH common/proxmox-acme v4 0/3] fix #5978: pem parser: relax parsing of chain entries Thomas Ellmenreich
2026-11-05 13:32 ` Fabian Grünbichler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1793885504.bskbk5fxyp.astroid@yuna.none \
    --to=f.gruenbichler@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=t.ellmenreich@proxmox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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