Re: bin/47449: syslogd doesn't honor mesg n

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

The following reply was made to PR bin/47449; 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/47449: syslogd doesn't honor mesg n
Date: Tue, 15 Jan 2013 11:53:29 -0500

 On Jan 15,  5:25am, dholland%netbsd.org@localhost 
(dholland%netbsd.org@localhost) wrote:
 -- Subject: bin/47449: syslogd doesn't honor mesg n
 
 | syslogd does not honor mesg n (g+w permission) on the ttys of users it
 | sends logs to.
 | 
 | This is a nuisance sometimes.
 | 
 | >How-To-Repeat:
 | 
 | Create a test user, add it as a destination in syslog.conf (e.g.
 | cron.*       testuser), log in, set mesg n, and watch the messages roll in
 | regardless.
 | 
 | >Fix:
 | 
 | As syslogd runs as root it needs to explicitly check for g+w
 | permission, instead of just using the same tty message code as other
 | things and assuming it'll get EACCES when mesg n is set.
 | 
 | Probably it should also override mesg n for LOG_EMERG messages, which
 | are traditionally walled to everyone.
 
 Do you have an example syslogd implementation in mind that honors that?
 What about messages explicitly sent to that user?
 
 christos