Bug 188722

Summary:	kdm pam_timestamp and pam_selinux messages
Product:	[Fedora] Fedora	Reporter:	Orion Poplawski <orion>
Component:	pam	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	5
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	pam-0.99.5.0-3	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-07-17 13:20:26 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Orion Poplawski 2006-04-12 16:32:09 UTC

Description of problem:
Seeing the following occassionally:

kdm: :0[21888]: pam_timestamp(kdm:auth): timestamp file
`/var/run/sudo/root/:0:vasha' is older than oldest login, disallowing access to
kdm for user root
 kdm: :0[21888]: pam_timestamp(kdm:session): updated timestamp file
`/var/run/sudo/root/:0:vasha'
 kdm: :0[21888]: pam_selinux(kdm:session): Warning!  Could not get current
context for /dev/:0, not relabeling: No such file or directory


Version-Release number of selected component (if applicable):
kdebase-3.5.1-5


Also see pam_timestamp messages on up to date FC4:
kdm: :0[21986]: pam_timestamp: timestamp file `/var/run/sudo/root/:0:mfw' has
unacceptable age (175195 seconds), disallowing access to kdm for user root

kdm: :0[501]: pam_timestamp: timestamp file `/var/run/sudo/root/:0:herten' is
older than oldest login, disallowing access to kdm for user root

Just wondering if this is a problem or not.  Logwatch reports them as Unmatched
Entries.

Comment 1 Orion Poplawski 2006-06-01 14:59:05 UTC

Reassigning to pam.

Comment 2 Tomas Mraz 2006-07-17 08:55:32 UTC

The pam_timestamp entries are fully legitimate information messages. However
they don't mean there is a problem (so they could be probably ignored in
logwatch). The pam_selinux message probably shouldn't be reported as this is not
something you could/should fix.