In a nutshell, pam_timestamp caches successful authentication
attempts, and allows you to use a recent successful attempt as
the basis for authentication. This is similar mechanism which is
used in sudo.
When an application opens a session using pam_timestamp, a
timestamp file is created in the timestampdir directory for the
user. When an application attempts to authenticate the user, a
pam_timestamp will treat a sufficiently recent timestamp file as
grounds for succeeding.
Specify an alternate directory where pam_timestamp creates
How long should pam_timestamp treat timestamp as valid after
their last modification date (in seconds). Default is 300
Attempt to inform the user when access is granted.
Turns on debugging messages sent to syslog(3).
The module was not able to retrieve the user name or no valid
timestamp file was found.
Everything was successful.
Timestamp file could not be created or updated.
This page is part of the linux-pam (Pluggable Authentication
Modules for Linux) project. Information about the project can be
found at ⟨http://www.linux-pam.org/⟩. If you have a bug report
for this manual page, see ⟨//www.linux-pam.org/⟩. This page was
obtained from the tarball Linux-PAM-1.3.0.tar.bz2 fetched from
⟨http://www.linux-pam.org/library/⟩ on 2020-12-18. If you
discover any rendering problems in this HTML version of the page,
or you believe there is a better or more up-to-date source for
the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original
manual page), send a mail to firstname.lastname@example.org
Linux-PAM Manual 04/01/2016 PAM_TIMESTAMP(8)