FreeBSD ports which are currently marked forbidden
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: x11/nvidia-driver-173 forbidden because: vulnerable to denial of service or arbitrary code execution (CVE-2014-8298) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: x11/nvidia-driver-173 forbidden because: vulnerable to denial of service or arbitrary code execution (CVE-2014-8298) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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 portname: x11/nvidia-driver-173 forbidden because: vulnerable to denial of service or arbitrary code execution (CVE-2014-8298) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: x11/nvidia-driver-173 forbidden because: vulnerable to denial of service or arbitrary code execution (CVE-2014-8298) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: x11/nvidia-driver-173 forbidden because: vulnerable to denial of service or arbitrary code execution (CVE-2014-8298) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: x11/nvidia-driver-173 forbidden because: vulnerable to denial of service or arbitrary code execution (CVE-2014-8298) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: x11/nvidia-driver-173 forbidden because: vulnerable to denial of service or arbitrary code execution (CVE-2014-8298) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: x11/nvidia-driver-173 forbidden because: vulnerable to denial of service or arbitrary code execution (CVE-2014-8298) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: x11/nvidia-driver-173 forbidden because: vulnerable to denial of service or arbitrary code execution (CVE-2014-8298) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: net/ntp-devel forbidden because: http://www.kb.cert.org/vuls/id/852879 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-devel portname: x11/nvidia-driver-173 forbidden because: vulnerable to denial of service or arbitrary code execution (CVE-2014-8298) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11&portname=nvidia-driver-173 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: net/dante forbidden because: Building on 10+ triggers a nasty bug with unix domain sockets build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=dante portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: net/dante forbidden because: Building on 10+ triggers a nasty bug with unix domain sockets build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=dante portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: net/dante forbidden because: Building on 10+ triggers a nasty bug with unix domain sockets build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=dante portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: audio/linux-f10-nas-libs forbidden because: http://www.freshports.org/vuxml.php?vid=bf7912f5-c1a8-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-f10-nas-libs portname: net/dante forbidden because: Building on 10+ triggers a nasty bug with unix domain sockets build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=dante portname: net/ntp forbidden because: CVE-2013-5211 / VU#348126 - Please use net/ntp-devel, pending upstream stable branch update. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: audio/linux-f10-libaudiofile forbidden because: http://www.freshports.org/vuxml.php?vid=09f47c51-c1a6-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-f10-libaudiofile portname: audio/linux-f10-nas-libs forbidden because: http://www.freshports.org/vuxml.php?vid=bf7912f5-c1a8-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-f10-nas-libs portname: devel/linux-f10-dbus-glib forbidden because: http://www.freshports.org/vuxml.php?vid=77bb0541-c1aa-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-f10-dbus-glib portname: ftp/linux-f10-curl forbidden because: http://www.freshports.org/vuxml.php?vid=9aecb94c-c1ad-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ftp&portname=linux-f10-curl portname: graphics/linux-f10-png forbidden because: http://www.freshports.org/vuxml.php?vid=262b92fe-81c8-11e1-8899-001ec9578670 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-f10-png portname: graphics/linux-f10-tiff forbidden because: http://www.freshports.org/vuxml.php?vid=8816bf3a-7929-11df-bcce-0018f3e2eb82 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-f10-tiff portname: net-p2p/cdonkey forbidden because: distfile got re-rolled build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=cdonkey portname: net/dante forbidden because: Building on 10+ triggers a nasty bug with unix domain sockets build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=dante portname: net/linux-f10-openldap forbidden because: http://www.freshports.org/vuxml.php?vid=abad20bf-c1b4-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=linux-f10-openldap portname: net/ntp forbidden because: CVE-2013-5211 / VU#348126 - Please use net/ntp-devel, pending upstream stable branch update. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc portname: security/linux-f10-gnutls forbidden because: http://www.freshports.org/vuxml.php?vid=f645aa90-a3e8-11e3-a422-3c970e169bc2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=linux-f10-gnutls portname: security/linux-f10-libgcrypt forbidden because: http://www.freshports.org/vuxml.php?vid=689c2bf7-0701-11e3-9a25-002590860428 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=linux-f10-libgcrypt portname: security/linux-f10-nss forbidden because: http://www.freshports.org/vuxml.php?vid=9ccfee39-3c3b-11df-9edc-000f20797ede build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=linux-f10-nss portname: security/linux-f10-openssl forbidden because: http://www.freshports.org/vuxml.php?vid=2ecb7b20-d97e-11e0-b2e2-00215c6a37bb|82b55df8-4d5a-11de-8811-0030843d3802 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=linux-f10-openssl portname: textproc/linux-f10-expat forbidden because: http://www.freshports.org/vuxml.php?vid=5f030587-e39a-11de-881e-001aa0166822 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=linux-f10-expat portname: textproc/linux-f10-libxml2 forbidden because: ht
FreeBSD ports which are currently marked forbidden
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: audio/linux-f10-libaudiofile forbidden because: http://www.freshports.org/vuxml.php?vid=09f47c51-c1a6-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-f10-libaudiofile portname: audio/linux-f10-nas-libs forbidden because: http://www.freshports.org/vuxml.php?vid=bf7912f5-c1a8-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-f10-nas-libs portname: chinese/acroread8-zh_CN forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=acroread8-zh_CN portname: chinese/acroread8-zh_TW forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=acroread8-zh_TW portname: devel/linux-f10-dbus-glib forbidden because: http://www.freshports.org/vuxml.php?vid=77bb0541-c1aa-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-f10-dbus-glib portname: french/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=french&portname=acroread8 portname: french/acroread9 forbidden because: No longer maintained upstream since 2013-06-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=french&portname=acroread9 portname: ftp/linux-f10-curl forbidden because: http://www.freshports.org/vuxml.php?vid=9aecb94c-c1ad-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ftp&portname=linux-f10-curl portname: german/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=german&portname=acroread8 portname: german/acroread9 forbidden because: No longer maintained upstream since 2013-06-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=german&portname=acroread9 portname: graphics/linux-f10-png forbidden because: http://www.freshports.org/vuxml.php?vid=262b92fe-81c8-11e1-8899-001ec9578670 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-f10-png portname: graphics/linux-f10-tiff forbidden because: http://www.freshports.org/vuxml.php?vid=8816bf3a-7929-11df-bcce-0018f3e2eb82 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-f10-tiff portname: japanese/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=acroread8 portname: japanese/acroread9 forbidden because: No longer maintained upstream since 2013-06-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=acroread9 portname: korean/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=korean&portname=acroread8 portname: net-p2p/cdonkey forbidden because: distfile got re-rolled build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=cdonkey portname: net/dante forbidden because: Building on 10+ triggers a nasty bug with unix domain sockets build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=dante portname: net/linux-f10-openldap forbidden because: http://www.freshports.org/vuxml.php?vid=abad20bf-c1b4-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=l
FreeBSD ports which are currently marked forbidden
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: audio/linux-f10-libaudiofile forbidden because: http://www.freshports.org/vuxml.php?vid=09f47c51-c1a6-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-f10-libaudiofile portname: audio/linux-f10-nas-libs forbidden because: http://www.freshports.org/vuxml.php?vid=bf7912f5-c1a8-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-f10-nas-libs portname: chinese/acroread8-zh_CN forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=acroread8-zh_CN portname: chinese/acroread8-zh_TW forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=chinese&portname=acroread8-zh_TW portname: devel/linux-f10-dbus-glib forbidden because: http://www.freshports.org/vuxml.php?vid=77bb0541-c1aa-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-f10-dbus-glib portname: french/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=french&portname=acroread8 portname: french/acroread9 forbidden because: No longer maintained upstream since 2013-06-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=french&portname=acroread9 portname: ftp/linux-f10-curl forbidden because: http://www.freshports.org/vuxml.php?vid=9aecb94c-c1ad-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ftp&portname=linux-f10-curl portname: german/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=german&portname=acroread8 portname: german/acroread9 forbidden because: No longer maintained upstream since 2013-06-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=german&portname=acroread9 portname: graphics/linux-f10-png forbidden because: http://www.freshports.org/vuxml.php?vid=262b92fe-81c8-11e1-8899-001ec9578670 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-f10-png portname: graphics/linux-f10-tiff forbidden because: http://www.freshports.org/vuxml.php?vid=8816bf3a-7929-11df-bcce-0018f3e2eb82 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-f10-tiff portname: japanese/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=acroread8 portname: japanese/acroread9 forbidden because: No longer maintained upstream since 2013-06-26 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=acroread9 portname: korean/acroread8 forbidden because: No longer maintained upstream since 2011-11-03 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=korean&portname=acroread8 portname: net/dante forbidden because: Building on 10+ triggers a nasty bug with unix domain sockets build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=dante portname: net/linux-f10-openldap forbidden because: http://www.freshports.org/vuxml.php?vid=abad20bf-c1b4-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=linux-f10-openldap portname: net/ntp forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp
FreeBSD ports which are currently marked forbidden
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: audio/linux-f10-libaudiofile forbidden because: http://www.freshports.org/vuxml.php?vid=09f47c51-c1a6-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-f10-libaudiofile portname: audio/linux-f10-nas-libs forbidden because: http://www.freshports.org/vuxml.php?vid=bf7912f5-c1a8-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=audio&portname=linux-f10-nas-libs portname: devel/linux-f10-dbus-glib forbidden because: http://www.freshports.org/vuxml.php?vid=77bb0541-c1aa-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=linux-f10-dbus-glib portname: ftp/linux-f10-curl forbidden because: http://www.freshports.org/vuxml.php?vid=9aecb94c-c1ad-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ftp&portname=linux-f10-curl portname: graphics/linux-f10-png forbidden because: http://www.freshports.org/vuxml.php?vid=262b92fe-81c8-11e1-8899-001ec9578670 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-f10-png portname: graphics/linux-f10-tiff forbidden because: http://www.freshports.org/vuxml.php?vid=8816bf3a-7929-11df-bcce-0018f3e2eb82 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-f10-tiff portname: net/linux-f10-openldap forbidden because: http://www.freshports.org/vuxml.php?vid=abad20bf-c1b4-11e3-a5ac-001b21614864 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=linux-f10-openldap portname: net/ntp forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc portname: security/linux-f10-gnutls forbidden because: http://www.freshports.org/vuxml.php?vid=f645aa90-a3e8-11e3-a422-3c970e169bc2 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=linux-f10-gnutls portname: security/linux-f10-libgcrypt forbidden because: http://www.freshports.org/vuxml.php?vid=689c2bf7-0701-11e3-9a25-002590860428 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=linux-f10-libgcrypt portname: security/linux-f10-nss forbidden because: http://www.freshports.org/vuxml.php?vid=9ccfee39-3c3b-11df-9edc-000f20797ede build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=linux-f10-nss portname: textproc/linux-f10-expat forbidden because: http://www.freshports.org/vuxml.php?vid=5f030587-e39a-11de-881e-001aa0166822 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=linux-f10-expat portname: textproc/linux-f10-libxml2 forbidden because: http://www.freshports.org/vuxml.php?vid=57f1a624-6197-11e1-b98c-bcaec565249c|7be92050-a450-11e2-9898-001060e06fd4|b8ae4659-a0da-11e1-a294-bcaec565249c build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=textproc&portname=linux-f10-libxml2 portname: www/linux-opera forbidden because: http://www.freshports.org/vuxml.php?vid=0925716f-34e2-11e2-aa75-003067c2616f|38daea4f-2851-11e2-9483-14dae938ec40|85f33a8d-492f-11e2-aa75-003067c2616f|cebed39d-9e6f-11e2-b3f5-003067c2616f|ea0f45e2-6c4b-11e2-98d9-003067c2616f build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-opera ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "fr
FreeBSD ports which are currently marked forbidden
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: net/ntp forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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/bugzilla40 forbidden because: no upstream fixes for CVE-2014-1517, see http://www.bugzilla.org/security/4.0.11/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=bugzilla40 portname: devel/bugzilla42 forbidden because: no upstream fixes for CVE-2014-1517, see http://www.bugzilla.org/security/4.0.11/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=bugzilla42 portname: net/ntp forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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/bugzilla40 forbidden because: no upstream fixes for CVE-2014-1517, see http://www.bugzilla.org/security/4.0.11/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=bugzilla40 portname: devel/bugzilla42 forbidden because: no upstream fixes for CVE-2014-1517, see http://www.bugzilla.org/security/4.0.11/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=bugzilla42 portname: net/ntp forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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/bugzilla40 forbidden because: no upstream fixes for CVE-2014-1517, see http://www.bugzilla.org/security/4.0.11/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=bugzilla40 portname: devel/bugzilla42 forbidden because: no upstream fixes for CVE-2014-1517, see http://www.bugzilla.org/security/4.0.11/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=bugzilla42 portname: net/ntp forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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/bugzilla40 forbidden because: no upstream fixes for CVE-2014-1517, see http://www.bugzilla.org/security/4.0.11/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=bugzilla40 portname: devel/bugzilla42 forbidden because: no upstream fixes for CVE-2014-1517, see http://www.bugzilla.org/security/4.0.11/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=bugzilla42 portname: net/ntp forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc portname: www/openx forbidden because: CVE-2013-7149 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=openx ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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/bugzilla40 forbidden because: no upstream fixes for CVE-2014-1517, see http://www.bugzilla.org/security/4.0.11/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=bugzilla40 portname: devel/bugzilla42 forbidden because: no upstream fixes for CVE-2014-1517, see http://www.bugzilla.org/security/4.0.11/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=bugzilla42 portname: net/asterisk14 forbidden because: Unsupported for so long that this version is not listed in security advisories build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=asterisk14 portname: net/ntp forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc portname: www/openx forbidden because: CVE-2013-7149 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=openx ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: multimedia/xmms forbidden because: Vulnerable: CVE-2007-0653 CVE-2007-0654 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=multimedia&portname=xmms portname: net/asterisk14 forbidden because: Unsupported for so long that this version is not listed in security advisories build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=asterisk14 portname: net/ntp forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp portname: net/ntp-rc forbidden because: CVE-2013-5211 / VU build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=ntp-rc portname: www/openx forbidden because: CVE-2013-7149 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=openx ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: www/openx forbidden because: CVE-2013-7149 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=openx ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: www/openx forbidden because: CVE-2013-7149 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=openx ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: lang/ruby18 forbidden because: Vulernerable, http://vuxml.org/freebsd/ebd877b9-7ef4-4375-b1fd-c67780581898.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=ruby18 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: lang/ruby18 forbidden because: Vulernerable, http://vuxml.org/freebsd/ebd877b9-7ef4-4375-b1fd-c67780581898.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=ruby18 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: www/linux-flashplugin9 forbidden because: CVE-2010-1297 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-flashplugin9 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: www/linux-flashplugin9 forbidden because: CVE-2010-1297 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-flashplugin9 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: www/linux-flashplugin9 forbidden because: CVE-2010-1297 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-flashplugin9 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: www/linux-flashplugin9 forbidden because: CVE-2010-1297 build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.10.20120608131052/linux-flashplugin-9.0r289_1.log (_Jun_13_10:34:28_UTC_2012) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-flashplugin9 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: shells/rssh forbidden because: http://www.vuxml.org/freebsd/65b25acc-e63b-11e1-b81c-001b77d09812.html (vulnerability) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=rssh portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: shells/rssh forbidden because: http://www.vuxml.org/freebsd/65b25acc-e63b-11e1-b81c-001b77d09812.html (vulnerability) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=rssh portname: www/opera forbidden because: http://www.opera.com/support/kb/view/1030/ http://www.opera.com/support/kb/view/1031/ http://www.opera.com/support/kb/view/1033/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=opera portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: shells/rssh forbidden because: http://www.vuxml.org/freebsd/65b25acc-e63b-11e1-b81c-001b77d09812.html (vulnerability) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=rssh portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: lang/eperl forbidden because: Vulnerable since 2001-06-21, http://portaudit.freebsd.org/73efb1b7-07ec-11e2-a391-000c29033c32.html build errors: http://pointyhat.FreeBSD.org/errorlogs/sparc64-errorlogs/e.7.20101015091133/eperl-2.2.14_3.log.bz2 (_Jul_31_06:17:35_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=lang&portname=eperl portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: shells/rssh forbidden because: http://www.vuxml.org/freebsd/65b25acc-e63b-11e1-b81c-001b77d09812.html (vulnerability) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=rssh portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: shells/rssh forbidden because: http://www.vuxml.org/freebsd/65b25acc-e63b-11e1-b81c-001b77d09812.html (vulnerability) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=rssh portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: shells/rssh forbidden because: http://www.vuxml.org/freebsd/65b25acc-e63b-11e1-b81c-001b77d09812.html (vulnerability) build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=shells&portname=rssh portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: security/sudosh3 forbidden because: Secunia Advisory SA38292, ISS X-Force sudosh-replay-bo (55903), replay() function buffer overflow. build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=sudosh3 portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: mail/sympa5 forbidden because: Multiple vulnerabilities have been discovered in Sympa archive management that allow to skip the scenario-based authorization mechanisms. http://www.sympa.org/security_advisories build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=sympa5 portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: mail/squirreloutlook forbidden because: Based on a vulnerable version of mail/squirrelmail build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=squirreloutlook portname: mail/sympa5 forbidden because: Multiple vulnerabilities have been discovered in Sympa archive management that allow to skip the scenario-based authorization mechanisms. http://www.sympa.org/security_advisories build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=sympa5 portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: mail/sympa5 forbidden because: Multiple vulnerabilities have been discovered in Sympa archive management that allow to skip the scenario-based authorization mechanisms. http://www.sympa.org/security_advisories build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=mail&portname=sympa5 portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/postgresql82-client forbidden because: Vulnerable http://www.postgresql.org/about/news/1377/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql82-client portname: databases/postgresql82-contrib forbidden because: Vulnerable http://www.postgresql.org/about/news/1377/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql82-contrib portname: databases/postgresql82-server forbidden because: Vulnerable http://www.postgresql.org/about/news/1377/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql82-server portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/postgresql82-client forbidden because: Vulnerable http://www.postgresql.org/about/news/1377/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql82-client portname: databases/postgresql82-contrib forbidden because: Vulnerable http://www.postgresql.org/about/news/1377/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql82-contrib portname: databases/postgresql82-server forbidden because: Vulnerable http://www.postgresql.org/about/news/1377/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql82-server portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/postgresql82-client forbidden because: Vulnerable http://www.postgresql.org/about/news/1377/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql82-client portname: databases/postgresql82-contrib forbidden because: Vulnerable http://www.postgresql.org/about/news/1377/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql82-contrib portname: databases/postgresql82-server forbidden because: Vulnerable http://www.postgresql.org/about/news/1377/ build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=postgresql82-server portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/linux-f10-flashplugin10 forbidden because: insecure version - use flashplugin11 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-f10-flashplugin10 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/apache13 forbidden because: CVE-2011-3368, no patches against this issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=apache13 portname: www/apache13+ipv6 forbidden because: CVE-2011-3368, no patches against this issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=apache13%2Bipv6 portname: www/apache13-ssl forbidden because: CVE-2011-3368, no patches against this issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=apache13-ssl portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: www/apache13 forbidden because: CVE-2011-3368, no patches against this issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=apache13 portname: www/apache13+ipv6 forbidden because: CVE-2011-3368, no patches against this issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=apache13%2Bipv6 portname: www/apache13-ssl forbidden because: CVE-2011-3368, no patches against this issue build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=apache13-ssl portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: sysutils/syslog-ng1 forbidden because: Vulnerable since 2008-11-18, http://portaudit.freebsd.org/75f2382e-b586-11dd-95f9-00e0815b8da8.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=syslog-ng1 portname: x11-toolkits/linux-pango forbidden because: Vulnerable since 2009-05-13, http://portaudit.freebsd.org/4b172278-3f46-11de-becb-001cc0377035.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=x11-toolkits&portname=linux-pango ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: archivers/pecl-phar forbidden because: Vulnerable since 2011-01-13, http://portaudit.freebsd.org/da3d381b-0ee6-11e0-becc-0022156e8794.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=archivers&portname=pecl-phar portname: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: databases/mysql323-client forbidden because: Vulnerable since 2006-10-29, http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysql323-client portname: databases/mysql323-scripts forbidden because: Vulnerable since 2006-10-29, http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysql323-scripts portname: databases/mysql323-server forbidden because: Vulnerable since 2006-10-29, http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysql323-server portname: databases/mysql40-client forbidden because: Vulnerable since 2006-10-29, http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysql40-client portname: databases/mysql40-scripts forbidden because: Vulnerable since 2006-10-29, http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysql40-scripts portname: databases/mysql40-server forbidden because: Vulnerable since 2006-10-29, http://portaudit.freebsd.org/a0e92718-6603-11db-ab90-000e35fd8194.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=mysql40-server portname: devel/libsoup22 forbidden because: Vulnerable since 2011-07-28, http://portaudit.freebsd.org/30cb4522-b94d-11e0-8182-485d60cb5385.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=devel&portname=libsoup22 portname: dns/bind9-sdb-ldap forbidden because: Vulnerable since 2011-06-04, http://portaudit.freebsd.org/1e1421f0-8d6f-11e0-89b4-001ec9578670.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=bind9-sdb-ldap portname: dns/bind9-sdb-postgresql forbidden because: Vulnerable since 2011-06-04, http://portaudit.freebsd.org/1e1421f0-8d6f-11e0-89b4-001ec9578670.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=dns&portname=bind9-sdb-postgresql portname: ftp/wgetpro forbidden because: Vulnerable since 2004-12-14, http://portaudit.freebsd.org/06f142ff-4df3-11d9-a9e7-0001020eed82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=ftp&portname=wgetpro portname: games/quake2forge forbidden because: Vulnerable since 2005-01-21, http://portaudit.freebsd.org/2c25e762-6bb9-11d9-93db-000a95bc6fae.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=games&portname=quake2forge portname: graphics/linux-tiff forbidden because: Vulnerable since 2004-10-13, http://portaudit.freebsd.org/8816bf3a-7929-11df-bcce-0018f3e2eb82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=graphics&portname=linux-tiff portname: japanese/mutt forbidden because: Vulnerable since 2007-07-29, http://portaudit.freebsd.org/863f95d3-3df1-11dc-b3d3-0016179b2dd5.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=japanese&portname=mutt portname: net-mgmt/nagios2 fo
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: math/mupad forbidden because: Relies on xpm, vulnerable since 2004-09-15, http://portaudit.freebsd.org/ef253f8b-0727-11d9-b45d-000c41e2cdad.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=mupad portname: net-p2p/torrentflux forbidden because: Vulnerable since 2006-10-07, http://portaudit.freebsd.org/72f21372-55e4-11db-a5ae-00508d6a62df.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=torrentflux portname: net/tptest forbidden because: Vulnerable since 2009-12-17, http://portaudit.freebsd.org/5486669e-ea9f-11de-bd9c-00215c6a37bb.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=tptest portname: security/cfs forbidden because: Buffer overflows allow remote attackers to cause DoS / execute arbitrary code build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=cfs portname: security/pgp6 forbidden because: Vulnerable since 2005-07-31, http://portaudit.freebsd.org/8375a73f-01bf-11da-bc08-0001020eed82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=pgp6 portname: www/plone forbidden because: Vulnerable since 2011-02-10, http://portaudit.freebsd.org/7c492ea2-3566-11e0-8e81-0022190034c0.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=plone portname: www/pyblosxom forbidden because: Vulnerable since 2009-02-11 http://portaudit.freebsd.org/b07f3254-f83a-11dd-85a4-ea653f0746ab.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=pyblosxom portname: www/rt36 forbidden because: Vulnerable since 2009-12-09, http://portaudit.freebsd.org/714c1406-e4cf-11de-883a-003048590f9e.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt36 portname: www/seamonkey2 forbidden because: several security vulnerabilities build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=seamonkey2 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: math/mupad forbidden because: Relies on xpm, vulnerable since 2004-09-15, http://portaudit.freebsd.org/ef253f8b-0727-11d9-b45d-000c41e2cdad.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=math&portname=mupad portname: net-p2p/torrentflux forbidden because: Vulnerable since 2006-10-07, http://portaudit.freebsd.org/72f21372-55e4-11db-a5ae-00508d6a62df.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net-p2p&portname=torrentflux portname: net/tptest forbidden because: Vulnerable since 2009-12-17, http://portaudit.freebsd.org/5486669e-ea9f-11de-bd9c-00215c6a37bb.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=net&portname=tptest portname: security/cfs forbidden because: Buffer overflows allow remote attackers to cause DoS / execute arbitrary code build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=cfs portname: security/pgp6 forbidden because: Vulnerable since 2005-07-31, http://portaudit.freebsd.org/8375a73f-01bf-11da-bc08-0001020eed82.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=security&portname=pgp6 portname: sysutils/dtc forbidden because: Many security issues, see http://bugs.freebsd.org/159736 build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=sysutils&portname=dtc portname: www/plone forbidden because: Vulnerable since 2011-02-10, http://portaudit.freebsd.org/7c492ea2-3566-11e0-8e81-0022190034c0.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=plone portname: www/pyblosxom forbidden because: Vulnerable since 2009-02-11 http://portaudit.freebsd.org/b07f3254-f83a-11dd-85a4-ea653f0746ab.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=pyblosxom portname: www/rt36 forbidden because: Vulnerable since 2009-12-09, http://portaudit.freebsd.org/714c1406-e4cf-11de-883a-003048590f9e.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=rt36 portname: www/seamonkey2 forbidden because: several security vulnerabilities build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=seamonkey2 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: www/chromium forbidden because: several security vulnerabilities build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=chromium portname: www/spip forbidden because: Security: http://www.spip-contrib.net/SPIP-2-1-8-corrige-une-importante-faille-de-securite build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=spip ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD ports which are currently marked forbidden
On Fri, Jan 07, 2011 at 10:29:42PM +0100, olli hauer wrote: > Ups, I thought freefall runs the gnats4 port. Nope. Never got updated. The problem is that we have people that have local copies of the repo, and we would need to get them to move all at the same time. (portsmon has a shim to do this, internally it uses the gnats4 format.) I just never got around to doing the coordination with those folks. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD ports which are currently marked forbidden
On 2011-01-07 22:16, Mark Linimon wrote: > On Fri, Jan 07, 2011 at 04:18:49PM +0100, Olli Hauer wrote: >> I wonder about the old gants port. >> Do we use parts of this port somewhere (OS/freefall...)? > > freefall, yep. It's our main GNATS installation. > > mcl Ups, I thought freefall runs the gnats4 port. ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD ports which are currently marked forbidden
On Fri, Jan 07, 2011 at 04:18:49PM +0100, Olli Hauer wrote: > I wonder about the old gants port. > Do we use parts of this port somewhere (OS/freefall...)? freefall, yep. It's our main GNATS installation. mcl ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: FreeBSD ports which are currently marked forbidden
On 2011-01-07 08:29, lini...@freebsd.org wrote: > 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: databases/gnats > forbidden because: Security issues > build errors: none. > overview: > http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats > I wonder about the old gants port. Do we use parts of this port somewhere (OS/freefall...)? The port is now marked since nearly 7 years as forbidden/broken, was scheduled to expire (2004-08-20) which was removed 5 years ago with the following comment. - Remove expiration date, this port is not going away yet ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: www/chromium forbidden because: several security vulnerabilities build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=chromium ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: www/chromium forbidden because: several security vulnerabilities build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.7.20101201194911/chromium-6.0.472.63.log.bz2 (_Dec__3_11:19:15_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=chromium ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: www/chromium forbidden because: several security vulnerabilities build errors: http://pointyhat.freebsd.org/errorlogs/i386-errorlogs/e.8.20101128220208/chromium-6.0.472.63.log (_Dec__1_01:10:38_UTC_2010) overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=chromium ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: irc/kvirc forbidden because: multiple vulnerabilities build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=irc&portname=kvirc portname: irc/kvirc-devel forbidden because: multiple vulnerabilities build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=irc&portname=kvirc-devel portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=firefox ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=firefox ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=firefox ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=firefox ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=firefox portname: www/linux-firefox-devel forbidden because: Security issues http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e16.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel portname: www/neon26 forbidden because: see CVE-2009-2474 please use neon28 or neon29 instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=neon26 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=firefox portname: www/linux-firefox-devel forbidden because: Security issues http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e16.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel portname: www/neon26 forbidden because: see CVE-2009-2474 please use neon28 or neon29 instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=neon26 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=firefox portname: www/linux-firefox-devel forbidden because: Security issues http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e16.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel portname: www/neon26 forbidden because: see CVE-2009-2474 please use neon28 or neon29 instead build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=neon26 ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
FreeBSD ports which are currently marked forbidden
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: databases/gnats forbidden because: Security issues build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=databases&portname=gnats portname: misc/compat3x forbidden because: FreeBSD-SA-03:05.xdr, FreeBSD-SA-03:08.realpath - not fixed / no lib available build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=misc&portname=compat3x portname: www/firefox forbidden because: too many security issues http://www.vuxml.org/freebsd/922d2398-9e2d-11de-a998-0030843d3802.html http://www.vuxml.org/freebsd/49e8f2ee-8147-11de-a994-0030843d3802.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=firefox portname: www/linux-firefox-devel forbidden because: Security issues http://www.vuxml.org/freebsd/f29fea8f-b19f-11dd-a55e-00163e16.html build errors: none. overview: http://portsmon.FreeBSD.org/portoverview.py?category=www&portname=linux-firefox-devel ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"