From: Kefu Chai <k.chai@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH ceph tentacle-stable-9 v3 0/1] patches: link the PVE cephx migration docs in the insecure key warnings
Date: Thu, 12 Nov 2026 16:20:31 +0800 [thread overview]
Message-ID: <20261112082032.649650-1-k.chai@proxmox.com> (raw)
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 squid-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 Tentacle 20.2.5 import. The quilt patch moves from
0019 to 0020, because 0019 is now taken by the EC scrub backport;
the change itself is untouched.
Link to v2: https://lore.proxmox.com/pve-devel/20261016103128.3895688-1-k.chai@proxmox.com/
Kefu Chai (1):
patches: link the PVE cephx migration docs in the insecure key warnings
patches/0020-mon-AuthMonitor-link-the-PVE-cephx-migration-docs-in.patch | 53 +++++++++++++++++++
patches/series | 1 +
2 files changed, 54 insertions(+)
--
2.47.3
next reply other threads:[~2026-11-12 8:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 8:20 Kefu Chai [this message]
2026-11-12 8:20 ` [PATCH ceph tentacle-stable-9 v3 1/1] patches: link the PVE cephx migration docs in the insecure key warnings Kefu Chai
2026-11-19 9:10 ` applied: [PATCH ceph tentacle-stable-9 v3 0/1] " 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=20261112082032.649650-1-k.chai@proxmox.com \
--to=k.chai@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.