/
usr
/
share
/
doc
/
pam
/
txts
/
/usr/share/doc/pam/txts
mkdir
upload
Name
Size
Mode
Actions
README.pam_access
5253
0644
edit
dl
rm
README.pam_chroot
1510
0644
edit
dl
rm
README.pam_console
1925
0644
edit
dl
rm
README.pam_cracklib
9757
0644
edit
dl
rm
README.pam_debug
1995
0644
edit
dl
rm
README.pam_deny
1035
0644
edit
dl
rm
README.pam_echo
1100
0644
edit
dl
rm
README.pam_env
3627
0644
edit
dl
rm
README.pam_exec
2230
0644
edit
dl
rm
README.pam_faildelay
827
0644
edit
dl
rm
README.pam_faillock
6062
0644
edit
dl
rm
README.pam_filter
3102
0644
edit
dl
rm
README.pam_ftp
1699
0644
edit
dl
rm
README.pam_group
2175
0644
edit
dl
rm
README.pam_issue
1356
0644
edit
dl
rm
README.pam_keyinit
2245
0644
edit
dl
rm
README.pam_lastlog
2597
0644
edit
dl
rm
README.pam_limits
2421
0644
edit
dl
rm
README.pam_listfile
3626
0644
edit
dl
rm
README.pam_localuser
1167
0644
edit
dl
rm
README.pam_loginuid
1117
0644
edit
dl
rm
README.pam_mail
2009
0644
edit
dl
rm
README.pam_mkhomedir
1361
0644
edit
dl
rm
README.pam_motd
2588
0644
edit
dl
rm
README.pam_namespace
11543
0644
edit
dl
rm
README.pam_nologin
1348
0644
edit
dl
rm
README.pam_permit
907
0644
edit
dl
rm
README.pam_postgresok
346
0644
edit
dl
rm
README.pam_pwhistory
2243
0644
edit
dl
rm
README.pam_rhosts
1882
0644
edit
dl
rm
README.pam_rootok
1086
0644
edit
dl
rm
README.pam_securetty
1342
0644
edit
dl
rm
README.pam_selinux
2909
0644
edit
dl
rm
README.pam_sepermit
1648
0644
edit
dl
rm
README.pam_shells
653
0644
edit
dl
rm
README.pam_stress
2060
0644
edit
dl
rm
README.pam_succeed_if
2864
0644
edit
dl
rm
README.pam_time
1301
0644
edit
dl
rm
README.pam_timestamp
1616
0644
edit
dl
rm
README.pam_tty_audit
2779
0644
edit
dl
rm
README.pam_umask
1631
0644
edit
dl
rm
README.pam_unix
7265
0644
edit
dl
rm
README.pam_userdb
2973
0644
edit
dl
rm
README.pam_usertype
1200
0644
edit
dl
rm
README.pam_warn
1224
0644
edit
dl
rm
README.pam_wheel
1968
0644
edit
dl
rm
README.pam_xauth
3695
0644
edit
dl
rm
Edit:
/usr/share/doc/pam/txts/README.pam_timestamp
(1616B)
pam_timestamp — Authenticate using cached successful authentication attempts ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ DESCRIPTION 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. OPTIONS timestampdir=directory Specify an alternate directory where pam_timestamp creates timestamp files. timestamp_timeout=number How long should pam_timestamp treat timestamp as valid after their last modification date (in seconds). Default is 300 seconds. verbose Attempt to inform the user when access is granted. debug Turns on debugging messages sent to syslog(3). NOTES Users can get confused when they are not always asked for passwords when running a given program. Some users reflexively begin typing information before noticing that it is not being asked for. EXAMPLES auth sufficient pam_timestamp.so verbose auth required pam_unix.so session required pam_unix.so session optional pam_timestamp.so AUTHOR pam_timestamp was written by Nalin Dahyabhai.
Save
cmd:
run