mirror of
https://github.com/systemd/systemd-stable.git
synced 2024-10-26 08:55:18 +03:00
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
(cherry picked from commit 90bc309aa2
)
This commit is contained in:
parent
8a6f966be4
commit
69de3e810a
@ -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>
|
||||
|
Loading…
Reference in New Issue
Block a user