From owner-freebsd-security Sat Mar 4 8:51: 7 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 4170C37B77B for ; Sat, 4 Mar 2000 08:51:04 -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 LAA13249 for ; Sat, 4 Mar 2000 11:51:02 -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 LAA24215 for ; Sat, 4 Mar 2000 11:51:02 -0500 (EST) Message-Id: <4.2.2.20000304114458.03c48b48@mail.sentex.net> X-Sender: mdtancsa@mail.sentex.net X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.2 Date: Sat, 04 Mar 2000 11:49:37 -0500 To: freebsd-security@freebsd.org From: Mike Tancsa Subject: work around for local DoS ? (kern 17152) 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 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