Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 19 Jun 2002 10:30:47 -0700 (PDT)
From:      "Jon Noack" <noackjr@compgeek.com>
To:        freebsd-questions@freebsd.org
Subject:   Re: rhetorical-questions@freebsd.org
Message-ID:  <20020619103048.28997.h003.c015.wm@mail.compgeek.com.criticalpath.net>

next in thread | raw e-mail | index | archive | help
> 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020619103048.28997.h003.c015.wm>