From owner-freebsd-ports@FreeBSD.ORG  Tue Aug 30 08:17:16 2011
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@FreeBSD.org
Received: from mx2.freebsd.org (mx2.freebsd.org [IPv6:2001:4f8:fff6::35])
	by hub.freebsd.org (Postfix) with ESMTP id 63490106564A;
	Tue, 30 Aug 2011 08:17:16 +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 5590915405A;
	Tue, 30 Aug 2011 08:17:15 +0000 (UTC)
Message-ID: <4E5C9C8A.1010105@FreeBSD.org>
Date: Tue, 30 Aug 2011 01:17:14 -0700
From: Doug Barton <dougb@FreeBSD.org>
Organization: http://SupersetSolutions.com/
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
	rv:6.0) Gecko/20110824 Thunderbird/6.0
MIME-Version: 1.0
To: Mark Linimon <linimon@lonesome.com>
References: <4E5C79AF.6000408@FreeBSD.org> <20110830062541.GA5538@lonesome.com>
In-Reply-To: <20110830062541.GA5538@lonesome.com>
X-Enigmail-Version: undefined
OpenPGP: id=1A1ABC84
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Cc: secteam@FreeBSD.org,
	"freebsd-ports@FreeBSD.org" <freebsd-ports@FreeBSD.org>
Subject: Re: Why do we not mark vulnerable ports DEPRECATED?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 30 Aug 2011 08:17:16 -0000

On 08/29/2011 23:25, Mark Linimon wrote:
> So, the right answer may be "it depends".

I think my point is, it shouldn't. If a port is important/popular than
it will be quickly fixed. If not, it goes away. Everyone wins.


-- 

	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/