Date: Sun, 2 May 2004 14:36:07 -0500 From: "Jacques A. Vidrine" <nectar@FreeBSD.org> To: Xin LI <delphij@frontfree.net> Cc: freebsd-security@FreeBSD.org Subject: Re: What's our current policy on ports FORBIDDEN knob? Message-ID: <20040502193607.GB33431@madman.celabo.org> In-Reply-To: <20040502172910.GA775@frontfree.net> References: <20040502172910.GA775@frontfree.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, May 03, 2004 at 01:29:10AM +0800, Xin LI wrote: > Greetings, > > I'm a little curious about the way FORBIDDEN knob is used in ports system. > Traditionally, we use it to mark a port which have known security issue, > with the new vuxml mechanism, are we still doing the same thing when > necessary? Or, only the "critical" ones, for example, remote exploitable > buffer overruns, etc? > > If the second assumption (only critical ones are marked FORBIDDEN) > is true, then what's our criteria of what should be marked FORBIDDEN > or not? Say, how serious a bug should be before a port is marked > FORBIDDEN? > > Someone who knows about these things please clarify this. Thanks in advance! The VuXML document is used to record practically all security issues, large or small. FORBIDDEN is more subjective. Personally, I mark a port FORBIDDEN if I believe it presents immediate danger to users. Cheers, -- Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040502193607.GB33431>