From: "Thomas Ellmenreich" <t.ellmenreich@proxmox.com>
To: "Thomas Ellmenreich" <t.ellmenreich@proxmox.com>,
<pve-devel@lists.proxmox.com>
Subject: Re: [PATCH common v4 2/3] pem parser: add testsuite for check_pem and split_pem
Date: Wed, 05 Aug 2026 16:23:36 +0200 [thread overview]
Message-ID: <DKH2TT7NFKLD.48CE46VVM6N6@proxmox.com> (raw)
In-Reply-To: <20260805141114.190477-4-t.ellmenreich@proxmox.com>
Please ignore this one, its a duplicate of the other [PATCH common v4 2/3]:
https://lore.proxmox.com/pve-devel/20260805141114.190477-3-t.ellmenreich@proxmox.com/
On Wed Aug 5, 2026 at 4:11 PM CEST, Thomas Ellmenreich wrote:
> having made considerable changes to both check_pem and split_pem
> in the previous commit, this commit introduces tests for both methods.
>
> Signed-off-by: Thomas Ellmenreich <t.ellmenreich@proxmox.com>
> ---
> test/Makefile | 2 +
> test/check_pem_test.pl | 365 +++++++++++++++++++++++++++++++++++++++++
> test/split_pem_test.pl | 279 +++++++++++++++++++++++++++++++
> 3 files changed, 646 insertions(+)
> create mode 100755 test/check_pem_test.pl
> create mode 100755 test/split_pem_test.pl
>
> diff --git a/test/Makefile b/test/Makefile
> index 961a0da..e5a5f42 100644
next prev parent reply other threads:[~2026-08-05 14:23 UTC|newest]
Thread overview: 6+ 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-05 14:11 ` [PATCH common v4 2/3] pem parser: add testsuite for check_ and split_pem Thomas Ellmenreich
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 [this message]
2026-08-05 14:11 ` [PATCH proxmox-acme v4 3/3] fix #5978: pem parser: relax parsing of chain entries: Thomas Ellmenreich
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=DKH2TT7NFKLD.48CE46VVM6N6@proxmox.com \
--to=t.ellmenreich@proxmox.com \
--cc=pve-devel@lists.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.