From owner-freebsd-questions Sun Jul 18 23:20:27 1999 Delivered-To: freebsd-questions@freebsd.org Received: from twwells.com (twwells.com [209.118.236.57]) by hub.freebsd.org (Postfix) with SMTP id F170C14E36 for ; Sun, 18 Jul 1999 23:20:25 -0700 (PDT) (envelope-from news@twwells.com) Received: from news by twwells.com with local (Exim 1.71 #2) id 1166kU-0003zG-00; Mon, 19 Jul 1999 02:18:02 -0400 From: bill@twwells.com (T. William Wells) To: freebsd-questions@freebsd.org Subject: Re: Why is this code in syslogd.c? Message-ID: <7mufng$eev$1@twwells.com> References: <19990718194853.A29020@internal> <19990719080007.A7410@internal> Date: Mon, 19 Jul 1999 02:18:02 -0400 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <19990719080007.A7410@internal>, Andre Albsmeier 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 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