1pam_timestamp(8) System Administrator's Manual pam_timestamp(8)
2
3
4
6 pam_timestamp - authenticate using cached successful authentication
7 attempts
8
10 auth sufficient /lib/security/pam_timestamp.so
11 session optional /lib/security/pam_timestamp.so
12
13
15 In a nutshell, pam_timestamp caches successful authentication attempts,
16 and allows you to use a recent successful attempt as the basis for
17 authentication.
18
19 When an application opens a session using pam_timestamp, a timestamp
20 file is created in the timestampdir directory for the user. When an
21 application attempts to authenticate the user, a pam_timestamp will
22 treat a sufficiently- recent timestamp file as grounds for succeeding.
23
24
26 debug turns on debugging via syslog(3).
27
28 timestampdir=name
29 tells pam_timestamp.so where to place and search for timestamp
30 files. This should match the directory configured for sudo(1)
31 in the sudoers(5) file.
32
33 timestamp_timeout=number
34 tells pam_timestamp.so how long it should treat timestamp files
35 as valid after their last modification date. This should match
36 the value configured for sudo(1) in the sudoers(5) file.
37
38 verbose
39 attempt to inform the user when access is granted.
40
41
43 /etc/pam.d/some-config-tool:
44 auth sufficient /lib/security/pam_timestamp.so verbose auth required
45 /lib/security/pam_unix.so
46 session required /lib/security/pam_permit.so session optional
47 /lib/security/pam_timestamp.so
48
49
51 Users can get confused when they aren't always asked for passwords when
52 running a given program. Some users reflexively begin typing informa‐
53 tion before noticing that it's not being asked for.
54
55
57 pam_timestamp_check(8)
58
59
61 Let's hope not, but if you find any, please email the author.
62
63
65 Nalin Dahyabhai <nalin@redhat.com>
66
67
68
69Red Hat Linux 2002/02/07 pam_timestamp(8)