public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH manager master+stable-8] pve8to9: improve error/log message for tls checks
Date: Wed, 19 Nov 2025 10:25:59 +0100	[thread overview]
Message-ID: <20251119092634.763388-1-d.csapak@proxmox.com> (raw)

we check different key sizes for RSA (2048) vs ECC (224) but the
logs/error always wrote '2048' which can be confusing if ECC keys are
used, for example:

PASS: Certificate 'pveproxy-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (256 >= 2048)

Use the actual size and type we check against in the log/error so reduce
confusion.

The new log line is then:

PASS: Certificate 'pveproxy-ssl.pem' passed Debian Busters (and newer) security level for TLS connections (256 >= 224 ECC)

Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
---
this is based on master, but should be cleanly cherry-pickable on
stable-8 currently

 PVE/CLI/pve8to9.pm | 10 +++++++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/PVE/CLI/pve8to9.pm b/PVE/CLI/pve8to9.pm
index 5a22c229..0c4b2343 100644
--- a/PVE/CLI/pve8to9.pm
+++ b/PVE/CLI/pve8to9.pm
@@ -2257,12 +2257,16 @@ sub check_misc {
             next;
         }
 
-        if ($size < $check->{minsize}) {
-            log_fail("'$fn', certificate's $check->{name} public key size is less than 2048 bit");
+        my $min_size = $check->{minsize};
+        my $name = $check->{name};
+        if ($size < $min_size) {
+            log_fail(
+                "'$fn', certificate's $check->{name} public key size is less than $min_size bit for $name"
+            );
             $certs_check_failed = 1;
         } else {
             log_pass(
-                "Certificate '$fn' passed Debian Busters (and newer) security level for TLS connections ($size >= 2048)"
+                "Certificate '$fn' passed Debian Busters (and newer) security level for TLS connections ($size >= $min_size $name)"
             );
         }
     }
-- 
2.47.3



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


             reply	other threads:[~2025-11-19  9:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19  9:25 Dominik Csapak [this message]
2025-11-19  9:48 ` [pve-devel] applied: " Thomas Lamprecht

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=20251119092634.763388-1-d.csapak@proxmox.com \
    --to=d.csapak@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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal