From owner-freebsd-security Sat Mar 4 9:28:50 2000 Delivered-To: freebsd-security@freebsd.org Received: from vinyl.sentex.ca (vinyl.sentex.ca [209.112.4.14]) by hub.freebsd.org (Postfix) with ESMTP id 4DABD37B73C for ; Sat, 4 Mar 2000 09:28:46 -0800 (PST) (envelope-from mike@sentex.net) Received: from granite.sentex.net (granite-atm.sentex.ca [209.112.4.1]) by vinyl.sentex.ca (8.9.3/8.9.3) with ESMTP id MAA14261 for ; Sat, 4 Mar 2000 12:28:42 -0500 (EST) (envelope-from mike@sentex.net) Received: from chimp (ospf-mdt.sentex.net [205.211.164.81]) by granite.sentex.net (8.8.8/8.6.9) with ESMTP id MAA01009; Sat, 4 Mar 2000 12:28:40 -0500 (EST) Message-Id: <4.2.2.20000304122608.03c1cb08@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 04 Mar 2000 12:27:16 -0500 To: Jonathan Fortin From: Mike Tancsa Subject: Re: work around for local DoS ? (kern 17152) Cc: freebsd-security@FreeBSD.ORG In-Reply-To: References: <4.2.2.20000304114458.03c48b48@mail.sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org At 12:21 PM 3/4/2000 -0500, Jonathan Fortin wrote: >ulimit In what way? The bug does not appear to be a resource issue ---Mike >On Sat, 4 Mar 2000, Mike Tancsa wrote: > > > > > I regular catch and kill accounts that try lamo things like fork bombs, so > > these sorts of things worry me. Is there any way to protect against the > > bug mentioned in PR 17152 (kernel panic:aio_write) Current seems to > survive > > just fine, but STABLE panics ? > > > > ---Mike > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-security" in the body of the message > > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message