summaryrefslogtreecommitdiffstats
path: root/contrib/bind9/lib
Commit message (Collapse)AuthorAgeFilesLines
* Update to 9.8.4-P1.erwin2012-12-07134-484/+1811
|\ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Security Fixes Prevents named from aborting with a require assertion failure on servers with DNS64 enabled. These crashes might occur as a result of specific queries that are received. New Features * Elliptic Curve Digital Signature Algorithm keys and signatures in DNSSEC are now supported per RFC 6605. [RT #21918] Feature Changes * Improves OpenSSL error logging [RT #29932] * nslookup now returns a nonzero exit code when it is unable to get an answer. [RT #29492] Other critical bug fixes are included. Approved by: delphij (mentor) MFC after: 3 days Security: CVE-2012-5688 Sponsored by: DK Hostmaster A/S
* | Upgrade to 9.8.3-P3:dougb2012-09-204-7/+35
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 Failuredougb2012-07-242-8/+23
| | | | | | | | | | | | | | | | | | | | | | 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.8.3-P1, the latest from ISC. This version containsdougb2012-06-042-7/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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 version 9.8.3, the latest from ISC.dougb2012-05-2820-214/+629
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Feature Change * BIND now recognizes the TLSA resource record type, created to support IETF DANE (DNS-based Authentication of Named Entities) Bug Fix * The locking strategy around the handling of iterative queries has been tuned to reduce unnecessary contention in a multi- threaded environment. Other critical bug fixes are included. All BIND users are encouraged to upgrade.
* | Update to version 9.8.2, the latest from ISC, which contains numerous bug fixes.dougb2012-04-05741-1733/+2514
| |
* | Upgrade to BIND 9.8.1-P1 to address the following DDOS bug:dougb2011-11-171-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Upgrade to BIND version 9.8.1. Release notes at:dougb2011-09-03126-1005/+1924
|\ \ | |/ | | | | | | | | | | | | https://deepthought.isc.org/article/AA-00446/81/ or /usr/src/contrib/bind9/ Approved by: re (kib)
* | Upgrade to version 9.8.0-P4dougb2011-07-16401-4055/+36976
|\ \ | |/ | | | | | | This version has many new features, see /usr/share/doc/bind9/README for details.
* | Update to version 9.6-ESV-R4-P3dougb2011-07-0610-59/+78
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Apply bug fixesdougb2011-07-061-10/+9
| | | | | | | | Submitted by: marius
* | Upgrade to 9.6-ESV-R4-P1, which address the following issues:dougb2011-05-28581-622/+629
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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.
* | Update to BIND 9.6.3, the latest from ISC on the 9.6 branch.dougb2011-02-0677-438/+964
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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
* | Update to version 9.6-ESV-R3, the latest from ISC, which addressesdougb2010-12-048-39/+131
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | 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. 2. Key algorithm rollover http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3614 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.
* | Update to 9.6-ESV-R2, the latest from ISC.dougb2010-10-3140-411/+755
| | | | | | | | | | | | This version contains bug fixes that are relevant to any caching/resolving name server; as well as DNSSEC-related fixes.
* | Upgrade to 9.6.2-P2, which addresses the following;dougb2010-05-202-3/+3
| | | | | | | | | | Named could return SERVFAIL for negative responses from unsigned zones.
* | Update to 9.6.2-P1, the latest patchfix release which deals withdougb2010-03-1833-172/+774
| | | | | | | | | | | | | | | | the problems related to the handling of broken DNSSEC trust chains. This fix is only relevant 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 releaseddougb2010-03-0392-610/+1464
| | | | | | | | | | | | | | | | | | | | | | | | security patches to the 9.6.1 version, as well as many other bug fixes. This version also incorporates a different fix for the problem we had patched in contrib/bind9/bin/dig/dighost.c, so that file is now back to being the same as the vendor version. 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.
* | Upgrade to BIND 9.6.1-P3.dougb2010-01-2523-129/+124
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This version 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.
* | Fix Read-After-Write (RAW) dependency violation for ar.ccv inmarcel2009-12-071-2/+2
| | | | | | | | | | | | | | isc_atomic_xadd() and isc_atomic_cmpxchg(). Approved by: dougb@ MFC after: 1 week
* | Update to BIND 9.6.1-P2. The vulnerability this is designed to fix isdougb2009-11-306-29/+65
| | | | | | | | | | | | 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.
* | This is the solution that ISC committed after 9.6.1-release fordougb2009-06-251-0/+9
| | | | | | | | | | the gcc warning issue. It should be included in the next upstream release.
* | Update to the final release version of BIND 9.6.1. It has the followingdougb2009-06-258-33/+176
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | changes from the 9.6.1rc1 version. The first 2 only affect DNSSEC. named could incorrectly delete NSEC3 records for empty nodes when processing a update request. Accept DS responses from delegation only zones. "delegation-only" was not being accepted in delegation-only type zones.
* | Local hack to get the build going again while ISC works on a moredougb2009-06-011-9/+0
| | | | | | | | | | | | | | | | | | | | | | permanent solution for 9.6.1-release. "My suggestion is to remove the whole attribute construct. It only suppresses a warning when a function is unused. In this case the function is defined as inline, so it's not causing a warning when not used." Submitted by: marcel
* | Update BIND to version 9.6.1rc1. This version has better performance anddougb2009-05-31863-65008/+28607
|\ \ | |/ | | | | | | | | | | | | | | | | | | | | | | lots of new features compared to 9.4.x, including: Full NSEC3 support Automatic zone re-signing New update-policy methods tcp-self and 6to4-self DHCID support. More detailed statistics counters including those supported in BIND 8. Faster ACL processing. Efficient LRU cache-cleaning mechanism. NSID support.
* | Merge from vendor/bind9/dist as of the 9.4.3-P2 importdougb2009-03-211-12/+67
| |
* | Merge from vendor/bind9/dist as of the 9.4.3-P1 importdougb2009-01-094-9/+8
| |
* | Merge from vendor/bind9/dist as of the 9.4.3 importdougb2008-12-23100-1626/+4995
|\ \ | |/
| * Flatten bind9 vendor work areapeter2008-07-12837-292145/+0
| |
* | Merge from vendor/bind9/dist as of the 9.4.2-P2 importdougb2008-09-0119-104/+393
| |
* | Merge from vendor/bind9/dist as of the 9.4.2-P1 import, includingdougb2008-07-128-34382/+285
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | the patch from ISC for lib/bind9/check.c and deletion of unused files in lib/bind. This version will by default randomize the UDP query source port (and sequence number of course) for every query. 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] options. 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. All users of BIND are strongly encouraged to upgrade to the latest version, and to utilize the source port randomization feature. 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
* Update this file so that BIND on ARM can actually work. I quote:dougb2007-12-031-1/+23
| | | | | | | | | | The problem was, isc_atomic_cmpxchg() is almost like our atomic_cmpset_32(), except it expects the old value to be returned, whereas our atomic_cmpset_32 returns 1 on success, or 0 on failure. So I re-implemented something suitable. Submitted by: cognet Reviewed by: bsdimp
* Vendor import of BIND 9.4.2dougb2007-12-02104-500/+2176
|
* Vendor import of 9.4.1-P1, which has fixes for the following:dougb2007-07-252-51/+457
| | | | | | | | | | | | | | | | | | | | | | | | | | 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. See also: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2925 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 servers. All users are encouraged to upgrade. See also: http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2007-2926 Approved by: re (kensmith, implicit)
* Add a custom atomic.h file which implements the C versions of thedougb2007-06-051-0/+59
| | | | | | code we already have assembly versions of. Written by: imp
* Vendor import of BIND 9.4.1dougb2007-06-02801-18339/+39127
|
* Vendor import of BIND 9.3.4dougb2007-01-294-13/+82
|
* Remove from the vendor branch files that are no longer in thedougb2006-12-102-314/+0
| | | | 9.3.3 sources.
* Vendor import of BIND 9.3.3dougb2006-12-10156-1562/+4753
|
* Update to version 9.3.2-P2, which addresses the vulnerabilitydougb2006-11-042-6/+57
| | | | | | | | | | | | | | | | | | | | | | announced by ISC dated 31 October (delivered via e-mail to the bind-announce@isc.org list on 2 November): 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.3.2-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.
* Vendor import of BIND 9.3.2-P1, which addresses the following securitydougb2006-09-061-22/+29
| | | | | | | | | | | | | 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.
* After some discussion with the folks at ISC, it turns out that the _ai_paddougb2006-01-041-3/+3
| | | | | | | | | | | | part of the structure was a hack to maintain binary compatibility with Sun binaries, and my understanding is that it's not needed generally on sparc systems running other operating systems. Therefore, hide this code behind the same set of tests as in lib/bind/include/netdb.h. This file is being imported on the vendor branch because a similar change (or change with similar effect) will be in the next version of BIND 9. This change will not affect other platforms in any way.
* Vendor import of BIND 9.3.2dougb2005-12-29157-8758/+7791
|
* Update the vendor branch with a patch to this file that wasdougb2005-08-181-2/+4
| | | | | | | | | | | | | | | | researched by glebius, and incorporated by ISC into the next version of BIND. Unfortunately, it looks like their release will come after the release of FreeBSD 6, so we will bring this in now. 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.
* Remove files from the vendor branch that were [re]moved in 9.3.1dougb2005-03-1725-16498/+0
|
* Vendor import of BIND 9.3.1dougb2005-03-1775-640/+6542
|
* Vendor import of BIND 9.3.0rc4.trhodes2004-09-193-0/+602
| | | | | These three files were missed in the original import because their names contained the magic letters w, i and n in that sequence.
* Vender import of BIND 9.3.0rc4.trhodes2004-09-19783-0/+277149
OpenPOWER on IntegriCloud