From owner-freebsd-security  Fri Jul  9  9:37:29 1999
Delivered-To: freebsd-security@freebsd.org
Received: from suburbia.net (gw.iq.org [203.4.184.233])
	by hub.freebsd.org (Postfix) with SMTP id 6A2BE155CB
	for <security@FreeBSD.ORG>; Fri,  9 Jul 1999 09:37:21 -0700 (PDT)
	(envelope-from proff@suburbia.net)
Received: (qmail 22244 invoked by uid 110); 9 Jul 1999 16:34:59 -0000
Message-ID: <19990709163459.22243.qmail@suburbia.net>
From: proff@suburbia.net
Subject: Re: Syslog alternatives?
In-Reply-To: <199907091628.KAA20328@harmony.village.org> from Warner Losh at "Jul 9, 99 10:28:15 am"
To: imp@village.org (Warner Losh)
Date: Sat, 10 Jul 1999 02:34:59 +1000 (EST)
Cc: alla@sovlink.ru, avalon@coombs.anu.edu.au, security@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL32 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-security@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

> 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...
> 
> Warner

Just because you can't think of an answer doesn't mean there isn't one :)

Cheers,
Julian.
 



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