Bug 8247 - /bin/login possibly printing null string in syslog
/bin/login possibly printing null string in syslog
Status: CLOSED NOTABUG
Product: Red Hat Linux
Classification: Retired
Component: util-linux (Show other bugs)
6.1
All Linux
medium Severity medium
: ---
: ---
Assigned To: Crutcher Dunnavant
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2000-01-06 18:37 EST by Viraj Alankar
Modified: 2008-05-01 11:37 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2000-02-03 16:43:27 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Viraj Alankar 2000-01-06 18:37:40 EST
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 15:56:59 EST
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 16:43:59 EST
This is normal behaviour when logging in from a local terminal. It is a NULL
pointer and that's perfectly OK with printf...

Note You need to log in before you can comment on or make changes to this bug.