Changelog for bind-doc-9.18.5-lp153.1.1.noarch.rpm :

* Thu Jul 21 2022 Josef Möllers - Update to bind release 9.18.5 Bugs fixed:
* When resolving a name, don\'t give up immediately if an authoritative server returns FORMERR; try the other servers first.
* When synth-from-dnssec generated a response using records from a higher zone, it could unexpectedly prove non-existance of records in a subordinate grafted-on namespace.
* Update HTTP listener settings on reconfiguration.
* Fix a crash in dig NS search mode when one of the NS server queries fail.
* Changed dnssec-signzone -H default to 0 additional NSEC3 iterations.
* When processing a catalog zone member zone make sure that there is no configured pre-existing forward-only forw]ard zone with that name. [bind-9.18.5.tar.xz bind-9.18.5.tar.xz.sha512.asc]
* Wed Jun 15 2022 Josef Möllers - Upgrade to 9.18.4: Bugs fixed:
* Only write key files if the dnssec-policy keymgr has changed the metadata.
* When the fetches-per-server quota was adjusted because of an authoritative server timing out more or less frequently, it was incorrectly set to 1 rather than the intended value. Notable functional changes:
* Key timing options for `dnssec-keygen` and `dnssec-settime` now accept times as printed by `dnssec-settime -p`.
* Key timing options for `dnssec-settime` and related utilities now accept \"UNSET\" times as printed by `dnssec-settime -p`. This obsoletes the following patch: bind-prevent-buffer-overflow.patch [bind-9.18.4.tar.xz, bind-9.18.4.tar.xz.sha512.asc, bind-prevent-buffer-overflow.patch]
* Thu May 19 2022 Josef Möllers - Upgrade to 9.18.3: Bugs fixed:
* Fix a crash in DNS-over-HTTPS (DoH) code caused by premature TLS stream socket object deletion.
* RPZ NSIP and NSDNAME rule processing didn\'t handle stub and static-stub zones at or above the query name. This has now been addressed.
* Fixed a deadlock that could occur if an rndc connection arrived during the shutdown of network interfaces.
* Refactor the fctx_done() function to set fctx to NULL after detaching, so that reference counting errors will be easier to avoid.
* udp_recv() in dispatch could trigger an INSIST when the callback\'s result indicated success but the response was canceled in the meantime.
* Work around a jemalloc quirk which could trigger an out-of-memory condition in named over time.
* If there was a pending negative cache DS entry, validations depending upon it could fail.
* dig returned a 0 exit status on UDP connection failure.
* Fix an assertion failure when using dig with +nssearch and +tcp options by starting the next query in the send_done() callback (like in the UDP mode) instead of doing that recursively in start_tcp(). Also ensure that queries interrupted while connecting are detached properly.
* Don\'t remove CDS/CDNSKEY DELETE records on zone sign when using \'auto-dnssec maintain;\'. This obsoletes the following patch: bind-define-local-instances-of-FALLTHROUGH-and-UNREACHABLE.patch [CVE-2022-1183, bsc#1199619]
* Tue May 17 2022 Josef Möllers - An assertion failure can be triggered if a TLS connection to a configured http TLS listener with a defined endpoint is destroyed too early. [CVE-2022-1183, bsc#1199619, CVE-2022-1183.patch]
* Mon May 16 2022 Martin Liška - Add upstream patch bind-prevent-buffer-overflow.patch.
* Thu May 12 2022 Josef Möllers - The named-checkconf had been moved from /usr/sbin to /usr/bin but that had not been reflected in scripts that called this, eg named.prep. So these scripts failed. Some installations still have \"createNamedConfInclude\" in the NAMED_INITIALIZE_SCRIPTS in /etc/sysconfig/named. The named.prep will now report this but continue. [bsc#1199044, vendor-files.tar.bz2]
* Mon Apr 25 2022 Josef Möllers - Upgrade to 9.18.2: Most important bugs fixed:
* The \"starting maxtime timer\" message related to outgoing zone transfers was incorrectly logged at the ERROR level instead of DEBUG(1).
* Ensure that zone maintenance queries have a retry limit.
* When using both the `+qr` and `+y` options `dig` could crash if the connection to the first server was not successful.
* dig could hang in some cases involving multiple servers in a lookup, when a request fails and the next one refuses to start for some reason, for example if it was an IPv4 mapped IPv6 address.
* dig +nssearch was hanging until manually interrupted.
* When an UPDATE targets a zone that is not configured, the requested zone name is now logged in the \"not authoritative\" error message, so that it is easier to track down problematic update clients.
* Quote the dns64 prefix in error messages that complain about problems with it, to avoid confusion with the following dns64 ACLs.
* When encountering socket error while trying to initiate a TCP connection to a server, dig could hang indefinitely, when there were more servers to try.
* When timing-out or having other types of socket errors during a query, dig wasn\'t trying to perform the lookup using other servers, in case they exist.
* Resending a UDP request in the result of a timeout could cause an assertion failure when the resent query\'s result was SERVFAIL.
* Replace single TCP write timer with per-TCP write timers.
* Invalid dnssec-policy definitions were being accepted where the defined keys did not cover both KSK and ZSK roles for a given algorithm. This is now checked for and the dnssec-policy is rejected if both roles are not present for all algorithms in use.
* Fix query context management issues in the TCP part of dig. Noteworthy functional changes:
* Add new \"reuseport\" option to enable/disable load balancing of sockets.
* Set the minimum MTU on UDPv6 and TCPv6 sockets and limit TCP maximum segment size (TCP_MAXSEG) to (1220) for both TCPv4 and TCPv6 sockets. Needed to define two macros in contrib code: FALLTHOUGH is a copy of how it is defined in UNREACHABLE follows the model used in MacOS /usr/include/c++/v1/cstdlib to determine if __builtin_ureachable is available [bind-9.18.2.tar.xz, bind-9.18.2.tar.xz.sha512.asc, bind-define-local-instances-of-FALLTHROUGH-and-UNREACHABLE.patch]
* Thu Mar 17 2022 Josef Möllers -
* When using forwarders, bogus NS records supplied by, or via, those forwarders may be cached and used by named if it needs to recurse for any reason, causing it to obtain and pass on potentially incorrect answers. [CVE-2021-25220]
* TCP connection slots may be consumed for an indefinite time frame via a specifically crafted TCP stream sent from a client. This issue can only be triggered on BIND servers which have keep-response-order enabled, which is not the default configuration. The keep-response-order option is an ACL block, and as such, any hosts specified within it will be able to trigger this issue on affected versions. [CVE-2022-0396]
* The RFC 8198 Aggressive Use of DNSSEC-Validated Cache feature (synth-from-dnssec) had been refactored and the default has been changed so that is now automatically enabled for dnssec-validating resolvers. Subsequently it was found that repeated patterns of specific queries to servers with this feature enabled could cause an INSIST failure in query.c:query_dname which causes named to terminate unexpectedly. The vulnerability affects BIND resolvers running 9.18.0 that have both dnssec-validation and synth-from-dnssec enabled. (Note that dnssec-validation auto; is the default setting unless configured otherwise in named.conf and that enabling dnssec-validation automatically enables synth-from-dnssec unless explicitly disabled) [CVE-2022-0635]
* The refactoring of the recursive client code introduced a \"backstop lifetime timer.\" While BIND is processing a request for a DS record that needs to be forwarded, it waits until this processing is complete or until the backstop lifetime timer has timed out. When the resume_dslookup() function is called as a result of such a timeout, the function does not test whether the fetch has previously been shut down. This introduces the possibility of triggering an assertion failure, which could cause the BIND process to terminate. [CVE-2022-0667]
* Reset client TCP connection when data received cannot be parsed as a valid DNS request. For a complete list of changes, see
* Bind Release Notes https://downloads.isc.org/isc/bind9/9.18.1/doc/arm/html/notes.html
* The CHANGES file in the source RPM This obsoletes bind-define-missing-threads.patch Also, removed bind-python3 from the spec file as it is not build any longer. [bind.spec, bind-9.18.1.tar.xz, bind-9.18.1.tar.xz.sha512.asc, bind-define-missing-threads.patch]
* Mon Jan 31 2022 Josef Möllers - Update to new MAJOR VERSION 9.18.0. This has many enhnancements, bug fixes and changes. The spec file also has mechanisms to run the integrated test suite. MAJOR CHANGES:
* Support for securing DNS traffic using Transport Layer Security (TLS). TLS is used by both DNS-over-TLS (DoT) and DNS-over-HTTPS (DoH).
* Support for zone transfers over TLS (XFR-over-TLS, XoT) for both incoming and outgoing zone transfers.
* The dig tool is now able to send DoT queries (+tls option).
* Support for OpenSSL 3.0 APIs was added. A number of utilities have been removed: dnssec-checkds, dnssec-coverage, dnssec-keymgr, which have been deprecated in favor of dnssec-policy feature, as well as python support (package python3-bind). A number of utilities have been moved from (/usr)/sbin to (/usr)/bin The DLZ modules have been put into seperate sub-packages to keep unwanted dependencies out of the main package:
* bind-modules-perl: dlz_perl_driver.so
* bind-modules-mysql: dlz_mysql_dynamic.so, dlz_mysqldyn_mod.so
* bind-modules-ldap: dlz_ldap_dynamic.so
* bind-modules-bdbhpt: dlz_bdbhpt_dynamic.so
* bind-modules-sqlite3: dlz_sqlite3_dynamic.so
* bind-modules-generic: dlz_filesystem_dynamic.so, dlz_wildcard_dynamic.so For a complete list of changes, see
* Bind Release Notes https://downloads.isc.org/isc/bind9/9.18.0/doc/arm/html/notes.html
* The CHANGES file in the source RPM [bind.spec, bind-9.18.0.tar.xz, bind-9.18.0.tar.xz.sha512.asc, bind-avoid-fallthrough-warning-error.patch, bind-contrib-pthread.patch, named-bootconf.diff, bind-define-missing-threads.patch]
* Mon Jan 24 2022 Josef Möllers - Old-style DLZ drivers have been deprecated in favor of DLZ modules. The DLZ drivers configuration option will be removed from the next major BIND 9 release. The option to use the DLZ modules is already available in BIND 9; please see the ARM section on DLZ modules. The dynamically lodable driver modules are stored in /usr/lib64/bind-plugins Example configurations for ldap and mysql are provided in named.conf. [bind.spec, vendor-files/config/named.conf]
* Fri Jan 21 2022 Callum Farmer - Add now working CONFIG parameter to sysusers generator
* Thu Jan 20 2022 Josef Möllers - Upgrade to release 9.16.25 This upgrade fixes the following bugs:
* Enforce enqueuing TCP resumeread to prevent the next read callback from being executed before the current read callback has finished, and the worker receive buffer has been marked as \"freed\".
* Allow replacing expired zone signatures with signatures created by the KSK.
* An assertion could occur if a catalog zone event was scheduled while the task manager was being shut down.
* Defer detaching from zone->raw in zone_shutdown() if the zone is in the process of being dumped to disk, to ensure that the unsigned serial number information is always written in the raw-format header of the signed version on an inline-signed zone.
* named could leak memory when two dnssec-policy clauses had the same name. named failed to log this error.
* Add a missing isc_condition_destroy() for nmsocket condition variable and add missing isc_mutex_destroy() for nmworker lock. [bind-9.16.25.tar.xz, bind-9.16.25.tar.xz.sha512.asc]
* Wed Jan 19 2022 Josef Möllers - Added /var/log to the ReadWritePaths as some log files are written there:
* dump-file \"/var/log/named_dump.db\"
* statistics-file \"/var/log/named.stats\" [bsc#1194721, vendor-files.tar.bz2]
* Wed Dec 15 2021 Josef Möllers - Upgrade to release 9.16.24 This upgrade fixes the following bugs:
* mdig now honors the operating system\'s preferred ephemeral port range.
* Fix a \"named\" crash related to removing and restoring a `catalog-zone` entry in the configuration file and running `rndc reconfig`.
* dns_sdlz_putrr failed to process some valid resource records.
* dnssec-dsfromkey failed to omit revoked keys. Functional change:
* Change the message when accepting TCP connection has failed to say \"Accepting TCP connection failed\" and change the log level for ISC_R_NOTCONNECTED, ISC_R_QUOTA and ISC_R_SOFTQUOTA results codes from ERROR to INFO. [bind-9.16.24.tar.xz]
* Fri Dec 03 2021 Josef Möllers - Upgrade to 9.16.23 Security issues fixed: The \"lame-ttl\" option is now forcibly set to 0. This effectively disables the lame server cache, as it could previously be abused by an attacker to significantly degrade resolver performance. (CVE-2021-25219) Bugs fixed: In 9.16.21:
* When a dynamic zone was made available in another view using the \"in-view\" statement, running \"rndc freeze\" always reported an \"already frozen\" error even though the zone was successfully frozen.
* Stale data in the cache could cause named to send non-minimized queries despite QNAME minimization being enabled.
* When a DNSSEC-signed zone which only has a single signing key available is migrated to use KASP, that key is now treated as a Combined Signing Key (CSK).
* When a member zone was removed from a catalog zone, journal files for the former were not deleted.
* named-checkconf failed to detect syntactically invalid values of the \"key\" and \"tls\" parameters used to define members of remote server lists.
* Fixed a regression which caused the EDNS TCP Keepalive option to be ignored inadvertently in client requests. It has now been fixed and this option is handled properly again.
* Fixed a regression which altered the internal memory structure of zone databases, but neglected to update the MAPAPI value for zone files in \"map\" format. This caused named to attempt to load incompatible map files, triggering an assertion failure on startup. The MAPAPI value has now been updated, so named rejects outdated files when encountering them.
* The thread-local isc_tid_v variable was not properly initialized when running BIND 9 as a Windows Service, leading to a crash on startup.
* \"map\" files exceeding 2GB in size failed to load due to a size comparison that incorrectly treated the file size as a signed integer. In 9.16.22:
* Remove the \"adjust interface\" mechanism which was responsible for setting up listeners on interfaces when the \"
*-source(-v6)\" address and port were the same as the \"listen-on(-v6)\" address and port. Such a configuration is no longer supported; under certain timing conditions, that mechanism could prevent named from listening on some TCP ports. This has been fixed.
* Multiple library names were mistakenly passed to the krb5-config utility when ./configure was invoked with the --with-gssapi=[/path/to/]krb5-config option. This has been fixed by invoking krb5-config separately for each required library.
* Fixed a regression which broke backward compatibility for the \"check-names master ...\" and \"check-names slave ...\" options. This has been fixed.
* Address a potential deadlock when checking zone content consistency. In 9.16.23:
* Address Coverity warning in lib/dns/dnssec.c.
* Fix a bug when comparing two RSA keys. There was a typo which caused the \"p\" prime factors to not being compared.
* Fix an assertion failure caused by missing member zones during a reload of a catalog zone. This obsoletes bind-CVE-2021-25219.patch and bind-fix-build-with-older-sphinx.patch Other issues: A compile time waring about fall through in a switch statement has been averted by marking the cases as FALLTHROUGH. [bind-9.16.23.tar.xz, bind-9.16.23.tar.xz.sha512.asc, bind-CVE-2021-25219.patch, bind-fix-build-with-older-sphinx.patch, bind-avoid-fallthrough-warning-error.patch]
* Mon Nov 08 2021 Josef Möllers - Aligned SLE15-SP4 and Factory spec files. [bind.spec]
* Thu Nov 04 2021 Josef Möllers - Fixed CVE-2021-25219: The lame-ttl option controls how long named caches certain types of broken responses from authoritative servers (see the security advisory for details). This caching mechanism could be abused by an attacker to significantly degrade resolver performance. The vulnerability has been mitigated by changing the default value of lame-ttl to 0 and overriding any explicitly set value with 0, effectively disabling this mechanism altogether. ISC\'s testing has determined that doing that has a negligible impact on resolver performance while also preventing abuse. Administrators may observe more traffic towards servers issuing certain types of broken responses than in previous BIND 9 releases. [bsc#1192146, CVE-2021-25219, bind-CVE-2021-25219.patch]
* Mon Oct 18 2021 Josef Möllers - Just specifying \"geoip-directory;\" in /etc/named.conf is not correct syntax. Must either put a path name or the string \"none\". Appended the work \"none\" to make it correct syntax.
* Fri Oct 08 2021 Josef Möllers - Added build requirement of libmaxminddb to the spec file Also added an entry for \"geoip-directory\" with the default path to /etc/named.conf. [bsc#1190884, vendor-files/config/named.conf, bind.spec]
* Thu Aug 19 2021 Josef Möllers - Upgrade to 9.16.20 Bugs fixed:
* An assertion failure occurred when named attempted to send a UDP packet that exceeded the MTU size, if Response Rate Limiting (RRL) was enabled. (CVE-2021-25218)
* Zones using KASP and inline-signed zones failed to apply changes from the unsigned zone to the signed zone under certain circumstances.
* \"rndc reload \" could trigger a redundant reload for an inline-signed zone whose zone file was not modified since the last \"rndc reload\".
* named failed to check the opcode of responses when performing zone refreshes, stub zone updates, and UPDATE forwarding.
* Some changes to \"zone-statistics\" settings were not properly processed by \"rndc reconfig\".
* The \"check DS\" code failed to release all resources upon named shutdown when a refresh was in progress.
* Authentication of rndc messages could fail if a \"controls\" statement was configured with multiple key algorithms for the same listener. More changes see CHANGES in the source package. [bsc#1189460, CVE-2021-25218]
* Thu Jul 29 2021 Paolo Stivanin - Update to 9.16.19
* A race condition could occur where two threads were competing for the same set of key file locks, leading to a deadlock. This has been fixed. [GL #2786]
* create_keydata() created an invalid placeholder keydata record upon a refresh failure, which prevented the database of managed keys from subsequently being read back. This has been fixed. [GL #2686]
* KASP support was extended with the \"check DS\" feature. Zones with \"dnssec-policy\" and \"parental-agents\" configured now check for DS presence and can perform automatic KSK rollovers. [GL #1126]
* Rescheduling a setnsec3param() task when a zone failed to load on startup caused a hang on shutdown. This has been fixed. [GL #2791]
* The configuration-checking code failed to account for the inheritance rules of the \"dnssec-policy\" option. This has been fixed. [GL #2780]
* If nsupdate sends an SOA request and receives a REFUSED response, it now fails over to the next available server. [GL #2758]
* For UDP messages larger than the path MTU, named now sends an empty response with the TC (TrunCated) bit set. In addition, setting the DF (Don\'t Fragment) flag on outgoing UDP sockets was re-enabled. [GL #2790]
* Views with recursion disabled are now configured with a default cache size of 2 MB unless \"max-cache-size\" is explicitly set. This prevents cache RBT hash tables from being needlessly preallocated for such views. [GL #2777]
* Change 5644 inadvertently introduced a deadlock: when locking the key file mutex for each zone structure in a different view, the \"in-view\" logic was not considered. This has been fixed. [GL #2783]
* Increasing \"max-cache-size\" for a running named instance (using \"rndc reconfig\") did not cause the hash tables used by cache databases to be grown accordingly. This has been fixed. [GL #2770]
* Signed, insecure delegation responses prepared by named either lacked the necessary NSEC records or contained duplicate NSEC records when both wildcard expansion and CNAME chaining were required to prepare the response. This has been fixed. [GL #2759]
* A bug that caused the NSEC3 salt to be changed on every restart for zones using KASP has been fixed. [GL #2725]
* Wed Jul 21 2021 Josef Möllers - Since BIND 9.9, it has been easier to use tsig-keygen and ddns-confgen to generare TSIG keys. In 9.13, TSIG support was removed from dnssec-keygen, so now it is just for DNSKEY (and KEY for obscure cases). tsig-keygen is now used to generate DDNS keys. [bsc#1187921, vendor-files.tar.bz2]
* Thu Jun 24 2021 Hans-Peter Jansen - Add patch bind-fix-build-with-older-sphinx.patch and sed fix in order to build with older distributions.
* Wed Jun 23 2021 Josef Möllers - Upgrade to 9.16.18
* The configuration-checking code failed to account for the inheritance rules of the \"key-directory\" option.
* When preparing DNS responses, named could replace the letters \'W\' (uppercase) and \'w\' (lowercase) with \'\\000\'. This has been fixed. [bind-9.16.18.tar.xz, bind-9.16.18.tar.xz.sha512.asc]
* Sat Jun 19 2021 Callum Farmer - Add now working CONFIG parameter to sysusers generator
* Thu Jun 17 2021 Josef Möllers - Upgrade to 9.16.17 Major changes (bug fixes):
* A copy-and-paste error caused the IP_DONTFRAG socket option to be enabled instead of disabled. This has been fixed.
* The calculation of the estimated IXFR transaction size in dns_journal_iter_init() was invalid.
* Fix a race condition in reading and writing key files for zones using KASP and configured in multiple views.
* Zones which are configured in multiple views with different values set for \"dnssec-policy\" and with identical values set for \"key-directory\" are now detected and treated as a configuration error.
* Address a potential memory leak in dst_key_fromnamedfile().
* Check that the first and last SOA record of an AXFR are consistent.
* Improvements related to network manager/task manager integration [bind-9.16.17.tar.xz, bind-9.16.17.tar.xz.sha512.asc]
* Fri May 21 2021 Josef Möllers - vendor-files/system/named.prep was missing a $ [bsc#1186278, vendor-files.tar.bz2]
* Thu May 20 2021 Josef Möllers - Upgrade to bind 9.16.16
* Feature Changes + DNSSEC responses containing NSEC3 records with iteration counts greater than 150 are now treated as insecure. [GL #2445] + The maximum supported number of NSEC3 iterations that can be configured for a zone has been reduced to 150. [GL #2642] + The default value of the max-ixfr-ratio option was changed to unlimited, for better backwards compatibility in the stable release series. [GL #2671] + Zones that want to transition from secure to insecure mode without becoming bogus in the process must now have their dnssec-policy changed first to insecure, rather than none. After the DNSSEC records have been removed from the zone, the dnssec-policy can be set to none or removed from the configuration. Setting the dnssec-policy to insecure causes CDS and CDNSKEY DELETE records to be published. [GL #2645] + The implementation of the ZONEMD RR type has been updated to match RFC 8976. [GL #2658] + The draft-vandijk-dnsop-nsec-ttl IETF draft was implemented: NSEC(3) TTL values are now set to the minimum of the SOA MINIMUM value or the SOA TTL. [GL #2347]
* Bug Fixes + It was possible for corrupt journal files generated by an earlier version of named to cause problems after an upgrade. This has been fixed. [GL #2670] + TTL values in cache dumps were reported incorrectly when stale-cache-enable was set to yes. This has been fixed. [GL #389] [GL #2289] + A deadlock could occur when multiple rndc addzone, rndc delzone, and/or rndc modzone commands were invoked simultaneously for different zones. This has been fixed. [GL #2626] + named and named-checkconf did not report an error when multiple zones with the dnssec-policy option set were using the same zone file. This has been fixed. [GL #2603] + If dnssec-policy was active and a private key file was temporarily offline during a rekey event, named could incorrectly introduce replacement keys and break a signed zone. This has been fixed. [GL #2596] + When generating zone signing keys, KASP now also checks for key ID conflicts among newly created keys, rather than just between new and existing ones. [GL #2628]
* Tue May 18 2021 Josef Möllers - In /usr/libexec/bind/named.prep the order of arguments for \"ln -s\" was wrong. [vendor-files/system/named.prep, bsc#1186057]
* Mon May 17 2021 Josef Möllers - \"systemctl reload named\" does not work:
* the \"kill\" command is in /usr/bin, not in /sbin,
* the order of the options/arguments was wrong, and
* the \"-p\" option is wrong (it\'s not like strace\'s \"-p\"). [bsc#1186046, vendor-files/system/named.service]
* Mon May 10 2021 Ferdinand Thiessen - SPEC file: Fixed outdated URL and use secured SourceURLs
* Mon May 03 2021 Josef Möllers - Upgrade to bind 9.16.15 Major changes:
* A specially crafted GSS-TSIG query could cause a buffer overflow in the ISC implementation of SPNEGO. (CVE-2021-25216)
* named crashed when a DNAME record placed in the ANSWER section during DNAME chasing turned out to be the final answer to a client query. (CVE-2021-25215)
* Insufficient IXFR checks could result in named serving a zone without an SOA record at the apex, leading to a RUNTIME_CHECK assertion failure when the zone was subsequently refreshed. This has been fixed by adding an owner name check for all SOA records which are included in a zone transfer. (CVE-2021-25214) More changes see CHANGES in the source package. [bsc#1185345,CVE-2021-25214,CVE-2021-25215,CVE-2021-25216]
* Thu Apr 08 2021 Josef Möllers - Rewrite of named service handling to better cope with systemd protection (see change from Thu Jan 21) by introducing a separate script \"named.prep\" which runs without restrictions prior to starting named. Removed all references to \"lwresd\" as \"The lightweight resolver daemon and library (lwresd and liblwres) have been removed.\" (See CHANGES, item 4707) [bind.spec, vendor-files.tar.bz2]
* Tue Mar 23 2021 Jan Engelhardt - Modernize specfile, and declare /bin/bash as required buildshell (use of {a,b} style expansion).
* Fri Mar 12 2021 Matthias Gerstner - pass PIE compiler and linker flags via environment variables to make /usr/bin/delv in bind-tools also position independent (bsc#1183453).- drop pie_compile.diff: no longer needed, this patch is difficult to maintain, the environment variable approach is less error prone.
* Thu Feb 18 2021 Josef Möllers -
*
*
* MAJOR CHANGES
*
*
*
* The libraries shipped with bind are now named after the bind version (eg libisc-9.16.10.so), not some kind of artificial number (eg libisc.so.1608)!
* For the time being (ie until the next upgrade), new BIND option \"stale-answer-client-timeout\" will be disabled (in /etc/named.conf): \"stale-answer-enable no;\"
* All libraries are now in bind-utils as they are used by bind and bind-utils only and bind requires bind-utils. This affects libdns, libirs, libisc, libisccc, libisccfg, libns
* Dropped the devel packages as the libraries are used internally only.
* Update to 9.16.12 Bugs fixed: - KASP incorrectly set signature validity to the value of the DNSKEY signature validity. - Fix off-by-one bug in ISC SPNEGO implementation. (CVE-2020-8625) - Dig now reports unknown dash options while pre-parsing the options. This prevents \"-multi\" instead of \"+multi\" from reporting memory usage before ending option parsing with \"Invalid option: -lti\". - Fixed a crash in \"dnssec-keyfromlabel\" when using ECDSA keys. - Emit useful error message when \"rndc retransfer\" is applied to a zone of inappropriate type. - Improve performance of the DNSSEC verification code by reducing the number of repeated calls to dns_dnssec_keyfromrdata(). - named failed to start when its configuration included a zone with a non-builtin \"allow-update\" ACL attached. - Address potential double free in generatexml(). - When migrating to KASP, BIND 9 considered keys with the \"Inactive\" and/or \"Delete\" timing metadata to be possible active keys. - Fix the \"three is a crowd\" key rollover bug in KASP by correctly implementing Equation (2) of the \"Flexible and Robust Key Rollover\" paper.
* dnssec-keygen can no longer generate HMAC keys. Use tsig-keygen instead. genDDNSkey script was modified to reflect this. [vendor-files/tools/bind.genDDNSkey, bsc#1180933, CVE-2020-8625, bsc#1182246, bsc#1182483]
* Thu Jan 21 2021 Josef Möllers - Upgrade to version 9.16.11
* Bug fixing (please check CHANGES file in the source RPM)
* Functional change: policy none;\", named now permits a safe transition to insecure mode and publishes the CDS and CDNSKEY DELETE records, as described in RFC 8078. Remove useless Makefiles and Makefile skeleton files in /usr/share/doc/packages/bind/contrib/ [bind.spec, bsc#1179040]
*
*
* MAJOR CHANGE
*
*
* Changed protection of/against \"named\" from chroot jail to systemd protection. This obsoletes subpackage named-chrootenv. Kudos to Matthias Gerstner [bind.spec, bind-chrootenv.conf, vendor-files.tar.bz2, bsc#1180294]
* Tue Dec 29 2020 Dirk Müller - update to 9.16.10: New Features:
* NSEC3 support was added to KASP. A new option for dnssec-policy, nsec3param, can be used to set the desired NSEC3 parameters. NSEC3 salt collisions are automatically prevented during resalting. [GL #1620]
* A new configuration option, stale-refresh-time, has been introduced. It allows a stale RRset to be served directly from cache for a period of time after a failed lookup, before a new attempt to refresh it is made. [GL #2066] Feature Changes:
* The default value of max-recursion-queries was increased from 75 to 100. Since the queries sent towards root and TLD servers are now included in the count (as a result of the fix for CVE-2020-8616), max-recursion-queries has a higher chance of being exceeded by non-attack queries, which is the main reason for increasing its default value. [GL #2305] The default value of nocookie-udp-size was restored back to 4096 bytes. Since max-udp-size is the upper bound for nocookie-udp-size, this change relieves the operator from having to change nocookie-udp-size together with max-udp-size in order to increase the default EDNS buffer size limit. nocookie-udp-size can still be set to a value lower than max-udp-size, if desired. [GL #2250] Bug Fixes: Handling of missing DNS COOKIE responses over UDP was tightened by falling back to TCP. [GL #2275] The CNAME synthesized from a DNAME was incorrectly followed when the QTYPE was CNAME or ANY. [GL #2280] Building with native PKCS#11 support for AEP Keyper has been broken since BIND 9.16.6. This has been fixed. [GL #2315] named could crash with an assertion failure if a TCP connection were closed while a request was still being processed. [GL #2227] named acting as a resolver could incorrectly treat signed zones with no DS record at the parent as bogus. Such zones should be treated as insecure. This has been fixed. [GL #2236] After a Negative Trust Anchor (NTA) is added, BIND performs periodic checks to see if it is still necessary. If BIND encountered a failure while creating a query to perform such a check, it attempted to dereference a NULL pointer, resulting in a crash. [GL #2244] A problem obtaining glue records could prevent a stub zone from functioning properly, if the authoritative server for the zone were configured for minimal responses. [GL #1736] UV_EOF is no longer treated as a TCP4RecvErr or a TCP6RecvErr. [GL #2208]
* Wed Nov 11 2020 Josef Möllers - Added special make instruction for the \"Administrator Reference Manual\" which is built using python3-Sphinx [bsc#1177983, bind.spec]- Removed \"Before=nss-lookup.target\" from named.service as that leads to a systemd ordering cycle [bsc#1177491, bsc#1178626, bsc#1177991, vendor-files.tar.bz2]
* Wed Oct 28 2020 Josef Möllers - Upgrade to version 9.16.8 New Features:
* Add a new rndc command, \"rndc dnssec -rollover\", which triggers a manual rollover for a specific key.
* Add a new rndc command, \"rndc dumpdb -expired\", which dumps the cache database, including expired RRsets that are awaiting cleanup, to the dump-file for diagnostic purposes. Bug Fixes:
* named reported an invalid memory size when running in an environment that did not properly report the number of available memory pages and/or the size of each memory page.
* With multiple forwarders configured, named could fail the REQUIRE(msg->state == (-1)) assertion in lib/dns/message.c, causing it to crash. This has been fixed.
* named erroneously performed continuous key rollovers for KASP policies that used algorithm Ed25519 or Ed448 due to a mismatch between created key size and expected key size.
* Updating contents of an RPZ zone which contained names spelled using varying letter case could cause some processing rules in that RPZ zone to be erroneously ignored. Local changes:
* Add /usr/lib64/named to the files and directories in bind-chrootenv.conf. This directory contains plugins loaded after the chroot(). [bsc#1177913,bsc#1178078,bsc#1177603,bind-chrootenv.conf]
* Fri Oct 23 2020 Josef Möllers - Removed \"dnssec-enable\" from named.conf as it has been obsoleted. Added a comment for reference which should be removed in the future.- Added a comment to the \"dnssec-validation\" in named.conf with a reference to forwarders which do not return signed responses.- Replaced named\'s dependency on time-sync with a dependency on time-set in named.service. [bsc#1177790,bsc#1175894,bsc#1177915,vendor-files.tar.bz2]
* Wed Oct 21 2020 Josef Möllers - Upgrade to version 9.16.7
* Fix (non-)publication of CDS and CDNSKEY records.
* \'dig +bufsize=0\' failed to disable EDNS.
* Address a TSAN report by ensuring each rate limiter object holds a reference to its task.
* With query minimization enabled, named failed to resolve ip6.arpa. names that had extra labels to the left of the IPv6 part.
* Silence the EPROTO syslog message on older systems.
* Fix off-by-one error when calculating new hash table size.
* Tighten LOC parsing to reject a period (\".\") and/or \"m\" as a value. Fix handling of negative altitudes which are not whole meters.
* rbtversion->glue_table_size could be read without the appropriate lock being held.
* Named erroneously accepted certain invalid resource records that were incorrectly processed after subsequently being written to disk and loaded back, as the wire format differed. Such records include: CERT, IPSECKEY, NSEC3, NSEC3PARAM, NXT, SIG, TLSA, WKS, and X25.
* NTA code needed to have a weak reference on its associated view to prevent the latter from being deleted while NTA tests were being performed.
* replace an INSIST() (which calls abort()) with a check and an error message. [bsc#1177913, bind-9.16.7.tar.xz]
* Fri Sep 18 2020 Josef Möllers - Removed \"-r /dev/urandom\" from all invocations of rndc-confgen (init/named system/lwresd.init system/named.init in vendor-files) as this option is deprecated and causes rndc-confgen to fail. [bsc#1173311, bsc#1176674, bsc#1170713, vendor-files.tar.bz2]
* Tue Sep 15 2020 Josef Möllers - /usr/bin/genDDNSkey: Removing the use of the -r option in the call of /usr/sbin/dnssec-keygen as BIND now uses the random number functions provided by the crypto library (i.e., OpenSSL or a PKCS#11 provider) as a source of randomness rather than /dev/random. Therefore the -r command line option no longer has any effect on dnssec-keygen. Leaving the option in genDDNSkey as to not break compatibility. Patch provided by Stefan Eisenwiener. [bsc#1171313, vendor-files.tar.bz2]
* Fri Sep 04 2020 Reinhard Max - Put libns into a separate subpackage to avoid file conflicts in the libisc subpackage due to different sonums (bsc#1176092).
* Fri Aug 28 2020 Dominique Leuenberger - Require /sbin/start_daemon: both init scripts, the one used in systemd context as well as legacy sysv, make use of start_daemon.
* Tue Aug 18 2020 Josef Möllers - Upgrade to version 9.16.6 Fixes five vilnerabilities: 5481. [security] \"update-policy\" rules of type \"subdomain\" were incorrectly treated as \"zonesub\" rules, which allowed keys used in \"subdomain\" rules to update names outside of the specified subdomains. The problem was fixed by making sure \"subdomain\" rules are again processed as described in the ARM. (CVE-2020-8624) [GL #2055] 5480. [security] When BIND 9 was compiled with native PKCS#11 support, it was possible to trigger an assertion failure in code determining the number of bits in the PKCS#11 RSA public key with a specially crafted packet. (CVE-2020-8623) [GL #2037] 5479. [security] named could crash in certain query resolution scenarios where QNAME minimization and forwarding were both enabled. (CVE-2020-8621) [GL #1997] 5478. [security] It was possible to trigger an assertion failure by sending a specially crafted large TCP DNS message. (CVE-2020-8620) [GL #1996] 5476. [security] It was possible to trigger an assertion failure when verifying the response to a TSIG-signed request. (CVE-2020-8622) [GL #2028] For the less severe bugs fixed, see the CHANGES file. [bsc#1175443, CVE-2020-8624, CVE-2020-8623, CVE-2020-8621, CVE-2020-8620, CVE-2020-8622]
* Thu Aug 06 2020 Josef Möllers - Added \"/etc/bind.keys\" to NAMED_CONF_INCLUDE_FILES in /etc/sysconfig/named to suppress warning message re missing file. [vendor-files.tar.bz2, bsc#1173983]
* Tue Jul 21 2020 Josef Möllers - Upgrade to version bind-9.16.5
* The \"primary\" and \"secondary\" keywords, when used as parameters for \"check-names\", were not processed correctly and were being ignored.
* \'rndc dnstap -roll \' did not limit the number of saved files to .
* Add \'rndc dnssec -status\' command.
* Addressed a couple of situations where named could crash For the full list, see the CHANGES file in the source RPM.
* Tue Jun 30 2020 Josef Möllers - Changed /var/lib/named to owner root:named and perms rwxrwxr-t so that named, being a/the only member of the \"named\" group has full r/w access yet cannot change directories owned by root in the case of a compromized named. [bsc#1173307, bind-chrootenv.conf]
* Thu Jun 18 2020 Josef Möllers - Upgrade to version bind-9.16.4 Fixing two security problems:
* It was possible to trigger an INSIST when determining whether a record would fit into a TCP message buffer. (CVE-2020-8618)
* It was possible to trigger an INSIST in lib/dns/rbtdb.c:new_reference() with a particular zone content and query patterns. (CVE-2020-8619) Also the following functional changes:
* Reject DS records at the zone apex when loading master files. Log but otherwise ignore attempts to add DS records at the zone apex via UPDATE.
* The default value of \"max-stale-ttl\" has been changed from 1 week to 12 hours.
* Zone timers are now exported via statistics channel. Thanks to Paul Frieden, Verizon Media. Added support for idn2 to spec file (Thanks to Holger Bruenjes ). More internal changes see the CHANGES file in the source RPM This update obsoletes Makefile.in.diff [bsc#1172958, CVE-2020-8618, CVE-2020-8619, Makefile.in.diff bind.spec]
* Fri May 15 2020 Josef Möllers - Upgrade to version bind-9.16.3 Fixing two security problems:
* Further limit the number of queries that can be triggered from a request. Root and TLD servers are no longer exempt from max-recursion-queries. Fetches for missing name server address records are limited to 4 for any domain. (CVE-2020-8616)
* Replaying a TSIG BADTIME response as a request could trigger an assertion failure. (CVE-2020-8617) Also
* Add engine support to OpenSSL EdDSA implementation.
* Add engine support to OpenSSL ECDSA implementation.
* Update PKCS#11 EdDSA implementation to PKCS#11 v3.0.
* Warn about AXFR streams with inconsistent message IDs.
* Make ISC rwlock implementation the default again. For more see CHANGS file in source RPM. [CVE-2020-8616, CVE-2020-8617, bsc#1171740, bind-9.16.3.tar.xz]
* Fri May 08 2020 Josef Möllers - bind needs an accurate clock, so wait for the time-sync.target to be reached before starting bind. [bsc#1170667, bsc#1170713, vendor-files.tar.bz2]
* Sat Mar 21 2020 Thorsten Kukuk - Use sysusers.d to create named user- Have only one package creating the user
* Fri Mar 20 2020 Thorsten Kukuk - coreutils are not used in %post, remove Requires.- Use systemd_ordering instead of hard requiring systemd
* Fri Mar 20 2020 Josef Möllers - Upgrade to version 9.16.1
* UDP network ports used for listening can no longer simultaneously be used for sending traffic.
* The system-provided POSIX Threads read-write lock implementation is now used by default instead of the native BIND 9 implementation.
* Fixed re-signing issues with inline zones which resulted in records being re-signed late or not at all. [bind-9.16.1.tar.xz]
* Sat Feb 22 2020 Tomáš Chvátal - Update download urls- Do not enable geoip on old distros, the geoip db was shut down so we need to use geoip2 everywhere
* Thu Feb 20 2020 Josef Möllers - Upgrade to version 9.16.0 Major upgrade, see https://downloads.isc.org/isc/bind9/9.16.0/RELEASE-NOTES-bind-9.16.0.html and CHANGES file in the source tree. Major functional change:
* What was set with --with-tuning=large option in older BIND9 versions is now a default, and a --with-tuning=small option was added for small (e.g. OpenWRT) systems.
* A new \"dnssec-policy\" option has been added to named.conf to implement a key and signing policy (KASP) for zones.
* The command (and manpage) bind9-config have been dropped as the BIND 9 libraries are now purely internal. No patches became obsolete through the upgrade. [bind-9.16.0.tar.xz]
* Wed Jan 08 2020 Josef Möllers - Upgrade to bind-9.14.9 bug fixes and feature improvements
* Tue Nov 19 2019 Josef Möllers - Upgrade to version 9.14.8:
* Set a limit on the number of concurrently served pipelined TCP queries.
* Some other bug fixing, see CHANGES file. [CVE-2019-6477, bsc#1157051]
* Fri Nov 08 2019 Josef Möllers - Upgrade to version 9.14.7
* removed dnsperf, idn, nslint, perftcpdns, query-loc-0.4.0, queryperf, sdb, zkt from contrib as they are not supported any more
* Added support for the GeoIP2 API from MaxMind
* See CHANGES file in the source RPM.
* obsoletes bind-CVE-2018-5745.patch (bsc#1126068)
* obsoletes bind-CVE-2019-6465.patch (bsc#1126069)
* obsoletes bind-CVE-2018-5743.patch (bsc#1133185)
* obsoletes bind-CVE-2019-6471.patch (bsc#1138687) [bsc#1111722, bsc#1156205, bsc#1126068, bsc#1126069, bsc#1133185, bsc#1138687, CVE-2019-6476, CVE-2019-6475, CVE-2019-6471, CVE-2018-5743, CVE-2019-6467, CVE-2019-6465, CVE-2018-5745, CVE-2018-5744, CVE-2018-5740, CVE-2018-5738, CVE-2018-5737, CVE-2018-5736, CVE-2017-3145, CVE-2017-3136, configure.in.diff, bind-99-libidn.patch, perl-path.diff, bind-sdb-ldap.patch, bind-CVE-2017-3145.patch, bug-4697-Restore-workaro]und-for-Microsoft-Windows-T.patch, bind-fix-fips.patch, bind-CVE-2018-5745.patch, bind-CVE-2019-6465.patch, bind-CVE-2018-5743.patch, bind-CVE-2019-6471.patch, CVE-2016-6170, bsc#1018700, bsc#1018701, bsc#1018702, bsc#1033466, bsc#1033467, bsc#1033468, bsc#1040039, bsc#1047184, bsc#1104129, bsc#906079, bsc#918330, bsc#936476, bsc#937028, bsc#939567, bsc#977657, bsc#983505, bsc#987866, bsc#989528, fate#320694, fate#324357, bnc#1127583, bnc#1127583, bnc#1109160]
* Fri Jul 12 2019 matthias.gerstnerAATTsuse.com- removal of SuSEfirewall2 service from Factory, since SuSEfirewall2 has been replaced by firewalld, see [1]. [1]: https://lists.opensuse.org/opensuse-factory/2019-01/msg00490.html
* Tue Apr 16 2019 Navin Kukreja - Add FIPS patch back into bind (bsc#1128220)- File: bind-fix-fips.patch
* Mon Dec 10 2018 Franck Bui - Don\'t rely on /etc/insserv.conf anymore for proper dependencies against nss-lookup.target in named.service and lwresd.service (bsc#1118367 bsc#1118368)
* Tue Sep 25 2018 Christophe Giboudeaux - Update named.root. One of the root servers IP has changed.- Install the LICENSE file.
* Fri Jul 06 2018 kukukAATTsuse.de- Add bind.conf and bind-chrootenv.conf to install the default files in /var/lib/named and create chroot environment on systems using transactional-updates [bsc#1100369] [FATE#325524].
* Fri Jun 22 2018 kukukAATTsuse.de- Cleanup pre/post install: remove all old code which was needed to update to SLES8.
* Wed Jun 06 2018 navin.kukrejaAATTsuse.com- Fix a patch error in dnszone-schema file (bsc#901577)
* Tue Jun 05 2018 navin.kukrejaAATTsuse.com- Add SPF records in dnszone-schema file (bsc#901577)
* Tue Jun 05 2018 navin.kukrejaAATTsuse.com- Fix the hostname in ldapdump to be valid (bsc#965748)- Patch file - bind-ldapdump-use-valid-host.patch
* Mon May 21 2018 scabreroAATTsuse.de- Add bug-4697-Restore-workaround-for-Microsoft-Windows-T.patch Fixes dynamic DNS updates against samba and Microsoft DNS servers (bsc#1094236).
* Thu May 17 2018 navin.kukrejaAATTsuse.com- Move chroot related files from bind to bind-chrootenv (bsc#1093338)
* Wed May 16 2018 navin.kukrejaAATTsuse.com- Remove rndc.key generation from bind.spec file because bind should create it on first boot (bsc#1092283)- Add misisng rndc.key check and generation code is lwresd.init script
* Mon Feb 26 2018 sweet_f_aAATTgmx.de- build with --enable-filter-aaaa to make it possible to use config option \"filter-aaaa-on-v4 yes\". Useful to workaround broken websites like netflix which block traffic from certain IPv6 tunnel providers. (bsc#1069633)
* Fri Feb 16 2018 bwiedemannAATTsuse.com- Add /dev/urandom to chroot env
* Wed Feb 07 2018 navin.kukrejaAATTsuse.com- Implement systemd init scripts for bind and lwresd (fate#323155)
* Tue Jan 23 2018 navin.kukrejaAATTsuse.com- Apply bind-CVE-2017-3145.patch to fix CVE-2017-3145 (bsc#1076118)
* Wed Dec 06 2017 vcizekAATTsuse.com- Use getent when adding user/group- update changelog to mention removed options
* Sat Nov 25 2017 meissnerAATTsuse.com- license changed to MPL-2.0 according to legal.
* Thu Nov 23 2017 rbrownAATTsuse.com- Replace references to /var/adm/fillup-templates with new %_fillupdir macro (boo#1069468)
* Wed Nov 22 2017 vcizekAATTsuse.com- Add back init scripts, systemd units aren\'t ready yet
* Tue Nov 21 2017 tchvatalAATTsuse.com- Add python3-bind subpackage to allow python bind interactions
* Tue Nov 21 2017 tchvatalAATTsuse.com- Sync configure options with RH package and remove unused ones
* Enable python3
* Enable gssapi
* Enable dnssec scripts
* Remove no longer recognized --enable-rrl
* Tue Nov 21 2017 tchvatalAATTsuse.com- Drop idnkit from the build, the bind uses libidn since 2007 to run all the resolutions in dig/etc. bsc#1030306- Add patch to make sure we build against system idn:
* bind-99-libidn.patch- Refresh patch:
* pie_compile.diff- Remove patches that are unused due to above:
* idnkit-powerpc-ltconfig.patch
* runidn.diff
* Tue Nov 21 2017 vcizekAATTsuse.com- drop bind-openssl11.patch (merged upstream)
* Fri Nov 17 2017 tchvatalAATTsuse.com- Remove systemd conditionals as we are not building on sle11 anyway- Force the systemd to be base for the initscript deployment
* Wed Nov 15 2017 vcizekAATTsuse.com- Bump up version of most of the libraries- Rename the subpackages to match the version updates- Add macros for easier handling of the library package names- Drop more unneeded patches
* dns_dynamic_db.patch (upstream)
* Tue Nov 14 2017 tchvatalAATTsuse.com- Update to 9.11.2 release:
* Many changes compared to 9.10 see the README file for in-depth listing
* For detailed changes with issues see CHANGES file
* Fixes for CVE-2017-3141 CVE-2017-3140 CVE-2017-3138 CVE-2017-3137 CVE-3136 CVE-2016-9778
* OpenSSL 1.1 support- Remove support for some old distributions and cleanup the spec file to require only what is really needed- Switch to systemd (bsc#1053808)- Remove german from the postinst messages- Remove patches merged upstream:
* bind-CVE-2017-3135.patch
* bind-CVE-2017-3142-and-3143.patch- Refresh named.root with another update
* Mon Nov 13 2017 mpluskalAATTsuse.com- Use python3 by default (fate#323526)
* Mon Sep 11 2017 meissnerAATTsuse.com- bind-openssl11.patch: add a patch for enabling openssl 1.1 support (builds for 1.0 and 1.1 openssl). (bsc#1042635)
* Tue Aug 01 2017 jcnengelAATTgmail.com- Enable JSON statistics
* Fri Jul 14 2017 meissnerAATTsuse.com- named.root: refreshed from internic to 2017060102 (bsc#1048729)
* Mon Jul 03 2017 dimstarAATTopensuse.org- Run systemctl daemon-reload even when this is not build with systemd support: if installing bind on a systemd service and not reloading systemd daemon, then the service \'named\' is not known right after package installation, causing confusion.
* Fri Jun 30 2017 sfleesAATTsuse.de- Added bind-CVE-2017-3142-and-3143.patch to fix a security issue where an attacker with the ability to send and receive messages to an authoritative DNS server was able to circumvent TSIG authentication of AXFR requests. A server that relies solely on TSIG keys for protection with no other ACL protection could be manipulated into (1) providing an AXFR of a zone to an unauthorized recipient and (2) accepting bogus Notify packets. [bsc#1046554, CVE-2017-3142, bsc#1046555, CVE-2017-3143]
* Sat May 20 2017 dimstarAATTopensuse.org- Fix named init script to dynamically find the location of the openssl engines (boo#1040027).
* Mon Mar 20 2017 kukukAATTsuse.de- Add with_systemd define with default off, since we still use init scripts and no systemd units.
* Sat Feb 18 2017 kukukAATTsuse.com- Don\'t require and call insserv if we use systemd
* Wed Feb 15 2017 navin.kukrejaAATTsuse.com- Fix assertion failure or a NULL pointer read for configurations using both DNS64 and RPZ
* CVE-2017-3135, bsc#1024130
* bind-CVE-2017-3135.patch
* Thu Jan 12 2017 sfleesAATTsuse.de- Update to latest release in the 9.10.X series
* Security fixes in 9.10.4
* Duplicate EDNS COOKIE options in a response could trigger an assertion failure. CVE-2016-2088. [RT #41809]
* The resolver could abort with an assertion failure due to improper DNAME handling when parsing fetch reply messages. CVE-2016-1286. [RT #41753]
* Malformed control messages can trigger assertions in named and rndc. CVE-2016-1285. [RT #41666]
* Certain errors that could be encountered when printing out or logging an OPT record containing a CLIENT-SUBNET option could be mishandled, resulting in an assertion failure. CVE-2015-8705. [RT #41397]
* Specific APL data could trigger an INSIST. CVE-2015-8704. [RT #41396]
* Incorrect reference counting could result in an INSIST failure if a socket error occurred while performing a lookup. CVE-2015-8461. [RT#40945]
* Insufficient testing when parsing a message allowed records with an incorrect class to be be accepted, triggering a REQUIRE failure when those records were subsequently cached. CVE-2015-8000. [RT #40987]
* For Features and other fixes in 9.10.4 see https://kb.isc.org/article/AA-01380/0/BIND-9.10.4-Release-Notes.html
* Description of patch changes
* BIND 9.10.4-P5 addresses the security issues described in CVE-2016-9131, CVE-2016-9147 and CVE-2016-9444. [bsc#1018699]
* BIND 9.10.4-P4 addresses the security issue described in CVE-2016-8864.
* BIND 9.10.4-P3 addresses the security issue described in CVE-2016-2776 and addresses an interoperability issue with ECS clients.
* BIND 9.10.4-P2 addresses the security issue described in CVE-2016-2775.
* BIND 9.10.4-P1 addresses Windows installation issues, the %z modifier is not supported under Windows and a race condition in the rbt/rbtdb implementation resulting in named exiting due to assertion failures being detected.
* Following patches removed, fixed upstream
* cve-2016-2776.patch
* cve-2016-8864.patch
* Tue Nov 01 2016 psimonsAATTsuse.com- Apply cve-2016-8864.patch to fix CVE-2016-8864 (bsc#1007829).
* Tue Sep 27 2016 psimonsAATTsuse.com- Apply cve-2016-2776.patch to fix CVE-2016-2776 (bsc#1000362).
* Thu Jun 16 2016 maxAATTsuse.com- Remove the start/stop dependency of named and lwresd on remote-fs to break a service dependency cycle (bsc#947483, bsc#963971).- Make /var/lib/named owned by the named user (bsc#908850, bsc#875691).- Call systemd service macros with the full service name.
* Thu Apr 14 2016 lnusselAATTsuse.de- remove BuildRequire libcap. That is only a legacy library, not actually used for building. libcap-devel pulls in the right one.
* Fri Mar 11 2016 maxAATTsuse.com- Security update 9.10.3-P4:
* CVE-2016-1285, bsc#970072: assert failure on input parsing can cause premature exit.
* CVE-2016-1286, bsc#970073: An error when parsing signature records for DNAME can lead to named exiting due to an assertion failure.
* CVE-2016-2088, bsc#970074: a deliberately misconstructed packet containing multiple cookie options to cause named to terminate with an assertion failure.
* Thu Feb 25 2016 bwiedemannAATTsuse.com- drop a changing timestamp making build reproducible
* Fri Feb 12 2016 crrodriguezAATTopensuse.org- Build with --with-randomdev=/dev/urandom otherwise libisc will use /dev/random to gather entropy and that might block, short read etc..
* Wed Jan 20 2016 maxAATTsuse.com- Security update 9.10.3-P3:
* Specific APL data could trigger an INSIST (CVE-2015-8704, bsc#962189).
* Certain errors that could be encountered when printing out or logging an OPT record containing a CLIENT-SUBNET option could be mishandled, resulting in an assertion failure (CVE-2015-8705, bsc#962190).
* Authoritative servers that were marked as bogus (e.g. blackholed in configuration or with invalid addresses) were being queried anyway.
* Mon Dec 21 2015 maxAATTsuse.com- Update to version 9.10.3-P2 to fix a remote denial of service by misparsing incoming responses (CVE-2015-8000, bsc#958861).
* Sun Oct 04 2015 jengelhAATTinai.de- Avoid double %setup, it confuses some versions of quilt.- Summary/description update
* Tue Sep 22 2015 meissnerAATTsuse.com- Update to version 9.10.2-P4
* An incorrect boundary boundary check in the OPENPGPKEY rdatatype could trigger an assertion failure. (CVE-2015-5986) [RT #40286] (bsc#944107)
* A buffer accounting error could trigger an assertion failure when parsing certain malformed DNSSEC keys. (CVE-2015-5722) [RT #40212] (bsc#944066)
* Wed Jul 29 2015 lmuelleAATTsuse.com- Update to version 9.10.2-P3 Security Fixes
* A specially crafted query could trigger an assertion failure in message.c. This flaw was discovered by Jonathan Foote, and is disclosed in CVE-2015-5477. [RT #39795]
* On servers configured to perform DNSSEC validation, an assertion failure could be triggered on answers from a specially configured server. This flaw was discovered by Breno Silveira Soares, and is disclosed in CVE-2015-4620. [RT #39795] Bug Fixes
* Asynchronous zone loads were not handled correctly when the zone load was already in progress; this could trigger a crash in zt.c. [RT #37573]
* Several bugs have been fixed in the RPZ implementation: + Policy zones that did not specifically require recursion could be treated as if they did; consequently, setting qname-wait-recurse no; was sometimes ineffective. This has been corrected. In most configurations, behavioral changes due to this fix will not be noticeable. [RT #39229] + The server could crash if policy zones were updated (e.g. via rndc reload or an incoming zone transfer) while RPZ processing was still ongoing for an active query. [RT #39415] + On servers with one or more policy zones configured as slaves, if a policy zone updated during regular operation (rather than at startup) using a full zone reload, such as via AXFR, a bug could allow the RPZ summary data to fall out of sync, potentially leading to an assertion failure in rpz.c when further incremental updates were made to the zone, such as via IXFR. [RT #39567] + The server could match a shorter prefix than what was available in CLIENT-IP policy triggers, and so, an unexpected action could be taken. This has been corrected. [RT #39481] + The server could crash if a reload of an RPZ zone was initiated while another reload of the same zone was already in progress. [RT #39649]
* Fri Jul 10 2015 lmuelleAATTsuse.com- Update to version 9.10.2-P2 - An uninitialized value in validator.c could result in an assertion failure. (CVE-2015-4620) [RT #39795]- Update to version 9.10.2-P1 - Include client-ip rules when logging the number of RPZ rules of each type. [RT #39670] - Addressed further problems with reloading RPZ zones. [RT #39649] - Addressed a regression introduced in change #4121. [RT #39611] - The server could match a shorter prefix than what was available in CLIENT-IP policy triggers, and so, an unexpected action could be taken. This has been corrected. [RT #39481] - On servers with one or more policy zones configured as slaves, if a policy zone updated during regular operation (rather than at startup) using a full zone reload, such as via AXFR, a bug could allow the RPZ summary data to fall out of sync, potentially leading to an assertion failure in rpz.c when further incremental updates were made to the zone, such as via IXFR. [RT #39567] - A bug in RPZ could cause the server to crash if policy zones were updated while recursion was pending for RPZ processing of an active query. [RT #39415] - Fix a bug in RPZ that could cause some policy zones that did not specifically require recursion to be treated as if they did; consequently, setting qname-wait-recurse no; was sometimes ineffective. [RT #39229] - Asynchronous zone loads were not handled correctly when the zone load was already in progress; this could trigger a crash in zt.c. [RT #37573] - Fix an out-of-bounds read in RPZ code. If the read succeeded, it doesn\'t result in a bug during operation. If the read failed, named could segfault. [RT #38559]
* Wed May 13 2015 hguoAATTsuse.com- Fix inappropriate use of /var/lib/named for locating dynamic-DB plugins. Dynamic-DB plugins are now loaded from %{_libexecdir}/bind, consistent with openSUSE packaging guideline.- Install additional header files which are helpful to the development of dynamic-DB plugins.
* Fri May 08 2015 lmuelleAATTsuse.com- Depend on systemd macros and sysvinit on post-12.3 only.- Create empty lwresd.conf at build time.- Reduce file list pre-13.1.
* Fri May 08 2015 lmuelleAATTsuse.com- Update to version 9.10.2 - Handle timeout in legacy system test. [RT #38573] - dns_rdata_freestruct could be called on a uninitialised structure when handling a error. [RT #38568] - Addressed valgrind warnings. [RT #38549] - UDP dispatches could use the wrong pseudorandom number generator context. [RT #38578] - Fixed several small bugs in automatic trust anchor management, including a memory leak and a possible loss of key state information. [RT #38458] - \'dnssec-dsfromkey -T 0\' failed to add ttl field. [RT #38565] - Revoking a managed trust anchor and supplying an untrusted replacement could cause named to crash with an assertion failure. (CVE-2015-1349) [RT #38344] - Fix a leak of query fetchlock. [RT #38454] - Fix a leak of pthread_mutexattr_t. [RT #38454] - RPZ could send spurious SERVFAILs in response to duplicate queries. [RT #38510] - CDS and CDNSKEY had the wrong attributes. [RT #38491] - adb hash table was not being grown. [RT #38470]- Update bind.keyring- Update baselibs.conf due to updates to libdns160 and libisc148
* Fri May 08 2015 hguoAATTsuse.com- Enable export libraries to support plugin development. Install DNSSEC root key. Expose new interface for developing dynamic zone database. + dns_dynamic_db.patch
* Tue Feb 10 2015 dvaleevAATTsuse.com- PowerPC can build shared libraries for sure. idnkit-powerpc-ltconfig.patch
* Fri Dec 12 2014 jengelhAATTinai.de- Explicitly BuildRequire systemd-rpm-macros since it is used for lwresd %post etc. Then drop pre-12.x material. Remove configure.in.diff2.
* Thu Dec 11 2014 jengelhAATTinai.de- Corrections to baselibs.conf
* Tue Dec 09 2014 lmuelleAATTsuse.com- Update to version 9.10.1-P1 - A flaw in delegation handling could be exploited to put named into an infinite loop. This has been addressed by placing limits on the number of levels of recursion named will allow (default 7), and the number of iterative queries that it will send (default 50) before terminating a recursive query (CVE-2014-8500); (bnc#908994). The recursion depth limit is configured via the \"max-recursion-depth\" option, and the query limit via the \"max-recursion-queries\" option. [RT #37580] - When geoip-directory was reconfigured during named run-time, the previously loaded GeoIP data could remain, potentially causing wrong ACLs to be used or wrong results to be served based on geolocation (CVE-2014-8680). [RT #37720]; (bnc#908995). - Lookups in GeoIP databases that were not loaded could cause an assertion failure (CVE-2014-8680). [RT #37679]; (bnc#908995). - The caching of GeoIP lookups did not always handle address families correctly, potentially resulting in an assertion failure (CVE-2014-8680). [RT #37672]; (bnc#908995).
* Sun Dec 07 2014 jengelhAATTinai.de- Convert some hard PreReq to leaner Requires(pre).- Typographical and orthographic fixes to description texts.
* Fri Dec 05 2014 Led - Fix bashisms in the createNamedConfInclude script.- Post scripts: remove \'-e\' option of \'echo\' that may be unsupported in some POSIX-compliant shells.
* Fri Dec 05 2014 lmuelleAATTsuse.com- Add openssl engines to the lwresd chroot.- Add /etc/lwresd.conf with attribute ghost to the list of files.- Add /run/lwresd to the list of files of the lwresd package.- Shift /run/named from the chroot sub to the main bind package.- Drop /proc from the chroot as multi CPU systems work fine even without it.
* Thu Dec 04 2014 lmuelleAATTsuse.com- Add a versioned dependency when obsoleting packages.
* Thu Dec 04 2014 lmuelleAATTsuse.com- Remove superfluous obsoletes
*-64bit in the ifarch ppc64 case; (bnc#437293).
* Wed Dec 03 2014 lmuelleAATTsuse.com- Fix gssapi_krb configure time header detection.
* Sun Nov 30 2014 lmuelleAATTsuse.com- Update root zone (dated Nov 5, 2014).
* Sat Nov 29 2014 lmuelleAATTsuse.com- Update to version 9.10.1 - This release addresses the security flaws described in CVE-2014-3214 and CVE-2014-3859.- Update to version 9.10.0 - DNS Response-rate limiting (DNS RRL), which blunts the impact of reflection and amplification attacks, is always compiled in and no longer requires a compile-time option to enable it. - An experimental \"Source Identity Token\" (SIT) EDNS option is now available. - A new zone file format, \"map\", stores zone data in a format that can be mapped directly into memory, allowing significantly faster zone loading. - \"delv\" (domain entity lookup and validation) is a new tool with dig-like semantics for looking up DNS data and performing internal DNSSEC validation. - Improved EDNS(0) processing for better resolver performance and reliability over slow or lossy connections. - Substantial improvement in response-policy zone (RPZ) performance. Up to 32 response-policy zones can be configured with minimal performance loss. - To improve recursive resolver performance, cache records which are still being requested by clients can now be automatically refreshed from the authoritative server before they expire, reducing or eliminating the time window in which no answer is available in the cache. - New \"rpz-client-ip\" triggers and drop policies allowing response policies based on the IP address of the client. - ACLs can now be specified based on geographic location using the MaxMind GeoIP databases. Use \"configure --with-geoip\" to enable. - Zone data can now be shared between views, allowing multiple views to serve the same zones authoritatively without storing multiple copies in memory. - New XML schema (version 3) for the statistics channel includes many new statistics and uses a flattened XML tree for faster parsing. The older schema is now deprecated. - A new stylesheet, based on the Google Charts API, displays XML statistics in charts and graphs on javascript-enabled browsers. - The statistics channel can now provide data in JSON format as well as XML. - New stats counters track TCP and UDP queries received per zone, and EDNS options received in total. - The internal and export versions of the BIND libraries (libisc, libdns, etc) have been unified so that external library clients can use the same libraries as BIND itself. - A new compile-time option, \"configure --enable-native-pkcs11\", allows BIND 9 cryptography functions to use the PKCS#11 API natively, so that BIND can drive a cryptographic hardware service module (HSM) directly instead of using a modified OpenSSL as an intermediary. - The new \"max-zone-ttl\" option enforces maximum TTLs for zones. This can simplify the process of rolling DNSSEC keys by guaranteeing that cached signatures will have expired within the specified amount of time. - \"dig +subnet\" sends an EDNS CLIENT-SUBNET option when querying. - \"dig +expire\" sends an EDNS EXPIRE option when querying. - New \"dnssec-coverage\" tool to check DNSSEC key coverage for a zone and report if a lapse in signing coverage has been inadvertently scheduled. - Signing algorithm flexibility and other improvements for the \"rndc\" control channel. - \"named-checkzone\" and \"named-compilezone\" can now read journal files, allowing them to process dynamic zones. - Multiple DLZ databases can now be configured. Individual zones can be configured to be served from a specific DLZ database. DLZ databases now serve zones of type \"master\" and \"redirect\". - \"rndc zonestatus\" reports information about a specified zone. - \"named\" now listens on IPv6 as well as IPv4 interfaces by default. - \"named\" now preserves the capitalization of names when responding to queries. - new \"dnssec-importkey\" command allows the use of offline DNSSEC keys with automatic DNSKEY management. - New \"named-rrchecker\" tool to verify the syntactic correctness of individual resource records. - When re-signing a zone, the new \"dnssec-signzone -Q\" option drops signatures from keys that are still published but are no longer active. - \"named-checkconf -px\" will print the contents of configuration files with the shared secrets obscured, making it easier to share configuration (e.g. when submitting a bug report) without revealing private information. - \"rndc scan\" causes named to re-scan network interfaces for changes in local addresses. - On operating systems with support for routing sockets, network interfaces are re-scanned automatically whenever they change. - \"tsig-keygen\" is now available as an alternate command name to use for \"ddns-confgen\".- Update to version 9.9.6 New Features - Support for CAA record types, as described in RFC 6844 \"DNS Certification Authority Authorization (CAA) Resource Record\", was added. [RT#36625] [RT #36737] - Disallow \"request-ixfr\" from being specified in zone statements where it is not valid (it is only valid for slave and redirect zones) [RT #36608] - Support for CDS and CDNSKEY resource record types was added. For details see the proposed Informational Internet-Draft \"Automating DNSSEC Delegation Trust Maintenance\" at http://tools.ietf.org/html/draft-ietf-dnsop-delegation-trust-maintainance-14. [RT #36333] - Added version printing options to various BIND utilities. [RT #26057] [RT #10686] - Added a \"no-case-compress\" ACL, which causes named to use case-insensitive compression (disabling change #3645) for specified clients. (This is useful when dealing with broken client implementations that use case-sensitive name comparisons, rejecting responses that fail to match the capitalization of the query that was sent.) [RT #35300] Feature Changes - Adds RPZ SOA to the additional section of responses to clearly indicate the use of RPZ in a manner that is intended to avoid causing issues for downstream resolvers and forwarders [RT #36507] - rndc now gives distinct error messages when an unqualified zone name matches multiple views vs. matching no views [RT #36691] - Improves the accuracy of dig\'s reported round trip times. [RT #36611] - When an SPF record exists in a zone but no equivalent TXT record does, a warning will be issued. The warning for the reverse condition is no longer issued. See the check-spf option in the documentation for details. [RT #36210] - \"named\" will now log explicitly when using rndc.key to configure command channel. [RT #35316] - The default setting for the -U option (setting the number of UDP listeners per interface) has been adjusted to improve performance. [RT #35417] - Aging of smoothed round-trip time measurements is now limited to no more than once per second, to improve accuracy in selecting the best name server. [RT #32909] - DNSSEC keys that have been marked active but have no publication date are no longer presumed to be publishable. [RT #35063] Bug Fixes - The Makefile in bin/python was changed to work around a bmake bug in FreeBSD 10 and NetBSD 6. [RT #36993] (
*
*) - Corrected bugs in the handling of wildcard records by the DNSSEC validator: invalid wildcard expansions could be treated as valid if signed, and valid wildcard expansions in NSEC3 opt-out ranges had the AD bit set incorrectly in responses. [RT #37093] [RT #37072] - When resigning, dnssec-signzone was removing all signatures from delegation nodes. It now retains DS and (if applicable) NSEC signatures. [RT #36946] - The AD flag was being set inappopriately on RPZ responses. [RT #36833] - Updates the URI record type to current draft standard, draft-faltstrom-uri-08, and allows the value field to be zero length [RT #36642] [RT #36737] - RRSIG sets that were not loaded in a single transaction at start up were not being correctly added to re-signing heaps. [RT #36302] - Setting \'-t aaaa\' in .digrc had unintended side-effects. [RT #36452] - A race condition could cause a crash in isc_event_free during shutdown. [RT #36720] - Addresses a race condition issue in dispatch. [RT #36731] - acl elements could be miscounted, causing a crash while loading a config [RT #36675] - Corrects a deadlock between view.c and adb.c. [RT #36341] - liblwres wasn\'t properly handling link-local addresses in nameserver clauses in resolv.conf. [RT #36039] - Buffers in isc_print_vsnprintf were not properly initialized leading to potential overflows when printing out quad values. [RT #36505] - Don\'t call qsort() with a null pointer, and disable the GCC 4.9 \"delete null pointer check\" optimizer option. This fixes problems when using GNU GCC 4.9.0 where its compiler code optimizations may cause crashes in BIND. For more information, see the operational advisory at https://kb.isc.org/article/AA-01167/. [RT #35968] - Fixed a bug that could cause repeated resigning of records in dynamically signed zones. [RT #35273] - Fixed a bug that could cause an assertion failure after forwarding was disabled. [RT #35979] - Fixed a bug that caused SERVFAILs when using RPZ on a system configured as a forwarder. [RT #36060] - Worked around a limitation in Solaris\'s /dev/poll implementation that could cause named to fail to start when configured to use more sockets than the system could accomodate. [RT #35878]- Remove merged rpz2+rl-9.9.5.patch and obsoleted rpz2+rl-9.9.5.patch- Removed pid-path.diff patch as /run/{named,lwresd}/ are used by default.- Update baselibs.conf (added libirs and library interface version updates).
* Fri Nov 14 2014 dimstarAATTopensuse.org- No longer perform gpg validation; osc source_validator does it implicit: + Drop gpg-offline BuildRequires. + No longer execute gpg_verify.