Date: Wed, 5 Apr 2000 13:48:36 -0500 (CDT) From: James Wyatt <jwyatt@rwsystems.net> To: matt@csis.gvsu.edu Cc: Andre Gironda <andre@sun4c.net>, goten@linux.sduteam.com, security@freebsd.org Subject: Re: Queston on secure syslogd Message-ID: <Pine.BSF.4.10.10004051345330.44209-100000@bsdie.rwsystems.net> In-Reply-To: <20000405141940.A6357@eos16.csis.gvsu.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On Wed, 5 Apr 2000 matt@csis.gvsu.edu wrote: > > Over the Internet, I'd be more likely to use scp, rsync, or CVSup > > even though I should probably use something better like IPSec or SNMPv3. > > Things like scp that copy files won't deliver messages in (pseudo) > real-time. I don't know if this is a priority for the original poster. > The simplest solution is to use a syslogd that delivers over TCP and > send messages through an ssh tunnel. My first thought was a ssh of a remote 'tail -f', but the ssh tunnel sounds best here to me too, fwiw. What about limiting the tunnel to just syslog so you don't have anyone trying to hack a machine through it. - Jy@ 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?Pine.BSF.4.10.10004051345330.44209-100000>