This bug was fixed in the package bind9 - 1:9.18.18-0ubuntu0.23.04.1
---------------
bind9 (1:9.18.18-0ubuntu0.23.04.1) lunar; urgency=medium
* New upstream release 9.18.18 (LP: #2028413)
- Updates:
+ Mark a primary server as temporarily unreachable when a TCP connection
response to an SOA query times out, matching behavior of a refused TCP
connection.
+ Mark dialup and heartbeat-interval options as deprecated.
+ Retry DNS queries without an EDNS COOKIE when the first response is
FORMERR with the EDNS COOKIE that was sent originally.
+ Use NS records for the relaxed QNAME minimization mode to reduce the
number of queries from named.
+ Mark TKEY mode 2 as deprecated.
+ Mark delegation-only and root-delegation-only as deprecated.
+ Run RPZ and catalog zone updates on specialized offload threads to
reduce blocked query processing time.
- Bug Fixes:
+ Fix assertion failure from processing already-queued queries while
server is being reconfigured or cache is being flushed.
+ Fix failure to load zones containing resource records with a TTL value
larger than 86400 seconds when dnssec-policy is set to insecure.
+ Fix the ability to read HMAC-MD5 key files (LP: #2015176).
+ Fix stability issues with the catalog zone implementation.
+ Fix bind9 getting stuck when listen-on statement for HTTP is removed
from configuration.
+ Do not return delegation from cache after stale-answer-client-timeout.
+ Fix failure to auto-tune clients-per-query limit in some situations.
+ Fix proper timeouts when using max-transfer-time-in and
max-transfer-idle-in statements.
+ Bring rndc read timeout back to 60 seconds from 30.
+ Treat libuv returning ISC_R_INVALIDPROTO as a network error.
+ Clean up empty-non-terminal NSEC3 records.
+ Fix log file rotation cleanup for absolute file path destinations.
+ Fix various catalog zone processing crashes.
+ Fix transfer hang when downloading large zones over TLS.
+ Fix named crash when adding a new zone into the configuration file for
a name which was already configured as member zone for a catalog zone.
+ Delay DNSSEC key queries until all zones have finished loading.
- See https://bind9.readthedocs.io/en/v9.18.18/notes.html for additional
information.
* d/p/CVE-2023-2828.patch, CVE-2023-2911.patch: Remove - fixed upstream in
9.18.16.
* d/p/CVE-2023-3341.patch: Refresh, matching upstream, to apply in 9.18.18.
* d/t/control, d/t/dyndb-ldap: add DEP8 test (LP: #2032650)
-- Lena Voytek <lena.voy...@canonical.com> Wed, 20 Sep 2023 14:52:27
-0700
** Changed in: bind9 (Ubuntu Lunar)
Status: Fix Committed => Fix Released
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2828
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-2911
** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-3341
--
You received this bug notification because you are a member of FreeIPA,
which is subscribed to bind-dyndb-ldap in Ubuntu.
https://bugs.launchpad.net/bugs/2028413
Title:
MRE updates of bind9 for focal, jammy and lunar
Status in bind-dyndb-ldap package in Ubuntu:
Fix Released
Status in bind9 package in Ubuntu:
Fix Released
Status in bind-dyndb-ldap source package in Focal:
Triaged
Status in bind9 source package in Focal:
Triaged
Status in bind-dyndb-ldap source package in Jammy:
Fix Released
Status in bind9 source package in Jammy:
Fix Released
Status in bind-dyndb-ldap source package in Lunar:
Fix Released
Status in bind9 source package in Lunar:
Fix Released
Bug description:
This bug tracks an update for the bind9 package, moving to versions:
* lunar (23.04): bind9 9.18.18
* jammy (22.04): bind9 9.18.18
* focal (20.04): bind9 9.16.43
These updates include bug fixes following the SRU policy exception
defined at https://wiki.ubuntu.com/Bind9Updates.
[Upstream changes]
9.18.13-9.18.18 for lunar and jammy:
Updates:
Mark a primary server as temporarily unreachable when a TCP connection
response to an SOA query times out, matching behavior of a refused TCP
connection.
Mark dialup and heartbeat-interval options as deprecated.
Retry DNS queries without an EDNS COOKIE when the first response is FORMERR
with the EDNS COOKIE that was sent originally.
Use NS records for the relaxed QNAME minimization mode to reduce the number
of queries from named.
Mark TKEY mode 2 as deprecated.
Mark delegation-only and root-delegation-only as deprecated.
Run RPZ and catalog zone updates on specialized offload threads to reduce
blocked query processing time.
Bug Fixes:
Fix assertion failure from processing already-queued queries while server is
being reconfigured or cache is being flushed.
Fix failure to load zones containing resource records with a TTL value larger
than 86400 seconds when dnssec-policy is set to insecure.
Fix the ability to read HMAC-MD5 key files (LP: #2015176).
Fix stability issues with the catalog zone implementation.
Fix bind9 getting stuck when listen-on statement for HTTP is removed from
configuration.
Do not return delegation from cache after stale-answer-client-timeout.
Fix failure to auto-tune clients-per-query limit in some situations.
Fix proper timeouts when using max-transfer-time-in and max-transfer-idle-in
statements.
Bring rndc read timeout back to 60 seconds from 30.
Treat libuv returning ISC_R_INVALIDPROTO as a network error.
Clean up empty-non-terminal NSEC3 records.
Fix log file rotation cleanup for absolute file path destinations.
Fix various catalog zone processing crashes.
Fix transfer hang when downloading large zones over TLS.
Fix named crash when adding a new zone into the configuration file for a name
which was already configured as a member zone for a catalog zone.
Delay DNSSEC key queries until all zones have finished loading.
CVE Fixes - already available as patches:
CVE-2023-2828
CVE-2023-2911
For full release notes, see:
https://bind9.readthedocs.io/en/v9.18.18/notes.html#notes-for-
bind-9-18-18
While there are behavioral changes in this release, I was unable to
find any backwards-incompatible changes. Some features were marked as
deprecated, but are still usable as they were before. Other changes
are related to performance and timeout management, neither of which
should change how bind9 works, but are worth keeping an eye on in case
any regressions arise.
[Test Plan]
DEP-8 test results:
simpletest PASS
validation FLAKY non-zero exit status 1
zonetest PASS
dyndb-ldap PASS
validation is known to be broken in its current state, both due to a
need for internet access and incorrect output checking, so the failure
is expected.
[Other Information]
Note to SRU team: this update must happen together with src:bind-dyndb-ldap,
and in a particular order:
- first src:bind9 must be accepted
- once src:bind9 is fully built in all architectures, *then*
src:bind-dyndb-ldap can be accepted. In other words, src:bind-dyndb-ldap must
build with the new src:bind9 version.
- it is expected that until both packages are in proposed and built in the
correct order, DEP8 tests will fail. That's our safeguard against mistakenly
releasing them out of sync
[Regression Potential]
Upstream has an extensive build and integration test suite. So
regressions would likely arise from a change in interaction with
Ubuntu-specific integrations.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bind-dyndb-ldap/+bug/2028413/+subscriptions
_______________________________________________
Mailing list: https://launchpad.net/~freeipa
Post to : freeipa@lists.launchpad.net
Unsubscribe : https://launchpad.net/~freeipa
More help : https://help.launchpad.net/ListHelp
