From owner-freebsd-vuxml@FreeBSD.ORG Mon Jun 27 17:12:54 2005 Return-Path: X-Original-To: freebsd-vuxml@FreeBSD.org Delivered-To: freebsd-vuxml@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3987A16A41C for ; Mon, 27 Jun 2005 17:12:54 +0000 (GMT) (envelope-from dan@langille.org) Received: from bast.unixathome.org (bast.unixathome.org [66.11.174.150]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0E49743D4C for ; Mon, 27 Jun 2005 17:12:54 +0000 (GMT) (envelope-from dan@langille.org) Received: from wocker (wocker.unixathome.org [192.168.0.99]) by bast.unixathome.org (Postfix) with ESMTP id 0D4963D37 for ; Mon, 27 Jun 2005 13:13:08 -0400 (EDT) From: "Dan Langille" To: freebsd-vuxml@FreeBSD.org Date: Mon, 27 Jun 2005 13:12:53 -0400 MIME-Version: 1.0 Message-ID: <42BFFB55.20439.3BB92155@localhost> Priority: normal X-mailer: Pegasus Mail for Windows (4.21c) Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Content-description: Mail message body Cc: Subject: FreshPorts incorrectly reports vulnerabilities X-BeenThere: freebsd-vuxml@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Documenting security issues in VuXML List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Jun 2005 17:12:54 -0000 As documented at http://www.freshports.org/phorum/read.php?f=1&i=1025&t=1025 : I just noticed that FreshPorts is incorrectly reporting vulnerabilities under a very specific situation. I'm using http://www.freshports.org/lang/ruby18/ as an example. You will notice that the skull shown at the top of the page is faded/white. It should be black, to indicate a current vulnerability. http://www.freshports.org/images/freshports-vuln-top.jpg The skull listed under the first commit is black: http://www.freshports.org/images/freshports-vuln-commits.jpg I'll fix this bug ASAP. -- Dan Langille : http://www.langille.org/ BSDCan - The Technical BSD Conference - http://www.bsdcan.org/