From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Kefu Chai <k.chai@proxmox.com>
Subject: applied: [PATCH ceph tentacle-stable-9 v3 0/1] patches: link the PVE cephx migration docs in the insecure key warnings
Date: Thu, 19 Nov 2026 10:10:46 +0100 [thread overview]
Message-ID: <179507944343.1316126.11281791599891820225.b4-ty@b4> (raw)
In-Reply-To: <20261112082032.649650-1-k.chai@proxmox.com>
On Thu, 12 Nov 2026 16:20:31 +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, but not bumped yet (anything else that should go in such a
bump?), thanks!
[1/1] patches: link the PVE cephx migration docs in the insecure key warnings
commit: 73d6ab1eec52519e63a0843427df44c49b8b97bd
prev parent reply other threads:[~2026-11-19 9:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 8:20 [PATCH ceph tentacle-stable-9 v3 0/1] patches: link the PVE cephx migration docs in the insecure key warnings Kefu Chai
2026-11-12 8:20 ` [PATCH ceph tentacle-stable-9 v3 1/1] " Kefu Chai
2026-11-19 9:10 ` Thomas Lamprecht [this message]
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=179507944343.1316126.11281791599891820225.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=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.