From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH docs 5/5] user management: clarify that password changes for PAM realm only apply to local node
Date: Wed, 4 Dec 2024 12:37:08 +0100 [thread overview]
Message-ID: <20241204113708.50043-6-f.ebner@proxmox.com> (raw)
In-Reply-To: <20241204113708.50043-1-f.ebner@proxmox.com>
Reported in the community forum:
https://forum.proxmox.com/threads/158518/
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
pveum.adoc | 10 ++++++++--
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/pveum.adoc b/pveum.adoc
index 81565ab..b8303e8 100644
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -170,8 +170,14 @@ Linux PAM Standard Authentication
As Linux PAM corresponds to host system users, a system user must exist on each
node which the user is allowed to log in on. The user authenticates with their
-usual system password. This realm is added by default and can't be removed. In
-terms of configurability, an administrator can choose to require two-factor
+usual system password. This realm is added by default and can't be removed.
+
+Password changes via the GUI or, equivalently, the `/access/password` API
+endpoint only apply to the local node and not cluster-wide. Even though {pve}
+has a multi-master design, using different passwords for different nodes can
+still offer a security benefit.
+
+In terms of configurability, an administrator can choose to require two-factor
authentication with logins from the realm and to set the realm as the default
authentication realm.
--
2.39.5
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2024-12-04 11:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-04 11:37 [pve-devel] [PATCH widget-toolkit/manager/access-control/docs 0/5] " Fiona Ebner
2024-12-04 11:37 ` [pve-devel] [PATCH widget-toolkit 1/5] password edit: support specifying a hint Fiona Ebner
2025-04-06 17:57 ` [pve-devel] applied: " Thomas Lamprecht
2024-12-04 11:37 ` [pve-devel] [PATCH manager 2/5] user: password edit: clarify that password changes for PAM realm only apply to local node Fiona Ebner
2025-04-06 18:01 ` Thomas Lamprecht
2025-04-07 8:18 ` [pve-devel] superseded: " Fiona Ebner
2024-12-04 11:37 ` [pve-devel] [PATCH access-control 3/5] api: " Fiona Ebner
2025-04-04 17:21 ` [pve-devel] applied: " Thomas Lamprecht
2024-12-04 11:37 ` [pve-devel] [PATCH access-control 4/5] api: password: use singular they pronoun Fiona Ebner
2025-04-04 17:21 ` [pve-devel] applied: " Thomas Lamprecht
2024-12-04 11:37 ` Fiona Ebner [this message]
2025-04-06 17:56 ` [pve-devel] applied: [PATCH docs 5/5] user management: clarify that password changes for PAM realm only apply to local node 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=20241204113708.50043-6-f.ebner@proxmox.com \
--to=f.ebner@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal