Re: bin/42540: /usr/bin/login does not log normal logins, does not log IP addresses

[christos%zoulas.com@localhost (Christos Zoulas)]

The following reply was made to PR bin/42540; it has been noted by GNATS.

From: christos%zoulas.com@localhost (Christos Zoulas)
To: gnats-bugs%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost, 
netbsd-bugs%netbsd.org@localhost
Cc: 
Subject: Re: bin/42540: /usr/bin/login does not log normal logins, does not log 
IP addresses
Date: Tue, 29 Dec 2009 10:48:32 -0500

 On Dec 29, 10:44am, christos%zoulas.com@localhost (Christos Zoulas) wrote:
 -- Subject: Re: bin/42540: /usr/bin/login does not log normal logins, does no
 
 | Yes, because it is only being passed in the hostname; it does not
 | lookup anything. Even the hostname passed can be bogus (although
 | one presumes that the daemon that forks login is trusted).
 | 
 | So your desired behavior is to use getpeername(2) to determine if
 | the login is remote and always syslog(LOG_INFO the infomation?
 
 Now that I looked more into it, it will use getpeername(2) to fill in
 the address in wtmpx. Isn't that good enough? (looking through the wtmpx
 records?)
 
 christos