pam_timestamp_check

Check to see if the default timestamp is valid

Synopsis

pam_timestamp_check [-k] [-d] [target_user]

add an example, a script, a trick and tips

: email address (won't be displayed)
: name

Step 2

Thanks for this example ! - It will be moderated and published shortly.

Feel free to post other examples Oops ! There is a tiny cockup. A damn 404 cockup. Please contact the loosy team who maintains and develops this wonderful site by clicking in the mighty feedback button on the side of the page. Say what happened. Thanks!

examples

auth sufficient pam_timestamp.so verbose
auth required pam_unix.so

session required pam_unix.so
session optional pam_timestamp.so

description

With no arguments pam_timestamp_check will check to see if the default timestamp is valid, or optionally remove it.

options

-k

Instead of checking the validity of a timestamp, remove it. This is analogous to sudo's -k option.

-d

Instead of returning validity using an exit status, loop indefinitely, polling regularly and printing the status on standard output.

target_user

By default pam_timestamp_check checks or removes timestamps generated by pam_timestamp when the user authenticates as herself. When the user authenticates as a different user, the name of the timestamp file changes to accommodate this. target_user allows to specify this user name.

files

/var/run/sudo/...

timestamp files and directories

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.

return values

The timestamp is valid.

The binary is not setuid root.

Invalid invocation.

User is unknown.

Permissions error.

Invalid controlling tty.

Timestamp is not valid.

see also

pam_timestamp_check, pam.conf, pam.d, pam

author

pam_tally was written by Nalin Dahyabhai.