Bug 199783

Summary:	pam_keyinit unduly noisy
Product:	[Fedora] Fedora	Reporter:	Michal Jaegermann <michal>
Component:	pam	Assignee:	Tomas Mraz <tmraz>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	rawhide
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2006-07-21 22:41:35 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 Michal Jaegermann 2006-07-21 22:09:24 UTC

Description of problem:

After recent pam changes /var/log/secure is constantly badgered
by messages in this style:

pam_keyinit(gdm:session): UID:0 [0]  GID:0 [0]
pam_keyinit(gdm:session): JOIN = 593955641
pam_keyinit(gdm:session): UID:0 [0]  GID:0 [0]
pam_keyinit(gdm:session): GET SESSION = 593955641
pam_keyinit(gdm:session): GET SESSION = 1
pam_keyinit(sshd:session): UID:0 [0]  GID:0 [0]
pam_keyinit(sshd:session): JOIN = 614504224
pam_keyinit(sshd:session): UID:0 [0]  GID:0 [0]
pam_keyinit(sshd:session): GET SESSION = 614504224
pam_keyinit(sshd:session): GET SESSION = 1

This does not look like it conveys any useful information to
a user/administrator of a system while no 'debug' option is used
in /etc/pam.d/ files.  It also looks awfully redundant.

Is this some kind of development debugging turned on which later
will disappear?  If not then logwatch should be taught about that.

Version-Release number of selected component (if applicable):
pam-0.99.5.0-3.fc6

Comment 1 Tomas Mraz 2006-07-21 22:41:35 UTC

The debugging messages were on by default. Fixed.