From owner-freebsd-security Tue Aug 17 22:21:46 1999 Delivered-To: freebsd-security@freebsd.org Received: from lariat.lariat.org (lariat.lariat.org [206.100.185.2]) by hub.freebsd.org (Postfix) with ESMTP id E0E9314F31 for ; Tue, 17 Aug 1999 22:21:42 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id XAA04964; Tue, 17 Aug 1999 23:21:47 -0600 (MDT) Message-Id: <4.2.0.58.19990817231641.04640280@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Pro Version 4.2.0.58 Date: Tue, 17 Aug 1999 23:18:00 -0600 To: Matthew Dillon From: Brett Glass Subject: Re: Any work around for this FreeBSD bug/DoS ? Cc: Mike Tancsa , freebsd-security@FreeBSD.ORG In-Reply-To: <199908180031.RAA40827@apollo.backplane.com> References: <4.1.19990816203409.05989960@granite.sentex.ca> <4.1.19990816213403.05a3b540@granite.sentex.ca> <4.2.0.58.19990817182156.0463ecd0@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Well, who's a kernel memory allocation expert? I would dive on this one, but I'd be coming in cold; I've never messed with that part of the kernel at all. All I know about mbuf allocation is what's in McKusick. --Brett At 05:31 PM 8/17/99 -0700, Matthew Dillon wrote: >: >:Perhaps. But this is no excuse for leaving such a serious hole open! No >:unprivileged user should be able to crash the system under any circumstances. >:Especially not this easily. >: >:--Brett > > I agree, but being a freeware project someone has to decide to fix it. > I've got my hands full with VM (and not having commit privs already makes > that difficult enough). > > -Matt > Matthew Dillon > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-security" in the body of the message