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 0A06E1FF0C0 for ; Wed, 18 Nov 2026 05:24:01 +0100 (CET) Received: from gate001.proxmox.com (localhost.localdomain [127.0.0.1]) by gate001.proxmox.com (Proxmox) with ESMTP id 1FDB02163D; Wed, 18 Nov 2026 05:23:59 +0100 (CET) From: Kefu Chai To: m.sandoval@proxmox.com Subject: Re: [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 12:23:50 +0800 Message-ID: <20261118042350.3856610-1-k.chai@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: References: <20261112082059.654926-1-k.chai@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1794975835155 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.201 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: CHUTDE2MKE65B6RZ4KYTAQCIAMVLKCRQ X-Message-ID-Hash: CHUTDE2MKE65B6RZ4KYTAQCIAMVLKCRQ X-MailFrom: k.chai@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: Hi Maximiliano, thanks a lot for testing this, and for going through the whole upgrade with the key migration on top, that's the part I was least sure about! Nice to see the URL show up right after the first monitor restart too, since that's when people run into the warning.