Bug 8247

Summary:	/bin/login possibly printing null string in syslog
Product:	[Retired] Red Hat Linux	Reporter:	Viraj Alankar <valankar>
Component:	util-linux	Assignee:	Crutcher Dunnavant <crutcher>
Status:	CLOSED NOTABUG	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.1
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:	2000-02-03 21:43:27 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 Viraj Alankar 2000-01-06 23:37:40 UTC

I noticed the following message from syslog:

Jan  6 16:34:20 myserver login: FAILED LOGIN SESSION FROM
xxx.edu FOR (null), Error in service module

The '(null)' looks suspiciously to be a printout of a null string.

Comment 1 Viraj Alankar 2000-01-23 20:56:59 UTC

This also appears to happen with RH 6.1:

Jan 17 11:02:22 mikrosopht PAM_pwdb[2396]: authentication failure; LOGIN(uid=0)
-> valankar for login service
Jan 17 11:02:23 mikrosopht login[2396]: FAILED LOGIN 1 FROM (null) FOR valankar,
Authentication failure
Jan 17 11:02:26 mikrosopht PAM_pwdb[2396]: (login) session opened for user
valankar by LOGIN(uid=0)

Comment 2 Elliot Lee 2000-02-03 21:43:59 UTC

This is normal behaviour when logging in from a local terminal. It is a NULL
pointer and that's perfectly OK with printf...