From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [45.144.208.40]) by lore.proxmox.com (Postfix) with ESMTPS id E1AC01FF0B6 for ; Thu, 12 Nov 2026 11:56:46 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 09EA42164B; Thu, 12 Nov 2026 11:56:44 +0100 (CET) From: Maximiliano Sandoval To: Kefu Chai Subject: Re: [PATCH ceph squid-stable-9 v3 0/1] patches: link the PVE cephx migration docs in the insecure key warnings In-Reply-To: <20261112082059.654926-1-k.chai@proxmox.com> (Kefu Chai's message of "Thu, 12 Nov 2026 16:20:58 +0800") References: <20261112082059.654926-1-k.chai@proxmox.com> User-Agent: mu4e 1.12.9; emacs 30.1 Date: Thu, 12 Nov 2026 11:56:38 +0100 Message-ID: MIME-Version: 1.0 Content-Type: text/plain X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794480999019 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.720 Adjusted score from AWL reputation of From: address DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment (newer systems) RCVD_IN_DNSWL_MED -2.3 Sender listed at https://www.dnswl.org/, medium trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Message-ID-Hash: OVTZ4S5UMFVBVFZOMUNQV4DD4L2YRDC7 X-Message-ID-Hash: OVTZ4S5UMFVBVFZOMUNQV4DD4L2YRDC7 X-MailFrom: m.sandoval@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 CC: pve-devel@lists.proxmox.com X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Kefu Chai writes: > The point releases added health checks for keys, service tickets and > cipher settings that still use aes, and a PVE user picking up the > release sees AUTH_INSECURE_KEYS_ALLOWED in `ceph health` with no hint > what to do about it. Append the PVE cephx migration guide's URL to > that check's summary, so the output itself points at the documented > migration path. > > The sibling patch for tentacle-stable-9 is resent separately. > > Both patches were tested in a lab environment, on three-node clusters > running packages built from these branches at 19.2.7-pve1 and > 20.2.5-pve1: the URL shows up in `ceph health`, `ceph -s`, `ceph > health detail` and the cluster log while the monitors still allow > aes, and it disappears once the allowed ciphers are restricted to > aes256k. > > Changes since v2: > > * rebase onto the Squid 19.2.7 import. The quilt patch itself is > unchanged. > > Link to v2: https://lore.proxmox.com/pve-devel/20261016103138.3896717-1-k.chai@proxmox.com/ > > Kefu Chai (1): > patches: link the PVE cephx migration docs in the insecure key warnings > > patches/0058-mon-AuthMonitor-link-the-PVE-cephx-migration-docs-in.patch | 53 +++++++++++++++++++ > patches/series | 1 + > 2 files changed, 54 insertions(+) Tested creating a cluster with ceph 19.2.3-pve4 with a single VM using a rbd storage. Upgraded the cluster to 19.2.7 with this patch applied and carried the cephx key migration. It all worked as expected. After restarting the first monitor after the upgrade, ceph -s displayed as expected: Monitors are configured to allow auth using insecure key types, see https://pve.proxmox.com/pve-docs/chapter-pveceph.html#pveceph_cephx_migration Tested-by: Maximiliano Sandoval Reviewed-by: Maximiliano Sandoval -- Maximiliano