Date: Mon, 19 Feb 2001 11:10:54 +0100 From: Ragnar Beer <rbeer@uni-goettingen.de> To: "Brandon Hicks" <fbsdsec@killaz-r-us.com> Subject: Re: Fw: Remote logging Message-ID: <p04330103b6b6a0a0ca31@[134.76.136.114]> In-Reply-To: <008201c099fa$38ab5480$57304c42@main.cox-internet.com> References: <008201c099fa$38ab5480$57304c42@main.cox-internet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
>-----Original Message----- >From: Brandon Hicks <fbsdsec@killaz-r-us.com> >To: Carroll Kong <damascus@home.com> >Date: Sunday, February 18, 2001 1:29 PM >Subject: Re: Remote logging > > >>My FreeBSD box is down, so i can't check this out.... We are moving around >>some things in the new server room. But I'm about to have 8 FreeBSD Boxes >>up, and plus one here in my office... with no daemon running on it and only >>to monitor the others. So, I would like this Information as well. Can >>someone see if syslogd says something when killed? If not can someone >write >>a patch for it, to make it says something like "Syslogd: Killed" at > >least.... Good idea! But if you have a remote intruder and you're logging via another NIC then he can take that interface down without cutting himself off and so the "killed" message wouldn't get where it should, would it? Ragnar 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?p04330103b6b6a0a0ca31>