|non port: head/dns/bind94/distinfo
found something from the cache
Number of commits found: 25
Wed, 1 Jun 2011
[ 00:22 dougb ] |
BIND 9.4.x is now EOL
Fri, 27 May 2011
[ 23:46 dougb ] |
Upgrade to 9.4-ESV-R4-P1, which addresses 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.
Fri, 3 Dec 2010
[ 23:57 dougb ] |
Update to version 9.4-ESV-R4, the latest from ISC, which addresses
the following security vulnerability.
For more information regarding these issues please see:
Key algorithm rollover
Affects resolver operators who are validating with DNSSEC,
and querying zones which are in a key rollover period.
The bug will cause answers to incorrectly be marked as insecure.
For the port:
1. Add CONFLICT for the ../bind-tools port
2. Remove CONFLICT for the removed ../bind9 port
3. Remove OPTION for threads on < RELENG_7
4. Remove MD5 from distinfo
5. Switch to pkg-install to create the symlinks to /etc/namedb/ as
requested in 
PR: ports/151635 
Submitted by: Benjamin Lee <email@example.com> 
Tue, 19 Oct 2010
[ 00:12 dougb ] |
Update to 9.4-ESV-R3, the latest from ISC.
Thu, 20 May 2010
[ 06:34 dougb ] |
Update to the latest patch set from ISC, which addresses the following:
Named could return SERVFAIL for negative responses
from unsigned zones.
Wed, 17 Mar 2010
[ 05:35 dougb ] |
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.
Tue, 2 Feb 2010
[ 07:14 dougb ] |
Upgrade to 9.4-ESV, the first of the "Extended Support Releases"
from ISC. It has numerous bug fixes compared to 9.4.3*, however
in the case of this version "extended" only applies till 2010/12/31
so serious BIND users are still encouraged to upgrade to 9.6.x.
Tue, 26 Jan 2010
[ 18:18 dougb ] |
Blah ... forgot to re-add this patch for the slave port again.
Mon, 25 Jan 2010
[ 00:25 dougb ] |
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
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
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
These issues only affect systems with DNSSEC validation enabled.
Sat, 5 Dec 2009
[ 02:12 dougb ] |
Add back the geoip patch that was mistakenly deleted in the upgrade
Mon, 30 Nov 2009
[ 02:46 dougb ] |
Update to the latest patchlevels for BINDs 9.. 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
Sat, 15 Aug 2009
[ 18:20 dougb ] |
Add a slave port to bind94 for the GeoIP patch from Caraytech.
The most popular use of this patch is to send web site visitors to their
nearest web server. Suppose you have a site called www.example555.com with
two web servers: one in the US and one in England. You can use this patch
in order for visitors from Europe to connect to the server in England and
all other visitors to the server in the US. This is just one example of
its usage. There are probably many others.
I created a slave port rather than making this an option but other than
that I was able to use the excellent work in the PR.
Submitted by: Jui-Nan Lin <firstname.lastname@example.org>
Wed, 29 Jul 2009
[ 18:23 dougb ] |
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.
Tue, 28 Jul 2009
[ 22:13 dougb ] |
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
More details can be found here: https://www.isc.org/node/474
All BIND users are encouraged to update to a patched version ASAP.
Sat, 21 Mar 2009
[ 20:40 dougb ] |
BIND 9.4.3-P2 is a SECURITY patch for BIND 9.4.3. It addresses a bug
in DNSSEC lookaside validation (DLV): unrecognized signature algorithms,
which should have been treated as the equivalent of an unsigned zone,
were instead treated as a validation failure.
Thu, 8 Jan 2009
[ 08:18 dougb ] |
Update to the -P1 versions of the current BIND ports which contain
the fix for the following vulnerability: https://www.isc.org/node/373
Return values from OpenSSL library functions EVP_VerifyFinal()
and DSA_do_verify() were not checked properly.
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.
Submitted by: Ronald F.Guilmette <email@example.com>
Fri, 19 Dec 2008
[ 21:40 dougb ] |
Update to version 9.4.3 which contains numerous bug fixes.
This version also includes the use-v-udp-ports options to configure
a range of random UDP ports to initiate queries from.
Sat, 9 Aug 2008
[ 07:23 dougb ] |
All -P2 versions now have PGP signatures with ISC's standard
PR: ports/126389 (for bind9)
Submitted by: Tsurutani Naoki <firstname.lastname@example.org>
Sat, 2 Aug 2008
[ 07:01 dougb ] |
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
Wed, 9 Jul 2008
[ 19:02 dougb ] |
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-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.
(Only the first 15 lines of the commit message are shown above )
Sat, 1 Dec 2007
[ 21:53 dougb ] |
Update to BIND 9.4.2. Many bugs are fixed, please see the CHANGES
file for more details.
Approved by: portmgr (erwin)
Tue, 24 Jul 2007
[ 22:02 dougb ] |
Update to 9.4.1-P1, which has fixes for the following:
1. The default access control lists (acls) are not being
correctly set. If not set anyone can make recursive queries
and/or query the cache contents.
2. 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
All users are encouraged to upgrade.
Tue, 1 May 2007
[ 01:00 dougb ] |
Update to version 9.4.1, a security update from ISC:
2172. [bug] query_addsoa() was being called with a non zone db.
If you are running BIND 9.4.0 (either pre-release or final),
you are advised to upgrade as soon as possible to BIND 9.4.1.
Mon, 26 Feb 2007
[ 07:57 dougb ] |
Update to the release version of 9.4.0.
Sun, 28 Jan 2007
[ 22:45 dougb ] |
Complete the update for bind94 after the repocopy, and hook it up.
Number of commits found: 25