From owner-freebsd-security@FreeBSD.ORG Wed Mar 17 06:23:32 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 CF86A16A4CE for ; Wed, 17 Mar 2004 06:23:32 -0800 (PST) Received: from gw.celabo.org (gw.celabo.org [208.42.49.153]) by mx1.FreeBSD.org (Postfix) with ESMTP id 686CA43D1D for ; Wed, 17 Mar 2004 06:23:32 -0800 (PST) (envelope-from nectar@celabo.org) Received: from madman.celabo.org (madman.celabo.org [10.0.1.111]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "madman.celabo.org", Issuer "celabo.org CA" (verified OK)) by gw.celabo.org (Postfix) with ESMTP id 70E0D5482B; Wed, 17 Mar 2004 08:23:31 -0600 (CST) Received: by madman.celabo.org (Postfix, from userid 1001) id 0B1806D465; Wed, 17 Mar 2004 08:23:31 -0600 (CST) Date: Wed, 17 Mar 2004 08:23:30 -0600 From: "Jacques A. Vidrine" To: "Peter C. Lai" Message-ID: <20040317142330.GA21961@madman.celabo.org> Mail-Followup-To: "Jacques A. Vidrine" , "Peter C. Lai" , freebsd-security@freebsd.org References: <20040317070051.GC716@cowbert.2y.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040317070051.GC716@cowbert.2y.net> X-Url: http://www.celabo.org/ User-Agent: Mutt/1.5.6i cc: freebsd-security@freebsd.org Subject: Re: portaudit 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: Wed, 17 Mar 2004 14:23:32 -0000 On Wed, Mar 17, 2004 at 02:00:51AM -0500, Peter C. Lai wrote: > Any reason why portaudit and its associated infrastructure was not announced to > this list or security-notifications? I recently discovered it, and discovered > the feature was added to bsd.port.mk in the beginning of feburary. Seeing as > the security officer apparently (without announcement) no longer issues > security notices (SNs) for ports, I am assuming that portaudit has replaced > SNs entirely, and that we should rely on that for ports operational security? > I'm not subscribed to -ports, -questions, or -current, which were apparently > where the portaudit introduction discussions took place. VuXML is the new mechanism for documenting security issues in ports. It has not been `announced' because it is still at an experimental stage. portaudit is one tool that reads the FreeBSD VuXML document, and is well- suited for automated checking. Cheers, -- Jacques Vidrine / nectar@celabo.org / jvidrine@verio.net / nectar@freebsd.org