As previously advertised, remove BIND 9.3.x coincident with the
EOL of RELENG_6.

DEPRECATED=             Past EOL, will be removed when RELENG_6 goes EOL
EXPIRATION_DATE=        2010-11-30

Update CONFLICTS for bind97

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]

Apply the patch derived from version 9.6.1-P1 which addresses 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.

- 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.

Upgrade to version 9.3.6.

Add a note to pkg-message indicating that ISC declared this version EOL
as of 1 December, but that we will support the port through the RELENG_6
lifetime.

Adjust WWWs for new ISC website

All -P2 versions now have PGP signatures with ISC's standard
signing key.

PR:             ports/126389 (for bind9)
Submitted by:   Tsurutani Naoki <turutani@scphys.kyoto-u.ac.jp>

Update to patchlevel 2 for all versions:

- performance improvement over the P1 releases, namely
   + significantly remedying the port allocation issues
   + allowing TCP queries and zone transfers while issuing as many
      outstanding UDP queries as possible
   + additional security of port randomization at the same level as P1

- also includes fixes for several bugs in the 9.5.0 base code

Upgrade to the -P1 versions of each port, which add stronger randomization
of the UDP query-source ports. The server will still use the same query
port for the life of the process, so users for whom the issue of cache
poisoning is highly significant may wish to periodically restart their
server using /etc/rc.d/named restart, or other suitable method.

In order to take advantage of this randomization users MUST have an
appropriate firewall configuration to allow UDP queries to be sent and
answers to be received on random ports; and users MUST NOT specify a
port number using the query-source[-v6] option.

The avoid-v[46]-udp-ports options exist for users who wish to eliminate
certain port numbers from being chosen by named for this purpose. See
the ARM Chatper 6 for more information.

Update CONFLICTS:
1. To take bind95 into account
2. s/bind9-sdb-ldap/bind9-sdb-mysql/
3. Delete references to BIND 8

Update to version 9.3.5. It contains the latest bug fixes, updates
to root server addresses, and a fix for the vulnerability mentioned
here: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0122

Users of BIND 9.3.x are strongly encouraged to upgrade to this
version. Also, the 9.3.x branch is now in maintenance-only mode.
Users are encouraged to investigate BIND 9.4.x or perhaps 9.5.x.

http://www.isc.org/index.pl?/sw/bind/versions_and_support.php

ISC recently announced that BIND 8 has been End-of-Life'd:
http://www.isc.org/index.pl?/sw/bind/bind8-eol.php

Therefore, per the previous announcement, remove the ports for BIND 8.
This includes the chinese/bind8 slave port, and mail/smc-milter which
has a dependency on libbind_r.a from BIND 8.x. The latter has been
unmaintained since 2005, and is 3 versions behind.

Approved by:    portmgr (linimon)

Update to 9.3.4-P1, which fixes the following:

The DNS query id generation is vulnerable to cryptographic
analysis which provides a 1 in 8 chance of guessing the next
query id for 50% of the query ids. This can be used to perform
cache poisoning by an attacker.

This bug only affects outgoing queries, generated by BIND 9 to
answer questions as a resolver, or when it is looking up data
for internal uses, such as when sending NOTIFYs to slave name
servers.

All users are encouraged to upgrade.

See also:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2926

- Set --mandir and --infodir in CONFIGURE_ARGS if the configure script
  supports them.  This is determined by running ``configure --help'' in
  do-configure target and set the shell variable _LATE_CONFIGURE_ARGS
  which is then passed to CONFIGURE_ARGS.
- Remove --mandir and --infodir in ports' Makefile where applicable
  Few ports use REINPLACE_CMD to achieve the same effect, remove them too.
- Correct some manual pages location from PREFIX/man to MANPREFIX/man
- Define INFO_PATH where necessary
- Document that .info files are installed in a subdirectory relative to
  PREFIX/INFO_PATH and slightly change add-plist-info to use INFO_PATH and
  subdirectory detection.

PR:             ports/111470
Approved by:    portmgr
Discussed with: stas (Mk/*), gerald (info related stuffs)
Tested by:      pointyhat exp run

Add a CONFLICTS to bind 9.4.

Upgrade to version 9.3.4, the latest from ISC, which addresses the
following security issues. All users of BIND are encouraged to upgrade
to this version.

2126.   [security]      Serialise validation of type ANY responses. [RT #16555]

2124.   [security]      It was possible to dereference a freed fetch
                        context. [RT #16584]

2089.   [security]      Raise the minimum safe OpenSSL versions to
                        OpenSSL 0.9.7l and OpenSSL 0.9.8d.  Versions
                        prior to these have known security flaws which
                        are (potentially) exploitable in named. [RT #16391]

2088.   [security]      Change the default RSA exponent from 3 to 65537.
                        [RT #16391]

2066.   [security]      Handle SIG queries gracefully. [RT #16300]

1941.   [bug]           ncache_adderesult() should set eresult even if no
                        rdataset is passed to it. [RT #15642]

Apply the markup fixes from the base to the nsupdate.8 and
nslookup.1 man pages.

Upgrade to version 9.3.3, the latest from ISC. This is
a maintenance release, with the usual round of bug and
security fixes.

All users of BIND 9 are encouraged to upgrade to this
version.

Update to version 9.3.2-P2, which addresses the vulnerability
announced by ISC dated 31 October (delivered via e-mail to the
bind-announce@isc.org list today):

Description:
        Because of OpenSSL's recently announced vulnerabilities
        (CAN-2006-4339, CVE-2006-2937 and CVE-2006-2940) which affect named,
        we are announcing this workaround and releasing patches.  A proof of
        concept attack on OpenSSL has been demonstrated for CAN-2006-4339.

        OpenSSL is required to use DNSSEC with BIND.

Fix for version 9.3.2-P1 and lower:
        Upgrade to BIND 9.2.3-P2, then generate new RSASHA1 and
        RSAMD5 keys for all old keys using the old default exponent
        and perform a key rollover to these new keys.

        These versions also change the default RSA exponent to be
        65537 which is not vulnerable to the attacks described in
        CAN-2006-4339.

Upgrade to version 9.3.2-P1, which addresses the following security
vulnerabilities:

http://www.niscc.gov.uk/niscc/docs/re-20060905-00590.pdf?lang=en
2066.  [security]      Handle SIG queries gracefully. [RT #16300]

http://www.kb.cert.org/vuls/id/697164
1941.  [bug]           ncache_adderesult() should set eresult even if no
                       rdataset is passed to it. [RT #15642]

All users of BIND 9 are encouraged to upgrade to this version.

Add OPTIONS to the rest of my ports that need them.

Add CONFLICTS to the bind* ports.

Replace ugly "@unexec rmdir %D... 2>/dev/null || true" with @dirrmtry

Approved by:    krion@
PR:             ports/88711 (related)

Update to 9.3.2, the latest from ISC

Move the verify target after pre-fetch.

Committed the wrong version ... s#/usr/local#${LOCALBASE}#

Fix a long-standing problem that appears when users install
openssl from ports, and do not use the option to have the port
version overwrite the base version.

Several folks have mentioned this problem in the past, but a
good workaround (and more importantly, solid testing) were
provided by the submitter.

Submitted by:   Uffe Vedenbrant <uffe@vedenbrant.se>

Add SHA256 checksums to my ports

For the ports that I maintain, do the following as appropriate:

1. Add myself as a backup master site (Sourceforge and CPAN ports
already have good enough coverage, so skip them).
2. For all ports that have them, download the PGP signature files.
3. For ports in 2, add a verify target to the Makefile
4. For ports where I was already providing a master site, update the URL.
5. Pet portlint in a couple of places.

This issue was researched by glebius, and this patch was
incorporated by ISC into the next version of BIND.

The patch addresses a problem with high-load resolvers which
hit memory barriers. Without this patch, running the resolving
name server out of memory would lead to "unpredictable results."

Of course, the canonical answer to this problem is to put more
memory into the system, however that is not always possible, and
the code should be able to handle this situation gracefully in
any case.

Approved by:    portmgr (krion)

ISC staff has informed me that in BIND 9.3.x, threads are always a
bad idea, so disable them in all cases unless the user has
affirmatively requested this through the define.

1. The OPTIONS stuff isn't working the way it should according to reports,
so rip it out until I have a chance to debug it.

2. Improve the comment about deprecating an old knob.

Upgrade to 9.3.1, the latest version from ISC. This version contains
several important fixes, including a remote (although unlikely) exploit.
See the CHANGES file for details.

All users of BIND 9 are highly encouraged to upgrade to this version.

Changes to the port include:
1. Remove ISC patch to 9.3.0 that addressed the remote exploit
2. Change to OPTIONS, and thereby
3. --enable-threads is now the default. Users report that the new thread
code in 9.3.x works significantly better than the old on all versions of
FreeBSD.
4. Add a temporary shim for the old PORT_REPLACES_BASE_BIND9 option.
The OPTIONS framework requires knobs to start with WITH_ or WITHOUT_
5. Remove patch that shoehorned named.conf.5 into the right place,
it has been fixed in the code.

Include a patch from ISC to deal with the following vulnerability:

Name:                   BIND: Self Check Failing [Added 2005.25.01]
Versions affected:      BIND 9.3.0
Severity:               LOW
Exploitable:            Remotely
Type:                   Denial of Service
Description:
An incorrect assumption in the validator (authvalidated) can result in a
REQUIRE (internal consistancy) test failing and named exiting.

Workarounds:
Turn off dnssec validation (off by default) at the options/view level.

        dnssec-enable no;

Active Exploits:        None known

Bump PORTREVISION accordingly.

It should be noted that the vast majority of users would not have
DNSSEC enabled, and therefore are not vulnerable to this bug.

The parens around the OSVERSION test were fatal for < 4.9, and did not
provide anything useful for newer systems, so remove them.

PR:             ports/72118
Submitted by:   Michel Lavondes <fox@vader.aacc.cc.md.us>
Approved by:    portmgr (eik)

Update to BIND 9.3.0, the latest from ISC. This version has several
significant updates, not the least of which is the new and improved
DNSSEC code based on the latest standards (including DS).

Various updates to the port, including:
1. Download the PGP signature
2. If running on ${OSVERSION} >= 503000, configure with threads
3. Update pkg-descr re IPv6 RRs
4. Update pkg-message to reflect a world with 6-current

There is also a patch to correct a man page installation error.
This problem should be fixed in the next release.

Approved by:    portmgr (marcus)

The ringserver sites don't have the latest BIND 9.

Submitted by:   fenner's distfile survey

DISTNAME is a slightly less painful way of dealing with wacky
version numbers.

Now that the SIZE thing has stabilized, add it to the ports I maintain.

I specifically stated that I did not want to bump portepoch for this port.

I realize that my error in version numbering previously caused some confusion
about 9.2.3 being a more up to date version than 9.2.3.4, but this will quickly
be resolved with the next version, and affected only a few users who installed
the release candidate. The portepoch change is permanent, and perpetuates a
silly kludge for no good reason.

Please do not change this again without discussing it with me.

Fix removal of the last digit in the version number issue.

[~/cvs/ports/dns/bind9] edwin@k7>pkg_version -t 9.2.3.4 9.2.3
>
[~/cvs/ports/dns/bind9] edwin@k7>pkg_version -t 9.2.3.4 9.2.3,1
<

Upgrade to the 9.2.3 release version

Unbreak(?) USE_OPENSSL support for people that don't have it in the base

Submitted by:   A cast of thousands

Upgrade to version 9.2.3rc4.

The 9.2.3 code has many many bugs fixed from 9.2.2, check CHANGES
for more information.

The rc4 code has the delegation-only options. Check the ARM for
information on how to enable it.

DOCSDIR'ify

Chase repocopies towards ports/dns

PR:             ports/56020
Submitted by:   Kimura Fuyuki <fuyuki@nigredo.org>
Approved by:    portmgr

Massive repo-copies request: net->dns (partly devel->dns)

PR:             ports/56020
Submitted by:   Kimura Fuyuki <fuyuki@nigredo.org>
Approved by:    portmgr