From owner-freebsd-security Tue Oct 6 01:17:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA29743 for freebsd-security-outgoing; Tue, 6 Oct 1998 01:17:23 -0700 (PDT) (envelope-from owner-freebsd-security@FreeBSD.ORG) Received: from mail.ftf.dk (mail.ftf.net [129.142.64.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA29733 for ; Tue, 6 Oct 1998 01:17:16 -0700 (PDT) (envelope-from regnauld@deepo.prosa.dk) Received: from mail.prosa.dk ([192.168.100.254]) by mail.ftf.dk (8.8.8/8.8.8/gw-ftf-1.0) with ESMTP id KAA29497; Tue, 6 Oct 1998 10:22:13 +0200 (CEST) (envelope-from regnauld@deepo.prosa.dk) X-Authentication-Warning: mail.ftf.dk: Host [192.168.100.254] claimed to be mail.prosa.dk Received: from deepo.prosa.dk (deepo.prosa.dk [192.168.100.10]) by mail.prosa.dk (8.8.8/8.8.5/prosa-1.1) with ESMTP id KAA04211; Tue, 6 Oct 1998 10:35:02 +0200 (CEST) Received: (from regnauld@localhost) by deepo.prosa.dk (8.8.8/8.8.5/prosa-1.1) id KAA10863; Tue, 6 Oct 1998 10:27:06 +0200 (CEST) Message-ID: <19981006102706.39881@deepo.prosa.dk> Date: Tue, 6 Oct 1998 10:27:06 +0200 From: Philippe Regnauld To: brooks@one-eyed-alien.net Cc: security@FreeBSD.ORG Subject: Re: The necessary steps for logging (the problem is fixed) References: <4.1.19981005093222.041901f0@mail.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e In-Reply-To: ; from brooks@one-eyed-alien.net on Mon, Oct 05, 1998 at 10:59:28AM -0700 X-Operating-System: FreeBSD 2.2.6-RELEASE i386 Phone: +45 3336 4148 Address: Ahlefeldtsgade 16, 1359 Copenhagen K, Denmark Organization: PROSA Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org brooks@one-eyed-alien.net writes: > On Mon, 5 Oct 1998, Brett Glass wrote: > > being the same as spaces in sendmail.cf and Makefiles. One thing you can > do in this case is use a sanity checker for syslog.conf files like the one > I wrote. You can get it at: > > http://www3.hmc.edu/~brdavis/software/syslogck/ One thing that could be done was to have a wrapper (like crontab -e) that checked syntax (f.ex, with your script) before installing the syslog.conf ? The wrapper would complain noisily and refuse to let you save the file if the file was bogus. syslog -e ? :-) -- -[ Philippe Regnauld / sysadmin / regnauld@deepo.prosa.dk / +55.4N +11.3E ]- The Internet is busy. Please try again later. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message