From owner-freebsd-ports@FreeBSD.ORG  Tue Apr  7 08:29:48 2015
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: ports@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 66A7A7BA
 for <ports@freebsd.org>; Tue,  7 Apr 2015 08:29:48 +0000 (UTC)
Received: from portsmon.freebsd.org (portsmon.freebsd.org
 [IPv6:2001:1900:2254:206a::50:3])
 (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 576B98A6
 for <ports@freebsd.org>; Tue,  7 Apr 2015 08:29:48 +0000 (UTC)
Received: from portsmon.freebsd.org ([127.0.1.104])
 by portsmon.freebsd.org (8.14.9/8.14.9) with ESMTP id t378TmGT014121
 for <ports@freebsd.org>; Tue, 7 Apr 2015 08:29:48 GMT
 (envelope-from linimon@FreeBSD.org)
Date: Tue, 7 Apr 2015 08:29:48 GMT
Message-Id: <201504070829.t378TmGT014121@portsmon.freebsd.org>
From: linimon@FreeBSD.org
To: ports@freebsd.org
Reply-To: portmgr-feedback@FreeBSD.org
Subject: FreeBSD unmaintained ports which are currently marked forbidden
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.18-1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/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, 07 Apr 2015 08:29:48 -0000

As part of an ongoing effort to reduce the number of problems in the
FreeBSD ports system, we periodically notify users about
ports that are marked as "forbidden" in their Makefiles.  Often,
these ports are so marked due to security concerns, such as known
exploits.

An overview of each port, including errors seen on the build farm,
is included below.

portname:           devel/cross-binutils
forbidden because:  Multiple vulnerbilities parsing PE and ihex files
build errors:       none.
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=cross-binutils


portname:           devel/mingw64-binutils
forbidden because:  Multiple vulnerbilities parsing PE and ihex files
build errors:
http://beefy2.isc.freebsd.org/bulk/head-amd64-default/2015-03-19_00h08m00s/logs/errors/x86_64-pc-mingw32-binutils-2.23.2_1.log
overview:           http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=mingw64-binutils