Date: Sun, 11 Jul 1999 20:15:48 +1000 (EST) From: Darren Reed <avalon@coombs.anu.edu.au> To: robert+freebsd@cyrus.watson.org Cc: sgk@cpmc.net, avalon@coombs.anu.edu.au, alla@sovlink.ru, security@FreeBSD.ORG Subject: Re: Syslog alternatives? Message-ID: <199907111015.UAA02040@cheops.anu.edu.au> In-Reply-To: <Pine.BSF.3.96.990709053246.24202H-100000@fledge.watson.org> from "Robert Watson" at Jul 9, 99 05:42:26 am
next in thread | previous in thread | raw e-mail | index | archive | help
In some mail from Robert Watson, sie said: [...] > Wasn't the one I was thinking of, but it certainly qualifies :-). Does it > actually authenticate the log data, or only the connection? It authenticates the connection (SSL), it can also authenticate the data exchanged (protection against connection corruption). It does not authenticate what gets saved to disk - that takes a human. > I had in mind > a protected process or kernel integrity protection service perhaps > involving key management for signing of log records, plus rotation of key > material, etc. I'll have to dig up the secure logging paper. And how do you authenticate what the kernel says ? To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199907111015.UAA02040>