From owner-freebsd-security  Sun Jul 11  2: 1:53 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 BDC1815156
	for <security@FreeBSD.ORG>; Sun, 11 Jul 1999 02:01:48 -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 TAA01593;
	Sun, 11 Jul 1999 19:02:08 +1000 (EST)
From: Darren Reed <avalon@coombs.anu.edu.au>
Message-Id: <199907110902.TAA01593@cheops.anu.edu.au>
Subject: Re: Syslog alternatives?
To: imp@village.org (Warner Losh)
Date: Sun, 11 Jul 1999 19:02:08 +1000 (EST)
Cc: alla@sovlink.ru, avalon@coombs.anu.edu.au, security@FreeBSD.ORG
In-Reply-To: <199907091628.KAA20328@harmony.village.org> from "Warner Losh" at Jul 9, 99 10:28:15 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 Warner Losh, sie said:
> 
> In message <3785AB58.2B3D8F05@sovlink.ru> Alla Bezroutchko writes:
> : > Prove to me that your log files have any integrity, in such a way that
> : > I cannot dispute it.
> : 
> : How integrity is achieved with syslog's alternatives?
> 
> That's a good question....  In order to do that, you'd have to have
> some kind of public-key private-key mechanism based on shared secrets
> to be sure.  I'm not sure how you can really achieve a secure log file
> integrity when things like VI exist...

Who says it needs to be stored in the same file ?

Darren


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