From owner-freebsd-questions Wed Jun 19 10:31:31 2002 Delivered-To: freebsd-questions@freebsd.org Received: from c015.snv.cp.net (h004.c015.snv.cp.net [209.228.35.119]) by hub.freebsd.org (Postfix) with SMTP id 28D9C37B43F for ; Wed, 19 Jun 2002 10:30:49 -0700 (PDT) Received: (cpmta 23566 invoked from network); 19 Jun 2002 10:30:48 -0700 Received: from 209.228.35.118 (HELO mail.compgeek.com.criticalpath.net) by smtp.compgeek.com (209.228.35.119) with SMTP; 19 Jun 2002 10:30:48 -0700 X-Sent: 19 Jun 2002 17:30:48 GMT Received: from [65.69.2.116] by mail.compgeek.com with HTTP; Wed, 19 Jun 2002 10:30:47 -0700 (PDT) Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 7bit MIME-Version: 1.0 To: freebsd-questions@freebsd.org From: "Jon Noack" Subject: Re: rhetorical-questions@freebsd.org X-Sent-From: noackjr@compgeek.com Date: Wed, 19 Jun 2002 10:30:47 -0700 (PDT) X-Mailer: Web Mail 5.0.10-14 Message-Id: <20020619103048.28997.h003.c015.wm@mail.compgeek.com.criticalpath.net> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > Okay, 4.6-RELEASE has been out for what, a few days? And it was released > with broken PPPOE code in the kernel source. There's a documented bug. > So why hasn't it been fixed in CVS yet for relang_4_6? If it's bothering you so much why don't you fix it? Seriously. That's part of what this whole open source thing is about. When you find a bug you report it nd either wait patiently until it gets fixed or fix it yourself. The only complaining should occur about Microsoft ;-). > On a related note, why is there not yet a FreeBSD security advisory for > the largest apache vulnerability in recent history? Historically I've noticed security advisories about ports take a while to come out. Apache may *seem* like it's part of FreeBSD (heck, even the good folks at apache.org run FreeBSD), but it's really not. Apache released an advisory and that is actually about all that is required. Should FreeBSD keep track of the security status of every port? That's up to the port maintainer (marking port forbidden until new version comes out) and whoever develops the code. I've noticed if there is a FreeBSD-specific problem with a port a port security advisory will be released -- this, on the other hand, affects nearly every version of Apache in modern history. > These are problems I'd expet to hear about with Linux (pick a distro), > not BSD. The PPPoE thing is frustrating, but if you're not actively involved in the fix then give it time. We just had a release and lots of people are a little low on motivation... Jon To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message