From owner-freebsd-security Sun Apr 23 21:26:39 2000 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 26B6F37B7BA for ; Sun, 23 Apr 2000 21:26:36 -0700 (PDT) (envelope-from brett@lariat.org) Received: from mustang.lariat.org (IDENT:ppp0.lariat.org@lariat.lariat.org [206.100.185.2]) by lariat.lariat.org (8.9.3/8.9.3) with ESMTP id WAA07867; Sun, 23 Apr 2000 22:26:21 -0600 (MDT) Message-Id: <4.3.1.2.20000423215640.00aea820@localhost> X-Sender: brett@localhost X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Sun, 23 Apr 2000 21:59:19 -0600 To: Mike Silbersack , Wes Peters From: Brett Glass Subject: Re: stream.c followup / MFC request Cc: security@FreeBSD.ORG In-Reply-To: References: <38FFB270.C4C8DD9F@softweyr.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-security@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I applied my own patch. I certainly HOPE that the 3.x branch is being updated. 4.0 shows promise, but we never run any new version on a production machine until it's at least at .2 or .3. It's unfortunate that many of the developers seem to concentrate on the bleeding edge when BSD gets its reputation for stability from the "stable" branches. --Brett Glass At 09:17 PM 4/23/2000, Mike Silbersack wrote: >On Thu, 20 Apr 2000, Wes Peters wrote: > > > Mike Silbersack wrote: > > > > > > So, my question is this: Would someone be willing to give Wes's patch > > > one more lookover and commit it to the RELENG_3 branch? > > > > If everyone is comfortable with it, I'll commit it. > >Hm, looks like nobody on this list is running 3.x anymore. > >FWIW, I haven't had any problems since I started using a kernel with the >patch applied, I think it's safe to go ahead. > >Mike "Silby" Silbersack > > > >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