Red Hat Bugzilla – Bug 71914
Inconsistent behavior with pam_timestamp
Last modified: 2015-03-04 20:11:16 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (compatible; Konqueror/3; Linux)
Description of problem:
When logging to the GNOME2 desktop:
Desktop -> Start Here -> Server Settings
The following redhat-config apps exist:
Domain Name Service
All of them EXCEPT for redhat-config-httpd uses pam_timestamp. This is inconsistent,unexpected and confusing behavior for the "newbie" Linux sysadmin who is most likely to be using these GUI configuration apps.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. less /etc/pam.d/redhat-config-httpd
2. Notice how pam_timestamp is NOT used
3. Compare to the other redhat-config apps
Actual Results: n/a
Expected Results: n/a
There are 22 /etc/pam.d/redhat-config-* files.
It looks like ALL of them use pam_timestamp except for:
TUI apps must not use pam_timestamp, which takes redhat-config-printer-tui out
of your list. Also, the command 'redhat-config-printer' may end up invoking
the TUI app, and so it also intentionally doesn't use pam_timestamp.
(The menus run 'redhat-config-printer-gui', which *does* use pam_timestamp.)
So this bug report just concerns redhat-config-httpd.
OK, fixed in CVS. Somehow this didn't make it into the fixes i made recently to
Next build will include the fix.
Read ya, Phil