From owner-cvs-ports@FreeBSD.ORG Mon Sep 5 10:09:27 2011 Return-Path: Delivered-To: cvs-ports@FreeBSD.org Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35]) by hub.freebsd.org (Postfix) with ESMTP id 219771065672; Mon, 5 Sep 2011 10:09:27 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from 172-17-198-245.globalsuite.net (hub.freebsd.org [IPv6:2001:4f8:fff6::36]) by mx2.freebsd.org (Postfix) with ESMTP id B1E8C14D96B; Mon, 5 Sep 2011 10:09:25 +0000 (UTC) Message-ID: <4E649FD4.6090908@FreeBSD.org> Date: Mon, 05 Sep 2011 03:09:24 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:6.0.1) Gecko/20110901 Thunderbird/6.0.1 MIME-Version: 1.0 To: Thierry Thomas References: <201109041252.p84CqgaG049222@repoman.freebsd.org> <4E640D06.6060605@FreeBSD.org> In-Reply-To: <4E640D06.6060605@FreeBSD.org> X-Enigmail-Version: undefined OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: cvs-ports@FreeBSD.org, cvs-all@FreeBSD.org, ports-committers@FreeBSD.org Subject: Re: cvs commit: ports/textproc/fy-aspell Makefile ports/textproc/ml-aspell Makefile ports/textproc/tk-aspell Makefile X-BeenThere: cvs-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: CVS commit messages for the ports tree List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Sep 2011 10:09:27 -0000 So, here is what happened. I naively assumed that all of the entries that go into creating the auditfile are located in security/vuxml/vuln.xml. It turns out that is not true. There is a bunch of stuff in ports-mgmt/portaudit-db/database that gets appended to the auditfile. (Thanks to flo, simon, and remko for helping me get sorted out.) The entry that incorrectly matched the aspell dictionaries was there. With Simon's permission I removed it, and now none of the aspell ports are labelled vulnerable. My apologies if I implied in any way that you were falling down on the job by not fixing this yourself. :-/ Doug -- Nothin' ever doesn't change, but nothin' changes much. -- OK Go Breadth of IT experience, and depth of knowledge in the DNS. Yours for the right price. :) http://SupersetSolutions.com/