Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 15997

Summary:	PAM and syslog logging of su attempts
Product:	[Retired] Red Hat Linux	Reporter:	Need Real Name <arhodes>
Component:	pam	Assignee:	Nalin Dahyabhai <nalin>
Status:	CLOSED RAWHIDE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.2
Target Milestone:	---
Target Release:	---
Hardware:	i386
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2000-08-11 14:50: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 Need Real Name 2000-08-11 14:50:24 UTC

syslog entries for invalid su varies for different users.
On my system, if I fail while attempting an su to: "root" or "named",
the syslog entries appear as:

Aug 11 09:25:25 mybox PAM_pwdb[22699]: authentication failure;
arhodes(uid=500) -> root for su service
Aug 11 09:25:31 mybox PAM_pwdb[22700]: authentication failure;
arhodes(uid=500) -> named for su service

However, if I attempt to su to "bin" or "operator", all I get in
the syslog entry is:

Aug 11 09:51:38 xanax PAM_pwdb[22733]: get passwd; pwdb: request not
recognized
Aug 11 09:51:54 xanax PAM_pwdb[22734]: get passwd; pwdb: request not
recognized

Anyone know why PAM_pwdb would exhibit these different behaviors?

Comment 1 Nalin Dahyabhai 2000-09-12 20:15:30 UTC

The pam_pwdb module is being replaced by the pam_unix module (which works
correctly) for upcoming releases.