Date: Tue, 20 Jul 1999 11:14:06 +0200 From: Andre Albsmeier <andre.albsmeier@mchp.siemens.de> To: "T. William Wells" <bill@twwells.com> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: Why is this code in syslogd.c? Message-ID: <19990720111406.A35123@internal> In-Reply-To: <7mufng$eev$1@twwells.com>; from T. William Wells on Mon, Jul 19, 1999 at 02:18:02AM -0400 References: <19990718194853.A29020@internal> <E115vml-00089S-00@twwells.com> <19990719080007.A7410@internal> <7mufng$eev$1@twwells.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 19-Jul-1999 at 02:18:02 -0400, T. William Wells wrote: > In article <19990719080007.A7410@internal>, > Andre Albsmeier <andre.albsmeier@mchp.siemens.de> wrote: > : 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... > > "X is something that a user should not do but can anyway. > Therefore, we should not prevent the user from doing Y." Not very > logical, is it? It's your logic, I didn't say that. I wanted to understand why it is there. So we can summarize: The code is there to prevent users from sending faked kern.xxx messages. The code does not cover other facilities so these can still be faked. > It would be nice if there was some control over who can send what > messages. But it's not there, so we can't rely on them. However, > it _is_ there for kernel messages, which is better than nothing. 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?19990720111406.A35123>