From: "Michael Köppl" <m.koeppl@proxmox.com>
To: "Maximiliano Sandoval" <m.sandoval@proxmox.com>,
<pve-devel@lists.proxmox.com>
Subject: Re: [PATCH docs 2/2] cephx-migration: Add link to CVE-2025-30156
Date: Tue, 08 Sep 2026 13:47:42 +0200 [thread overview]
Message-ID: <DL9WSYPJQN0Q.60JZ9WS7J58X@proxmox.com> (raw)
In-Reply-To: <20260908113718.326913-3-m.sandoval@proxmox.com>
Reviewed-by: Michael Köppl <m.koeppl@proxmox.com>
On Tue Sep 8, 2026 at 1:37 PM CEST, Maximiliano Sandoval wrote:
> Signed-off-by: Maximiliano Sandoval <m.sandoval@proxmox.com>
> ---
> pveceph.adoc | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/pveceph.adoc b/pveceph.adoc
> index 9664289..625768f 100644
> --- a/pveceph.adoc
> +++ b/pveceph.adoc
> @@ -1341,7 +1341,8 @@ Why the Health Checks Appear
> Ceph Squid 19.2.6 and Ceph Tentacle 20.2.4 add health checks for keys and
> temporary access credentials that use the older `aes` encryption method. The
> checks can therefore appear directly after an upgrade even if the cluster
> -worked without warnings before. The older method is affected by CVE-2025-30156.
> +worked without warnings before. The older method is affected by
> +https://docs.ceph.com/en/latest/security/CVE-2025-30156['CVE-2025-30156'].
> See the upstream release announcement for background footnote:[Ceph: Squid
> v19.2.6 and Tentacle v20.2.4 released
> https://ceph.io/en/news/blog/2026/v20-2-4-v19-2-6-combo-released/].
next prev parent reply other threads:[~2026-09-08 11:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-08 11:37 [PATCH docs 0/2] cephx-migration: Replace consumer with client Maximiliano Sandoval
2026-09-08 11:37 ` [PATCH docs 1/2] " Maximiliano Sandoval
2026-09-08 11:47 ` Michael Köppl
2026-09-08 11:37 ` [PATCH docs 2/2] cephx-migration: Add link to CVE-2025-30156 Maximiliano Sandoval
2026-09-08 11:47 ` Michael Köppl [this message]
2026-09-08 15:45 ` superseded: [PATCH docs 0/2] cephx-migration: Replace consumer with client Maximiliano Sandoval
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=DL9WSYPJQN0Q.60JZ9WS7J58X@proxmox.com \
--to=m.koeppl@proxmox.com \
--cc=m.sandoval@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