non port: dns/bind95/distinfo |
Number of commits found: 17 |
Saturday, 1 Jan 2011
|
00:38 dougb
Remove dns/bind95 which entered EOL 2010-09
|
Friday, 3 Dec 2010
|
23:02 dougb
Actually remove the MD5, oops
|
Thursday, 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.
|
Wednesday, 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.
|
Monday, 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
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.
|
Monday, 30 Nov 2009
|
02:46 dougb
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.
|
Friday, 25 Sep 2009
|
00:34 dougb
Update to version 9.5.2, the latest from ISC. This version has numerous
bug fixes, and all users of BIND 9.5.x are encouraged to upgrade.
Feature safe: yes
|
Wednesday, 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.
|
Tuesday, 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
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.
|
Saturday, 21 Mar 2009
|
20:33 dougb
BIND 9.5.1-P2 is a SECURITY patch for BIND 9.5.1. 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.
|
Thursday, 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
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>
|
Monday, 29 Dec 2008
|
21:29 dougb
Upgrade to version 9.5.1 which includes numerous bug fixes and performance
improvements, including, "Additional support for query port randomization
including performance improvement and port range specification."
When building on amd64 ports' configure doesn't properly recognize our
arch, so help it along a bit. [1]
Submitted by: ivan jr sy <ivan_jr@yahoo.com> [1]
|
Saturday, 9 Aug 2008
|
07:23 dougb
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>
|
Saturday, 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
|
Wednesday, 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[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.
Also please note, this issue applies only to UDP query ports. A random
ephemeral port is always chosen for TCP queries.
This issue applies primarily to name servers whose main purpose is to
resolve random queries (sometimes referred to as "caching" servers, or
more properly as "resolving" servers), although even an "authoritative"
name server will make some queries, primarily at startup time.
This update addresses issues raised in:
http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-1447
http://www.kb.cert.org/vuls/id/800113
http://tools.ietf.org/html/draft-ietf-dnsext-forgery-resilience
|
Thursday, 3 Jul 2008
|
07:26 dougb
Update for 9.5.0
Some of the important features of BIND 9 are:
DNS Security: DNSSEC (signed zones), TSIG (signed DNS requests)
IP version 6: Answers DNS queries on IPv6 sockets, IPv6 resource records (AAAA)
Experimental IPv6 Resolver Library
DNS Protocol Enhancements: IXFR, DDNS, Notify, EDNS0
Improved standards conformance
Views: One server process can provide multiple "views" of the DNS namespace,
e.g. an "inside" view to certain clients, and an "outside" view to others.
Multiprocessor Support, including working threads in this version
BIND 9.5 has a number of new features over previous versions, including:
GSS-TSIG support (RFC 3645), DHCID support
Experimental http server and statistics support for named via xml
More detailed statistics counters, compatible with the ones supported in BIND 8
Faster ACL processing
Efficient LRU cache cleaning mechanism.
NSID support (RFC 5001).
|
06:12 dougb
Forced commit to note that these files were repo-copied from dns/bind94
|
Number of commits found: 17 |