From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) by lore.proxmox.com (Postfix) with ESMTPS id 5D32B1FF137 for ; Tue, 17 Mar 2026 15:22:06 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BDD28FDB5; Tue, 17 Mar 2026 15:22:13 +0100 (CET) From: Arthur Bied-Charreton To: pve-devel@lists.proxmox.com Subject: [PATCH pve-cluster v3 1/3] fix #6701: Add keyUsage extension to root CA Date: Tue, 17 Mar 2026 15:20:35 +0100 Message-ID: <20260317142206.482976-2-a.bied-charreton@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260317142206.482976-1-a.bied-charreton@proxmox.com> References: <20260317142206.482976-1-a.bied-charreton@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-SPAM-LEVEL: Spam detection results: 0 AWL -1.143 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment KAM_LAZY_DOMAIN_SECURITY 1 Sending domain does not have any anti-forgery methods RCVD_IN_VALIDITY_CERTIFIED_BLOCKED 0.408 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_RPBL_BLOCKED 0.819 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RCVD_IN_VALIDITY_SAFE_BLOCKED 0.903 ADMINISTRATOR NOTICE: The query to Validity was blocked. See https://knowledge.validity.com/hc/en-us/articles/20961730681243 for more information. RDNS_NONE 0.793 Delivered to internal network by a host with no rDNS SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_NONE 0.001 SPF: sender does not publish an SPF Record Message-ID-Hash: 4RXXC3RGERUXEV3TYVQWA7EKS7C5HIB6 X-Message-ID-Hash: 4RXXC3RGERUXEV3TYVQWA7EKS7C5HIB6 X-MailFrom: abied-charreton@jett.proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Add the keyUsage[1] extension to the PVE root CA to comply with RFC 5280, which Python decided to enforce as of 3.13 by adding the VERIFY_X509_STRICT flag, which breaks some clients like Ansible. The authorityKeyIdentifier[2] and subjectKeyIdentifier[3] extensions are required by RFC 5280 as well, however OpenSSL adds them in by default based on /etc/ssl/openssl.cnf, so there is no need for explicitly passing them. Test script: ``` import socket, ssl ctx = ssl.create_default_context(cafile="/etc/pve/pve-root-ca.pem") ctx.wrap_socket(socket.create_connection(("localhost", 8006)), server_hostname="localhost") print("success") ``` [1] https://www.rfc-editor.org/rfc/rfc5280#section-4.2.1.3 [2] https://www.rfc-editor.org/rfc/rfc5280#section-4.2.1.1 [3] https://www.rfc-editor.org/rfc/rfc5280#section-4.2.1.2 Signed-off-by: Arthur Bied-Charreton --- src/PVE/Cluster/Setup.pm | 2 ++ 1 file changed, 2 insertions(+) diff --git a/src/PVE/Cluster/Setup.pm b/src/PVE/Cluster/Setup.pm index 75d3507..4f528ba 100644 --- a/src/PVE/Cluster/Setup.pm +++ b/src/PVE/Cluster/Setup.pm @@ -439,6 +439,8 @@ sub gen_pveca_cert { '-new', '-x509', '-nodes', + '-addext', + 'keyUsage=critical,keyCertSign,cRLSign', '-key', $pveca_key_fn, '-out', -- 2.47.3