From: Lennart Poettering <lennart@poettering.net>
Date: Mon, 11 Jul 2022 13:12:24 +0000 (+0200)
Subject: man: explain why pam_systemd_home wants to be in all four stacks
X-Git-Tag: v252-rc1~681
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=90bc309aa2c1430941f4c50f73e681ab3e488bd3;p=thirdparty%2Fsystemd.git

man: explain why pam_systemd_home wants to be in all four stacks

Suggested here:

https://bugzilla.redhat.com/show_bug.cgi?id=2085485#c5
---

diff --git a/man/pam_systemd_home.xml b/man/pam_systemd_home.xml
index 906d1c15169..93153b57aa0 100644
--- a/man/pam_systemd_home.xml
+++ b/man/pam_systemd_home.xml
@@ -93,8 +93,13 @@
   <refsect1>
     <title>Module Types Provided</title>
 
-    <para>The module provides all four management operations: <option>auth</option>, <option>account</option>,
-    <option>session</option>, <option>password</option>.</para>
+    <para>The module implements all four PAM operations: <option>auth</option> (reason: when per-user
+    disk encryption is used, the disk encryption key is derived from the authentication credential supplied
+    at login time), <option>account</option> (reason: <filename>systemd-homed.service</filename> account
+    validity may be configured in more detail than in the traditional Linux user database, and thus needs to
+    be verified separately), <option>session</option> (user sessions must be tracked, in order to implement
+    automatic release when the last session of a managed user is gone), <option>password</option> (user
+    passwords may be changed through PAM).</para>
   </refsect1>
 
   <refsect1>