Remove expired ports:
20140130 multimedia/kino: Not developed since 2009, declared dead 05.08.2013 on
there website.
2014-01-31 x11-drivers/xf86-video-imstt: Broken, unsupported and unmaintained
upstream.
2014-01-31 x11-drivers/xf86-video-via: Broken, not supported upstream.
2014-01-31 multimedia/vdr-plugin-softdevice: Broken after ffmpeg update (not
sure it ever worked)
2014-01-31 sysutils/mbmon: Use sysutils/xmbmon instead. This port will be
removed soon
2014-01-31 dns/bind96: EOL in January 2014, consider moving to Bind 9.8 or 9.9
2014-01-31 x11-drivers/xf86-video-nouveau: Not supported, missing kernel
support. use the nvidia driver.

Security update to fix CVE-2014-0591 as reported at
https://kb.isc.org/article/AA-01078/74/

9.9.4 -> 9.9.4-P2
9.8.6 -> 9.8.6-P2
9.6-ESV-R10 -> 9.6-ESV-R10-P2

Security:	CVE-2014-0591 Remote DOS

There's always a default value for named_conf now, so no need to
check for it, and espcially not for a wrong value.

Noticed by:	Stefan Bethke <stb@lassitu.de>
Approved by:	mat (maintainer)

Add the DOCS option to OPTIONS_DEFAULT.

Hand the BIND ports to a new volunteer.

bind(96,98,99): Couple OSVERSION with OPSYS

OSVERSION is platform-specific and must be used with OPSYS.

Approved by:	maintainer (erwin)

To prevent fallout of lowering __FreeBSD_version in releng/10.0 branch,
adjust OSVERSION evaluation in ports that specifically use '100050N'.

Approved by:	affected maintainers (implicit)
Sponsored by:	The FreeBSD Foundation

Install named.conf as named.conf.sample and don't overwrite on upgrade

Bullet hole in foot:	joeld
Pointy hat:		erwin

- Respect BIND_DESTETC and PREFIX

Submitted by:	sunpoet (myself)
Approved by:	erwin (maintainer)

Fix startup script.

PR:		184159 [1]
Submitted by:	Pawel Biernacki <pawel.biernacki@gmail.com> [1],
		Trond Endrestoel <Trond.Endrestol@ximalas.info> (private email)

Support FreeBSD 10.0.

On FreeBSD 10.0, all configuration is installed under
/usr/local/etc/namedb and installs its own rc script in
$PREFIX, which no longer support chroot installations.

LINKS and REPLACE_BASE options are not supported on 10.0
for obvious reasons.

Note for FreeBSD 9.x and earlier users, LINKS is no longer
the default option, though still supported.

An UPDATING entry will follow after bind99 is fixed
as well.

Drop support for REPLACE_BIND option after BIND was removed from base,
there's nothing to replace.

Add NO_STAGE all over the place in preparation for the staging support (cat:
dns)

Update to 9.6-ESV-R10

Security Fixes

   Prevents exploitation of a runtime_check which can crash named
   when satisfying a recursive query for particular malformed zones.
   (CVE-2013-3919) [RT #33690]

Feature Changes

   rndc status now also shows the build-id. [RT #20422]

   Improved OPT pseudo-record processing to make it easier to support
   new EDNS options. [RT #34414]

. introduce ICONV_CONFIGURE_BASE variable at Mk/Uses/iconv.mk. It's value is
  "--with-libiconv=${LOCALBASE}" at systems pre OSVERSION 100043 and "" (null)
  otherwise;
. convert all ports which has CONFIGURE_ARGS=--with-libiconv=${LOCALBASE}.

Approved by:	portmgr (bapt, implicit)

Update to 9.6-ESV-R9-P1

Security Fixes

   Prevents exploitation of a runtime_check which can crash named
   when satisfying a recursive query for particular malformed zones.
   (CVE-2013-3919) [RT #33690]

   Prevents a named assert (crash) when validating caused by using
   "Bad cache" data before it has been initialized. [CVE-2012-3817]
   [RT #30025]

   A condition has been corrected where improper handling of
   zero-length RDATA could cause undesirable behavior, including
   termination of the named process. [CVE-2012-1667] [RT #29644]

See release notes for further features and bug fixes:
https://kb.isc.org/article/AA-00968/0/BIND-9.6-ESV-R9-P1-Release-Notes.html

Security:	CVE-2013-3919
		CVE-2012-3817
		CVE-2012-1667

Update to 9.6-ESV-R9 and extend the EOL to January 2014

Make pkg-message and pkg-install a local file to the bind96
port and not include the one from the deprecated bind97 port, which is
to be removed.

Add a gentle reminder that Bind 9.6 will be EOL shortly
and recommend planning to move to newer versions before
June 2013.

http://www.isc.org/software/bind/versions

Add LICENSE.

- Use new OPTIONS_GROUP for DLZ options.[1]
- This also allows more than one DLZ option
  to be set.[2]

Submitted by:	bapt [1] (as RADIO)
Suggested by:	az [2] (thus GROUP instead)

Improve the SSL option description

Submitted by:	Kazunori Fujiwara <fujiwara@jprs.co.jp>
Feature safe:	yes

Remove gpg signature checking that in itself does not
provide any additional security.

Feature safe:	yes

- Update CONFLICTS
- Fix a typo in the OPTIONSNG conversion
- Add FIXED_RRSET option
- Add RPZ options (9.8 and 9.8 only)

PR:		172586
Submitted by:	Craig Leres <leres@ee.lbl.gov>
Feature safe:	yes

Reduce lenght of the option description for DLZ_MYSQL to
avoid problems with the older dialog(1) on FreeBSD 8.x

Noticed by:	Terry Kennedy <terry@tmk.com>
Feature safe:	yes

- Convert to OPTIONSNG
- Turn on IPv6 support by default

Feature safe:	yes

Update to 9.6-ESV-R8

Feature safe:	yes

Upgrade to the latest BIND patch level:

A deliberately constructed combination of records could cause named
to hang while populating the additional section of a response.

Security:	 
http://www.vuxml.org/freebsd/57a700f9-12c0-11e2-9f86-001d923933b6.html

Take maintainership of the BIND ports while I'm working on the latest
security releases.

Throw my ports back in the pool, and make my intentions clear for the
various ports that I've created.

I bid fond fare well
A chapter closes for me
What opens for you?

Upgrade to the latest BIND patch level:

Prevents a crash when queried for a record whose RDATA exceeds
65535 bytes.

Prevents a crash when validating caused by using "Bad cache" data
before it has been initialized.

ISC_QUEUE handling for recursive clients was updated to address
a race condition that could cause a memory leak. This rarely
occurred with UDP clients, but could be a significant problem
for a server handling a steady rate of TCP queries.

A condition has been corrected where improper handling of
zero-length RDATA could cause undesirable behavior, including
termination of the named process.

For more information: https://kb.isc.org/article/AA-00788

Heavy DNSSEC Validation Load Can Cause a "Bad Cache" Assertion Failure
in BIND9

High numbers of queries with DNSSEC validation enabled can cause an
assertion failure in named, caused by using a "bad cache" data structure
before it has been initialized.

CVE: CVE-2012-3817
Posting date: 24 July, 2012

Upgrade to 9.6-ESV-R7-P1, 9.7.6-P1, 9.8.3-P1, and 9.9.1-P1, the latest
from ISC. These patched versions contain a critical bugfix:

  Processing of DNS resource records where the rdata field is zero length
  may cause various issues for the servers handling them.

  Processing of these records may lead to unexpected outcomes. Recursive
  servers may crash or disclose some portion of memory to the client.
  Secondary servers may crash on restart after transferring a zone
  containing these records. Master servers may corrupt zone data if the
  zone option "auto-dnssec" is set to "maintain". Other unexpected
  problems that are not listed here may also be encountered.

All BIND users are strongly encouraged to upgrade.

Upgrade to BIND versions 9.9.1, 9.8.3, 9.7.6, and 9.6-ESV-R7,
the latest from ISC. These versions all contain the following:

Feature Change

*  BIND now recognizes the TLSA resource record type, created to
   support IETF DANE (DNS-based Authentication of Named Entities)
   [RT #28989]

Bug Fix

*  The locking strategy around the handling of iterative queries
   has been tuned to reduce unnecessary contention in a multi-
   threaded environment.

Each version also contains other critical bug fixes.

All BIND users are encouraged to upgrade to these latest versions.

Update to version 9.6-ESV-R6, the latest from ISC, which contains numerous bug
fixes.

For the port, switch to using the PORTDOCS macro.
Also, switch to the (identical) pkg-message in ../bind97 which was apparently
missed
when the other ports were converted.

Feature safe:   yes

Upgrade to the latest security patch releases to address the
following DDOS bug:

Recursive name servers are failing with an assertion:
INSIST(! dns_rdataset_isassociated(sigrdataset))

At this time it is not thought that authoritative-only servers
are affected, but information about this bug is evolving rapidly.

Because it may be possible to trigger this bug even on networks
that do not allow untrusted users to access the recursive name
servers (perhaps via specially crafted e-mail messages, and/or
malicious web sites) it is recommended that ALL operators of
recursive name servers upgrade immediately.

For more information see:
https://www.isc.org/software/bind/advisories/cve-2011-tbd
which will be updated as more information becomes available.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-4313

Feature safe:   yes

Remove more tags from pkg-descr files fo the form:

- Name
em@i.l

or variations thereof. While I'm here also fix some whitespace and other
formatting errors, including moving WWW: to the last line in the file.

Update to version 9.6-ESV-R5 which contains various bug fixes
and improvements:

ftp://ftp.isc.org/isc/bind9/9.6-ESV-R5/RELEASE-NOTES-BIND-9.6-ESV.html

Remove patch incorporated into version 9.6-ESV-R5

Fix the location of the default pid file in named.8

Problem pointed out in the PR

PR:             conf/155006
Submitted by:   Helmut Schneider <jumper99@gmx.de>

Update to versions 9.7.3-P3, and 9.6-ESV-R4-P3.

ALL BIND USERS ARE ENCOURAGED TO UPGRADE IMMEDIATELY

This update addresses the following vulnerability:

CVE-2011-2464
=============
Severity:       High
Exploitable:    Remotely

Description:

A defect in the affected BIND 9 versions allows an attacker to remotely
cause the "named" process to exit using a specially crafted packet. This
defect affects both recursive and authoritative servers. The code location
of the defect makes it impossible to protect BIND using ACLs configured
within named.conf or by disabling any features at compile-time or run-time.

https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2464
https://www.isc.org/software/bind/advisories/cve-2011-2464

Upgrade to 9.6-ESV-R4-P1 and 9.7.3-P1, which address the following issues:

1. Very large RRSIG RRsets included in a negative cache can trigger
an assertion failure that will crash named (BIND 9 DNS) due to an
off-by-one error in a buffer size check.

This bug affects all resolving name servers, whether DNSSEC validation
is enabled or not, on all BIND versions prior to today. There is a
possibility of malicious exploitation of this bug by remote users.

2. Named could fail to validate zones listed in a DLV that validated
insecure without using DLV and had DS records in the parent zone.

Add a patch provided by ru@ and confirmed by ISC to fix a crash at
shutdown time when a SIG(0) key is being used.

Miscellaneous cleanups and fixes, some of the windowmaker stuff
gracefully provided by danfe.

Update to BIND 9.6.3, the latest from ISC on the 9.6 branch.

All 9.6 users with DNSSEC validation enabled should upgrade to this
version, or the latest version in the 9.7 branch, prior to 2011-03-31 in
order to avoid validation failures for names in .COM as described here:

https://www.isc.org/announcement/bind-9-dnssec-validation-fails-new-ds-record

In addition the fixes for this and other bugs, there are also the following:

* Various fixes to kerberos support, including GSS-TSIG
* Various fixes to avoid leaking memory, and to problems that could prevent
  a clean shutdown of named

Feature safe:   yes

CONFLICTS for bind98

Update to version 9.6-ESV-R3, the latest from ISC, which addresses
the following security vulnerabilities.

For more information regarding these issues please see:
http://www.isc.org/announcement/guidance-regarding-dec-1st-2010-security-advisories

1. Cache incorrectly allows ncache and rrsig for the same type

   http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3613

   Affects resolver operators whose servers are open to potential
   attackers. Triggering the bug will cause the server to crash.

   This bug applies even if you do not have DNSSEC enabled.

Update to 9.6-ESV-R2, the latest from ISC.

This version contains bug fixes that are relevant to any
caching/resolving name server; as well as DNSSEC-related
fixes.

Update to the latest patch set from ISC, which addresses the following:

   Named could return SERVFAIL for negative responses
   from unsigned zones.

Update to the latest patchfix releases to deal with the problems
related to the handling of broken DNSSEC trust chains.

This fix is only necessary for those who have DNSSEC validation
enabled and configure trust anchors from third parties, either
manually, or through a system like DLV.

Upgrade to version 9.6.2. This version includes all previously released
security patches to the 9.6.1 version, as well as many other bug fixes.

Due to the fact that the DNSSEC algorithm that will be used to sign the
root zone is only included in this version and in 9.7.x those who wish
to do validation MUST upgrade to one of these prior to July 2010.

Feature safe:   yes

Upgrade to BIND 9.4.3-P5, 9.5.2-P2, and 9.6.1-P3. These versions address
the following vulnerabilities:

BIND 9 Cache Update from Additional Section
https://www.isc.org/advisories/CVE-2009-4022v6
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2009-4022
A nameserver with DNSSEC validation enabled may incorrectly add
unauthenticated records to its cache that are received during the
resolution of a recursive client query

BIND 9 DNSSEC validation code could cause bogus NXDOMAIN responses
https://www.isc.org/advisories/CVE-2010-0097
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-0097
There was an error in the DNSSEC NSEC/NSEC3 validation code that could
cause bogus NXDOMAIN responses (that is, NXDOMAIN responses for records
proven by NSEC or NSEC3 to exist) to be cached as if they had validated
correctly

These issues only affect systems with DNSSEC validation enabled.

Update CONFLICTS for bind97

Update to the latest patchlevels for BINDs 9.[456]. The vulnerability
this is designed to fix is related to DNSSEC validation on a resolving
name server that allows access to untrusted users. If your system does
not fall into all 3 of these categories you do not need to update
immediately.

Wrap some query socket handling in dig with a socket != NULL bow

This patch or something similar will likely be included in a future
BIND release.

PR:             bin/138061
Submitted by:   Michael Baker <michael.baker@diversit.com.au>
Original patch submitted by:    Volker <volker@vwsoft.com>
Patch reviewed and tweaked by:  ISC

The new LINKS OPTION is not only useless it's harmful when combined
with the REPLACE_BASE option so if the latter is defined don't try
to make the LINKS.

Problem pointed out by: Chris Wopat <me@falz.net>

For all:
Add an OPTION (on by default) to install the appropriate symlinks for
named.conf and rndc.key in /usr/local/etc and /var/named/usr/local/etc.

For bind9[456]:
Add OPTIONs (off by default) for the DLZ configure options, and their
corresponding ports knobs. [1] The basic infrastructure for this was
provided in the PR, but this version is slightly different in a few
details so responsibility for bugs is mine.

PR:             ports/122974 [1]
Submitted by:   Michael Schout <mschout@gkg.net> [1]

The dependency on idnkit should be a LIB_, not a BUILD_

PR:             ports/137240
Submitted by:   danger

Update the hashes of the PGP signature files for the new releases.
The previous signatures were derived from the wrong key.
The new signatures all verify correctly.

No changes to the hashes for the software itself.

Update to patched versions which address a remote DoS vulnerability:

        Receipt of a specially-crafted dynamic update message may
        cause BIND 9 servers to exit. This vulnerability affects all
        servers -- it is not limited to those that are configured to
        allow dynamic updates. Access controls will not provide an
        effective workaround.

More details can be found here: https://www.isc.org/node/474

All BIND users are encouraged to update to a patched version ASAP.

Update to version 9.6.1, the latest from ISC. This version contains
numerous bug fixes and updates, especially in the DNSSEC code, including
the new NSEC3 protocol. Full details are available at:

http://oldwww.isc.org/sw/bind/view/?release=9.6.1&noframes=1

- Flip from MAKE_JOBS_SAFE to MAKE_JOBS_UNSAFE, fails both on pointyhat and on
  my local machine

Fix CONFLICTS (again). The previous example didn't work at all for ports
other than plain bind9 since the real PORTNAMEs for the other ports are
bind9[456]. This fix has the added advantage of covering REPLACE_BASE.

Where it matters, update regarding MAKE_JOBS_{UN}SAFE for my ports

Update to the -P1 versions of the current BIND ports which contain
the fix for the following vulnerability: https://www.isc.org/node/373

Description:
Return values from OpenSSL library functions EVP_VerifyFinal()
and DSA_do_verify() were not checked properly.

Impact:
It is theoretically possible to spoof answers returned from
zones using the DNSKEY algorithms DSA (3) and NSEC3DSA (6).

In short, if you're not using DNSSEC to verify signatures you have
nothing to worry about.

While I'm here, address the issues raised in the PR by adding a knob
to disable building with OpenSSL altogether (which eliminates DNSSEC
capability), and fix the configure arguments to better deal with the
situation where the user has ssl bits in both the base and LOCALBASE.

PR:             ports/126297
Submitted by:   Ronald F.Guilmette <rfg@tristatelogic.com>

Update CONFLICTS to reflect the addition of the bind96 port,
the demise of bind9-dlz, and updates to the bind9-sdb-* ports.

Update after repo-copy for BIND 9.6.0

Forced commit to mark repo-copy from bind95