From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH] acme: add missing include for Crypt::OpenSSL::Random
Date: Thu, 9 Apr 2026 13:10:11 +0200 [thread overview]
Message-ID: <20260409111219.75078-1-f.ebner@proxmox.com> (raw)
While this seems to not happen or be rare in practice, the
import_random_seed() function from Crypt::OpenSSL::RSA might call into
Crypt::OpenSSL::Random::random_bytes() if the random number generator
is not already seeded enough.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
src/PVE/ACME.pm | 1 +
1 file changed, 1 insertion(+)
diff --git a/src/PVE/ACME.pm b/src/PVE/ACME.pm
index f1e9bb7..e6fb9c2 100644
--- a/src/PVE/ACME.pm
+++ b/src/PVE/ACME.pm
@@ -15,6 +15,7 @@ use Digest::SHA qw(sha256 sha256_hex hmac_sha256);
use HTTP::Request;
use LWP::UserAgent;
+use Crypt::OpenSSL::Random;
use Crypt::OpenSSL::RSA;
use PVE::Certificate;
--
2.47.3
reply other threads:[~2026-04-09 11:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20260409111219.75078-1-f.ebner@proxmox.com \
--to=f.ebner@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox