From owner-freebsd-security@FreeBSD.ORG Tue Mar 30 07:43:02 2004 Return-Path: Delivered-To: freebsd-security@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 263A816A4CE for ; Tue, 30 Mar 2004 07:43:02 -0800 (PST) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id DD97243D49 for ; Tue, 30 Mar 2004 07:43:01 -0800 (PST) (envelope-from nectar@celabo.org) Received: from localhost (localhost [127.0.0.1]) by gw.celabo.org (Postfix) with ESMTP id 740225487E; Tue, 30 Mar 2004 09:43:01 -0600 (CST) Received: from gw.celabo.org ([127.0.0.1]) by localhost (hellblazer.celabo.org [127.0.0.1]) (amavisd-new, port 10024) with SMTP id 83042-06; Tue, 30 Mar 2004 09:42:50 -0600 (CST) Received: from lum.celabo.org (lum.celabo.org [10.0.1.107]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "lum.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id 71C9554893; Tue, 30 Mar 2004 09:41:57 -0600 (CST) Received: by lum.celabo.org (Postfix, from userid 501) id AC90F18336D; Tue, 30 Mar 2004 08:24:16 -0600 (CST) Date: Tue, 30 Mar 2004 08:24:16 -0600 From: "Jacques A. Vidrine" To: Michael Nottebrock Message-ID: <20040330142416.GJ10949@lum.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , Michael Nottebrock , Oliver Eikemeier , FreeBSD Security References: <40686785.7020002@fillmore-labs.com> <20040329185347.GB87233@madman.celabo.org> <40687E18.9060907@fillmore-labs.com> <20040329201926.GA88529@madman.celabo.org> <40689343.4080602@fillmore-labs.com> <4068A0AF.2090807@gmx.net> <4068A90A.7000104@fillmore-labs.com> <4068B881.4010304@gmx.net> <20040330045646.GD5998@madman.celabo.org> <406912E7.4040806@gmx.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <406912E7.4040806@gmx.net> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.6i cc: FreeBSD Security cc: Oliver Eikemeier Subject: Re: cvs commit: ports/multimedia/xine Makefile X-BeenThere: freebsd-security@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Security issues [members-only posting] List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 30 Mar 2004 15:43:02 -0000 On Tue, Mar 30, 2004 at 08:25:43AM +0200, Michael Nottebrock wrote: > Right, and I have no problem with that (I _like_ portaudit :-)). However, > it seems to me that marking ports FORBIDDEN for security reasons is more or > less obsoleted (and made redundant) by portaudit/VuXML and committers > having to hand-scan VuXML for updates and mark ports FORBIDDEN by hand just > seems like duplicated (and error-prone) work... so maybe it's time to to > away with marking ports FORBIDDEN for security reasons completely? Maybe :-) > Also, what eik says about integrating portaudit into sysinstall (does this > imply moving portaudit into the base-system at some point?) sounds very > good to me, but I still don't like security-by-default schemes which can't > be disabled by flipping a switch. FORBIDDEN ports are an example for this, > forcing users to hand-edit a port Makefile in order to make it buildable > (especially when the security issue is really minor or I'm not even > affected) is just a tad too BOFH-ish for my taste. Well, a reason I mentioned `hooks' to Oliver is because I have my own unfinished scheme for managing this issue. It takes a different approach than portaudit, that I think you'd like. But I don't want to say more because it is vaporware until release :-) Basically, any attempt to integrate such vulnerability checking into pkg_* tools or bsd.port.mk needs to be done so that tools can plug-in. In that fashion, users have a choice of security policy. The commit of a `Vulnerability Check' to bsd.port.mk happened under my radar, so I didn't comment on it at the time. It may or may not be sufficient for hooks as it is now. Cheers, -- Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org