From owner-freebsd-security Fri Jul 9 2: 6:56 1999 Delivered-To: freebsd-security@freebsd.org Received: from outpost.cpmc.net (outpost.lukarcos.com [195.239.240.132]) by hub.freebsd.org (Postfix) with SMTP id 77D1715540 for ; Fri, 9 Jul 1999 02:06:42 -0700 (PDT) (envelope-from sgk@outpost.cpmc.net) Received: (qmail 72927 invoked by uid 911); 9 Jul 1999 09:05:30 -0000 Date: Fri, 9 Jul 1999 13:05:30 +0400 From: Sergei Kolobov To: Robert Watson Cc: Darren Reed , Alla Bezroutchko , security@FreeBSD.ORG Subject: Re: Syslog alternatives? Message-ID: <19990709130530.A72919@cpmc.net> References: <199907090707.RAA16350@cheops.anu.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.5i In-Reply-To: ; from Robert Watson on Fri, Jul 09, 1999 at 04:20:13AM -0400 Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Robert Watson wrote: > if configured carefully. There have been discussions of alternatives, and > I think someone claimed to have written a secure syslog at one point; I > don't have a reference for it. I believe Schneier coauthored a paper on I guess you were referring to nsyslogd by Darren Reed: 06/01/1999 - Darren Reed, the author of IP Filter, announced the release of Nsyslog, a syslog implementation that * supports TCP connections * can be used with SSL to encrypt delivery of syslog messages * can be used with libwrap and /etc/hosts.{allow,deny} to only accept log connections from given hosts * allows you to set a desired fsync rate for given log files More information is available at: http://coombs.anu.edu.au/~avalon/nsyslog.html --sgk To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message