aboutsummaryrefslogtreecommitdiffstats
path: root/security/linux-f10-nss
diff options
context:
space:
mode:
authorbdrewery <bdrewery@FreeBSD.org>2014-09-20 22:13:41 +0800
committerbdrewery <bdrewery@FreeBSD.org>2014-09-20 22:13:41 +0800
commit7c055feed8932abcf8b7d869c805d1db6f78a8cd (patch)
tree2d5c47259c8d4aa302f8bd7e67668fbb2e2bf2e5 /security/linux-f10-nss
parent7466881b87cffd02378a9b77c1201f08df3bd626 (diff)
downloadfreebsd-ports-gnome-7c055feed8932abcf8b7d869c805d1db6f78a8cd.tar.gz
freebsd-ports-gnome-7c055feed8932abcf8b7d869c805d1db6f78a8cd.tar.zst
freebsd-ports-gnome-7c055feed8932abcf8b7d869c805d1db6f78a8cd.zip
Remove FORBIDDEN that references vuxml. We already have vuxml, portaudit
and pkg audit to handle this. The user can make their own decision as to whether or not they want to use vulnerable ports or packages. Using FORBIDDEN like this is not proper. It should only be used in extreme cases. In the meantime, the new Linux ports are being tested and should arrive soon. With hat: portmgr
Diffstat (limited to 'security/linux-f10-nss')
-rw-r--r--security/linux-f10-nss/Makefile2
1 files changed, 0 insertions, 2 deletions
diff --git a/security/linux-f10-nss/Makefile b/security/linux-f10-nss/Makefile
index 5f1ea1f74ab2..9c4943c9d0d1 100644
--- a/security/linux-f10-nss/Makefile
+++ b/security/linux-f10-nss/Makefile
@@ -12,8 +12,6 @@ DISTNAME= ${PORTNAME}-${PORTVERSION}-${RPMVERSION}
MAINTAINER= emulation@FreeBSD.org
COMMENT= Network Security Services (Linux Fedora 10)
-FORBIDDEN= http://www.freshports.org/vuxml.php?vid=9ccfee39-3c3b-11df-9edc-000f20797ede
-
CONFLICTS= linux-f8-nss-[0-9]*
ONLY_FOR_ARCHS= i386 amd64