From owner-freebsd-security@FreeBSD.ORG Mon Apr 19 02:50:05 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A6F3416A4CE; Mon, 19 Apr 2004 02:50:05 -0700 (PDT) Received: from www.svzserv.kemerovo.su (www.svzserv.kemerovo.su [213.184.65.80]) by mx1.FreeBSD.org (Postfix) with ESMTP id 077E843D49; Mon, 19 Apr 2004 02:50:02 -0700 (PDT) (envelope-from eugen@kuzbass.ru) Received: from kuzbass.ru (kost [213.184.65.82])i3J9nwM4068962; Mon, 19 Apr 2004 17:49:58 +0800 (KRAST) (envelope-from eugen@kuzbass.ru) Message-ID: <4083A0C2.3F86159E@kuzbass.ru> Date: Mon, 19 Apr 2004 17:49:54 +0800 From: Eugene Grosbein Organization: SVZServ X-Mailer: Mozilla 4.8 [en] (Windows NT 5.0; U) X-Accept-Language: ru,en MIME-Version: 1.0 To: "Crist J. Clark" References: <1998.213.112.193.35.1082212115.squirrel@mail.hackunite.net> <20040419021239.GA67288@blossom.cjclark.org> Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit X-Mailman-Approved-At: Tue, 20 Apr 2004 02:16:30 -0700 cc: freebsd-security@freebsd.org Subject: Re: Is log_in_vain really good or really bad? X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 19 Apr 2004 09:50:05 -0000 "Crist J. Clark" wrote: > > On Sat, Apr 17, 2004 at 04:28:35PM +0200, z3l3zt@hackunite.net wrote: > [snip] > > > My server box is a Intel Celeron 733Mhz, 384Mb of RAM.. yet it's slow from > > time to time since I only run ATA66 due to the old motherboard. When this > > "attack" occured yesterday, the box almost died and the box were working > > 100%.. all users who were logged in got "spammed" since the default > > *.emerg in /etc/syslog.conf is set to "*" .. > > Not sure what that has to do with anything. The log_in_vain messages get > logged at "info" level. What messages were your users seeing? > -- > Crist J. Clark | cjclark@alum.mit.edu I believe that was a bug in syslogd and this bug is already fixed in both of CURRENT and STABLE for not so long. Eugene