From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Shannon Sterz <s.sterz@proxmox.com>,
Mark Atwood <mark@wolfssl.com>,
pve-devel@lists.proxmox.com
Subject: Re: [PATCH cluster v2 1/1] datacenter config: add ticket-signature-hash option
Date: Thu, 19 Nov 2026 13:38:55 +0100 [thread overview]
Message-ID: <ff30aa76-4ccc-4550-8e9e-4af36c44062d@proxmox.com> (raw)
In-Reply-To: <DMY8KD0ZGUMK.QED7IOIXLGPK@proxmox.com>
Thanks for your input, more than appreciated.
Am 18.11.26 um 10:40 schrieb Shannon Sterz:
> Using the cluster version guard helper [2] would come with one downside:
> It als errors when not all nodes are online or the version information
> is unreadable. In that case we'd probably want to fall back to SHA-1,
> which for FIPS compliant nodes would mean that they can't log in if a
> single node goes down. While logging in with TFA is already an issue in
> an unquorate state, this would arguably be worse for FIPS users.
I mean, FIPS compliance might require quorum to allow login in the
first place? as only with quorum you can ensure that the user config
and its access control lists etc. are up-to-date and the user is allowed
to login. We argued convenience-over-security for the common case, but
for security compliance the latter often should be weighted higher I
think. So this might be actually a feature for FIPS?
But in any case rather orthogonal to this here.
> So we'd need to keep using SHA-256 at least until a new node joins with
> a version that's too old. We could do that with a non-dying variant of
> the helper that reads the stale info from pmxcfs as usually version
> numbers only go up. However, nodes with an unknown version would remain
> an issue. Alternatively we may want to add a fallback to SHA-256 if
> signing with SHA-1 fails or allow an override similar to this approach.
>
> The nice thing about this option is that it only depends on the state of
> the local node. Even in an unquorate state the cluster config stays
> readable as pmxcfs switches to read-only mode.
hmm, using an option like this certainly makes it a bit simpler to
reason about when to do what, so can be fine by me. We can switch the
default here then e.g. in PVE 10 (we require all nodes to be on latest
9.x before upgrade anyway) or if we're more cautious then 11. And there
might be other algos in the future, so OK to have this config as
infrastructure for that.
> [1]: https://lore.proxmox.com/all/DMKS80347XID.3KPXPXVUHQ3ZG@proxmox.com/
> [2]: https://git.proxmox.com/?p=pve-cluster.git;a=commitdiff;h=168ac114df
next prev parent reply other threads:[~2026-11-19 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-13 3:06 [PATCH cluster v2 0/1] datacenter config: add ticket-signature-hash option Mark Atwood
2026-11-13 3:06 ` [PATCH cluster v2 1/1] " Mark Atwood
2026-11-17 16:05 ` Shannon Sterz
2026-11-18 4:14 ` Thomas Lamprecht
2026-11-18 9:40 ` Shannon Sterz
2026-11-19 12:38 ` Thomas Lamprecht [this message]
2026-11-19 13:37 ` Shannon Sterz
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=ff30aa76-4ccc-4550-8e9e-4af36c44062d@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=mark@wolfssl.com \
--cc=pve-devel@lists.proxmox.com \
--cc=s.sterz@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