From owner-freebsd-security Mon Feb 19 2:11:11 2001 Delivered-To: freebsd-security@freebsd.org Received: from gwdu42.gwdg.de (gwdu42.gwdg.de [134.76.10.26]) by hub.freebsd.org (Postfix) with ESMTP id 6797837B4EC for ; Mon, 19 Feb 2001 02:11:09 -0800 (PST) Received: from partner.uni-psych.gwdg.de ([134.76.136.114]) by gwdu42.gwdg.de with esmtp (Exim 3.14 #18) id 14UnHe-0002UY-00; Mon, 19 Feb 2001 11:11:06 +0100 Mime-Version: 1.0 X-Sender: rbeer@popper.gwdg.de Message-Id: In-Reply-To: <008201c099fa$38ab5480$57304c42@main.cox-internet.com> References: <008201c099fa$38ab5480$57304c42@main.cox-internet.com> Date: Mon, 19 Feb 2001 11:10:54 +0100 To: "Brandon Hicks" From: Ragnar Beer Subject: Re: Fw: Remote logging Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >-----Original Message----- >From: Brandon Hicks >To: Carroll Kong >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