From owner-freebsd-ports-bugs@freebsd.org  Thu Dec 24 14:41:11 2015
Return-Path: <owner-freebsd-ports-bugs@freebsd.org>
Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 05703A51E64
 for <freebsd-ports-bugs@mailman.ysv.freebsd.org>;
 Thu, 24 Dec 2015 14:41:11 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from kenobi.freebsd.org (kenobi.freebsd.org
 [IPv6:2001:1900:2254:206a::16:76])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id EAA5F1E4D
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 24 Dec 2015 14:41:10 +0000 (UTC)
 (envelope-from bugzilla-noreply@freebsd.org)
Received: from bugs.freebsd.org ([127.0.1.118])
 by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id tBOEfAbJ027215
 for <freebsd-ports-bugs@FreeBSD.org>; Thu, 24 Dec 2015 14:41:10 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-ports-bugs@FreeBSD.org
Subject: [Bug 203227] security/vuxml: Incorrectly flagging ruby20 as insecure
 (false positive)
Date: Thu, 24 Dec 2015 14:41:10 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: Ports & Packages
X-Bugzilla-Component: Ports Framework
X-Bugzilla-Version: Latest
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: terry-freebsd@glaver.org
X-Bugzilla-Status: Closed
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: sunpoet@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-203227-13-zEhYTT0Bj1@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-203227-13@https.bugs.freebsd.org/bugzilla/>
References: <bug-203227-13@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Dec 2015 14:41:11 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203227

--- Comment #24 from Terry Kennedy <terry-freebsd@glaver.org> ---
It seems that the updated vuln.xml didn't make it out of the ports tree and
into wherever "pkg audit -F" fetches it from, as it told me "vulnxml file
up-to-date". Manually copying vuln.xml from /usr/ports/security/vuxml/vuln.xml
to /var/db/pkg/vuln.xml stopped the complaint. Thanks!

-- 
You are receiving this mail because:
You are on the CC list for the bug.