From 206ea90725a4325ba19ce143374063985ea27827 Mon Sep 17 00:00:00 2001
From: upstream <upstream@localhost>
Date: Sat, 3 Oct 2026 03:22:04 +0200
Subject: [PATCH] Upstream proxmox-git/pve-docs state of the touched files
 before 31adf6ab65

---
 pveum.adoc | 8 --------
 1 file changed, 8 deletions(-)

diff --git a/pveum.adoc b/pveum.adoc
index 49cfd68..d089cb6 100644
--- a/pveum.adoc
+++ b/pveum.adoc
@@ -184,14 +184,6 @@ 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.
 
-{pve} uses the PAM service name `proxmox-ve-auth` to authenticate users of this
-realm. This allows changing the PAM configuration only for logins to {pve},
-without affecting other services like the login on the console or via SSH, by
-creating the file `/etc/pam.d/proxmox-ve-auth`. If this file does not exist,
-PAM uses the configuration of the `other` service, so a copy of
-`/etc/pam.d/other` is a good starting point. Like the system users, this
-configuration is local to each node.
-
 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.