Bug 2216462
| Summary: | bind-9.18.16 is available | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Upstream Release Monitoring <upstream-release-monitoring> | ||||
| Component: | bind | Assignee: | Petr Menšík <pemensik> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | rawhide | CC: | anon.amish, customercare, dns-sig, mruprich, pemensik, vonsch, zdohnal | ||||
| Target Milestone: | --- | Keywords: | FutureFeature, Reopened, Security, SecurityTracking, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| URL: | https://downloads.isc.org/isc/bind9/9.18.16/doc/arm/html/notes.html#notes-for-bind-9-18-16 | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | bind-9.18.16-1.fc39 bind-9.18.16-1.fc38 bind-9.18.16-1.fc37 | Doc Type: | If docs needed, set a value | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2023-06-25 00:50:12 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | 2216627, 2216630 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Upstream Release Monitoring
2023-06-21 13:57:09 UTC
Created attachment 1971891 [details]
Update to 9.18.16 (#2216462)
the-new-hotness/release-monitoring.org's scratch build of bind-9.18.16-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=102421701 No change seems needed, this brings few bug fixes and vulnerability fixes as well. --- 9.18.16 released --- 6192. [security] A query that prioritizes stale data over lookup triggers a fetch to refresh the stale data in cache. If the fetch is aborted for exceeding the recursion quota, it was possible for 'named' to enter an infinite callback loop and crash due to stack overflow. This has been fixed. (CVE-2023-2911) [GL #4089] 6190. [security] Improve the overmem cleaning process to prevent the cache going over the configured limit. (CVE-2023-2828) [GL #4055] 6188. [performance] Reduce memory consumption by allocating properly sized send buffers for stream-based transports. [GL #4038] 6186. [bug] Fix a 'clients-per-query' miscalculation bug. When the 'stale-answer-enable' options was enabled and the 'stale-answer-client-timeout' option was enabled and larger than 0, named was taking two places from the 'clients-per-query' limit for each client and was failing to gradually auto-tune its value, as configured. [GL #4074] 6185. [func] Add "ClientQuota" statistics channel counter, which indicates the number of the resolver's spilled queries due to reaching the clients per query quota. [GL !7978] 6183. [bug] Fix a serve-stale bug where a delegation from cache could be returned to the client. [GL #3950] 6182. [cleanup] Remove configure checks for epoll, kqueue and /dev/poll. [GL #4098] 6181. [func] The "tkey-dhkey" option has been deprecated; a warning will be logged when it is used. In a future release, Diffie-Hellman TKEY mode will be removed. [GL #3905] 6180. [bug] The session key object could be incorrectly added to multiple different views' keyrings. [GL #4079] 6179. [bug] Fix an interfacemgr use-after-free error in zoneconf.c:isself(). [GL #3765] 6176. [test] Add support for using pytest & pytest-xdist to execute the system test suite. [GL #3978] 6174. [bug] BIND could get stuck on reconfiguration when a 'listen' statement for HTTP is removed from the configuration. That has been fixed. [GL #4071] 6173. [bug] Properly process extra "nameserver" lines in resolv.conf otherwise the next line is not properly processed. [GL #4066] 6169. [bug] named could crash when deleting inline-signing zones with "rndc delzone". [GL #4054] 6165. [bug] Fix a logic error in dighost.c which could call the dighost_shutdown() callback twice and cause problems if the callback function was not idempotent. [GL #4039] FEDORA-2023-c0ff5a2f68 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-c0ff5a2f68 FEDORA-2023-8e1ddb1fa2 has been submitted as an update to Fedora 38. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8e1ddb1fa2 FEDORA-2023-1d526d551c has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2023-1d526d551c FEDORA-2023-c0ff5a2f68 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-8e1ddb1fa2 has been pushed to the Fedora 38 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-8e1ddb1fa2` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8e1ddb1fa2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-1d526d551c has been pushed to the Fedora 37 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-1d526d551c` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-1d526d551c See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-8e1ddb1fa2 has been pushed to the Fedora 38 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2023-1d526d551c has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. *** Bug 2218464 has been marked as a duplicate of this bug. *** |