From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate001.proxmox.com (gate001.proxmox.com [IPv6:2a0f:8001:1:32::40]) by lore.proxmox.com (Postfix) with ESMTPS id 8185B1FF0C0 for ; Wed, 18 Nov 2026 15:51:15 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id A08E7217B4; Wed, 18 Nov 2026 15:51:13 +0100 (CET) From: Thomas Lamprecht To: pve-devel@lists.proxmox.com, Kefu Chai Subject: applied: [PATCH ceph squid-stable-9 v3 0/1] patches: link the PVE cephx migration docs in the insecure key warnings Date: Wed, 18 Nov 2026 15:51:01 +0100 Message-ID: <179501345770.1416143.18071907364279465400.b4-ty@b4> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20261112082059.654926-1-k.chai@proxmox.com> References: <20261112082059.654926-1-k.chai@proxmox.com> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1795013469575 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.170 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: X4ZTSJ5FEOAPR5EDT7R6CX27X7EHZ7GG X-Message-ID-Hash: X4ZTSJ5FEOAPR5EDT7R6CX27X7EHZ7GG X-MailFrom: t.lamprecht@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: On Thu, 12 Nov 2026 16:20:58 +0800, Kefu Chai wrote: > 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. > > [...] Applied, thanks! [1/1] patches: link the PVE cephx migration docs in the insecure key warnings commit: d456e3571a0c880133fd16828962a9288a18d75b