Date: Mon, 19 Jul 1999 08:00:07 +0200 From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de> To: "T. William Wells" <bill@twwells.com> Cc: Andre Albsmeier <andre.albsmeier@mchp.siemens.de>, freebsd-questions@FreeBSD.ORG Subject: Re: Why is this code in syslogd.c? Message-ID: <19990719080007.A7410@internal> In-Reply-To: <E115vml-00089S-00@twwells.com>; from T. William Wells on Sun, Jul 18, 1999 at 02:35:39PM -0400 References: <19990718194853.A29020@internal> <E115vml-00089S-00@twwells.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 18-Jul-1999 at 14:35:39 -0400, T. William Wells wrote: > > On Sun, 18-Jul-1999 at 13:18:01 -0400, T. William Wells wrote: > > > Kernel messages should come from the kernel. If users could > > > generate them, this could cause many problems. > > > > How can a user generate a kernel message? If I do a > > "logger -p kern.crit blah" this is logged as user.crit even if > > the code in question is commented out... > > If you check out the syslog() code itself, you'll note that it > does this translation; logger calls syslog(). But syslog() is an > ordinary C function; there is nothing to keep an application from > generating "kernel" messages if they don't use syslog() itself but > instead generate the messages themselves. OK, I found the place, thanks for the hint. But I still can't understand what's the reason for doing that. OK, a user could fake a kernel message but now he can do the same thing with all other facilities. He can fake mail or auth messages as he likes... Thanks, -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19990719080007.A7410>