From owner-freebsd-security  Fri Jul  9  0: 8:28 1999
Delivered-To: freebsd-security@freebsd.org
Received: from cheops.anu.edu.au (cheops.anu.edu.au [150.203.76.24])
	by hub.freebsd.org (Postfix) with ESMTP id 63CB914BDB
	for <security@FreeBSD.ORG>; Fri,  9 Jul 1999 00:08:19 -0700 (PDT)
	(envelope-from avalon@cheops.anu.edu.au)
Received: (from avalon@localhost)
	by cheops.anu.edu.au (8.9.1/8.9.1) id RAA16350;
	Fri, 9 Jul 1999 17:07:05 +1000 (EST)
From: Darren Reed <avalon@coombs.anu.edu.au>
Message-Id: <199907090707.RAA16350@cheops.anu.edu.au>
Subject: Re: Syslog alternatives?
To: alla@sovlink.ru (Alla Bezroutchko)
Date: Fri, 9 Jul 1999 17:07:04 +1000 (EST)
Cc: security@FreeBSD.ORG
In-Reply-To: <37859B74.7528C158@sovlink.ru> from "Alla Bezroutchko" at Jul 9, 99 10:49:24 am
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

In some mail from Alla Bezroutchko, sie said:
> 
> This is not exactly FreeBSD security question. More like general
> Unix security. Hope it is not completely off topic. 
> 
> I was looking at several syslogd alternatives (BTW, I don't think
> I have a complete list, can you suggest something?) and found out
> that I don't understand what is wrong with traditional syslogd from 
> security standpoint.
> 
> Could someone explain me or point me to some resources that explain
> why syslogd is bad?

Prove to me that your log files have any integrity, in such a way that
I cannot dispute it.

Darren


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-security" in the body of the message