From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Kefu Chai <k.chai@proxmox.com>, pve-devel@lists.proxmox.com
Subject: Re: [PATCH ceph squid-stable-8] patches: link the PVE 8 upgrade notes in the insecure key warning
Date: Thu, 19 Nov 2026 10:17:06 +0100 [thread overview]
Message-ID: <9ddfd3f5-9864-4316-bf23-0087ace46be2@proxmox.com> (raw)
In-Reply-To: <20261119060555.562383-1-k.chai@proxmox.com>
Am 19.11.26 um 07:06 schrieb Kefu Chai:
> Adapt the squid-stable-9 docs hint from d456e3571a0c for Bookworm.
> The 8-to-9 upgrade guide quotes AUTH_INSECURE_KEYS_ALLOWED and explains
> that these warnings alone do not block the upgrade. It links the key
> migration steps to use after every node has been upgraded.
>
> Signed-off-by: Kefu Chai <k.chai@proxmox.com>
> ---
> ...r-link-the-PVE-8-cephx-upgrade-notes.patch | 33 +++++++++++++++++++
> patches/series | 1 +
> 2 files changed, 34 insertions(+)
> create mode 100644 patches/0044-mon-AuthMonitor-link-the-PVE-8-cephx-upgrade-notes.patch
This is for an EOL release, doing a bump here sets a precedence that we
release still updates, which is IMO not ideal. I mean, I can see where
this comes from; but a simple help hint that can be figured out by anyone
doing a quick search or look at the docs seems IMO less pressing than the
thousands or so of rather relevant security issues we're releasing fixes
in a month for all over the place.
prev parent reply other threads:[~2026-11-19 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-19 6:05 [PATCH ceph squid-stable-8] patches: link the PVE 8 upgrade notes in the insecure key warning Kefu Chai
2026-11-19 9:17 ` 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=9ddfd3f5-9864-4316-bf23-0087ace46be2@proxmox.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox