Debian Patches
Status for bind9/1:9.16.50-1~deb11u3
| Patch | Description | Author | Forwarded | Bugs | Origin | Last update |
|---|---|---|---|---|---|---|
| 0001-Add_--install-layout=deb_to_setup.py_call.patch | Add_--install-layout=deb_to_setup.py_call | Debian DNS Packaging <pkg-dns-devel@lists.alioth.debian.org> | no | 2017-11-24 | ||
| 0002-python-fix-for-dist-packages.patch | python fix for dist-packages | Jim Popovitch <jimpop@domainmail.org> | no | 2019-07-13 | ||
| 0003-Remove-the-reference-to-OPTIONS.md-it-breaks-build-o.patch | Remove the reference to OPTIONS.md - it breaks build on Debian stretch | =?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@debian.org> | no | 2022-03-16 | ||
| 0004-Disable-treat-warnings-as-errors-in-sphinx-build.patch | Disable treat-warnings-as-errors in sphinx-build | =?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@debian.org> | no | 2022-05-18 | ||
| 0005-Add-a-limit-to-the-number-of-RRs-in-RRSets.patch | Add a limit to the number of RRs in RRSets Previously, the number of RRs in the RRSets were internally unlimited. As the data structure that holds the RRs is just a linked list, and there are places where we just walk through all of the RRs, adding an RRSet with huge number of RRs inside would slow down processing of said RRSets. The fix for end-of-life branches make the limit compile-time only for simplicity and the limit can be changed at the compile time by adding following define to CFLAGS: -DDNS_RDATASET_MAX_RECORDS=<limit> (cherry picked from commit c5c4d00c38530390c9e1ae4c98b65fbbadfe9e5e) |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-03-01 | ||
| 0006-Add-a-limit-to-the-number-of-RR-types-for-single-nam.patch | Add a limit to the number of RR types for single name Previously, the number of RR types for a single owner name was limited only by the maximum number of the types (64k). As the data structure that holds the RR types for the database node is just a linked list, and there are places where we just walk through the whole list (again and again), adding a large number of RR types for a single owner named with would slow down processing of such name (database node). Add a hard-coded limit (100) to cap the number of the RR types for a single owner. The limit can be changed at the compile time by adding following define to CFLAGS: -DDNS_RBTDB_MAX_RTYPES=<limit> |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-05-29 | ||
| 0007-Expand-the-list-of-the-priority-types.patch | Expand the list of the priority types Add HTTPS, SVCB, SRV, PTR, NAPTR, DNSKEY and TXT records to the list of the priority types that are put at the beginning of the slabheader list for faster access and to avoid eviction when there are more types than the max-types-per-name limit. (cherry picked from commit b27c6bcce894786a8e082eafd59eccbf6f2731cb) |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-06-17 | ||
| 0008-Make-the-resolver-qtype-ANY-test-order-agnostic.patch | Make the resolver qtype ANY test order agnostic Instead of relying on a specific order of the RR types in the databases pick the first RR type as returned from the cache. (cherry picked from commit 58f660cf2b800963fa649bc9823a626009db3a7e) |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-06-17 | ||
| 0009-Be-smarter-about-refusing-to-add-many-RR-types-to-th.patch | Be smarter about refusing to add many RR types to the database Instead of outright refusing to add new RR types to the cache, be a bit smarter: 1. If the new header type is in our priority list, we always add either positive or negative entry at the beginning of the list. 2. If the new header type is negative entry, and we are over the limit, we mark it as ancient immediately, so it gets evicted from the cache as soon as possible. 3. Otherwise add the new header after the priority headers (or at the head of the list). 4. If we are over the limit, evict the last entry on the normal header list. (cherry picked from commit 57cd34441a1b4ecc9874a4a106c2c95b8d7a3120) |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-06-17 | ||
| 0010-Remove-support-for-SIG-0-message-verification.patch | Remove support for SIG(0) message verification (cherry picked from commit 857fd5c346e3309ee8e280c29174b46579af5a13) |
=?utf-8?b?UGV0ciDFoHBhxI1law==?= <pspacek@isc.org> | no | 2024-05-16 | ||
| 0011-Document-SIG-0-verification-removal.patch | Document SIG(0) verification removal (cherry picked from commit 654ba34d80b8b6ed805461d7ada2466f8c19a6f1) |
=?utf-8?b?UGV0ciDFoHBhxI1law==?= <pspacek@isc.org> | no | 2024-05-16 | ||
| 0012-Enable-stdout-autoflush-in-authsock.pl.patch | Enable stdout autoflush in authsock.pl With enabled buffering the output gets lost when the process receives a TERM signal. Disable the buffering. (cherry picked from commit a0311dfb6e2a51f89dfa8b200b96a0f4675fb654) |
Aram Sargsyan <aram@isc.org> | no | 2024-05-21 | ||
| 0013-Adapt-the-tsiggss-test-to-the-SIG-0-removal.patch | Adapt the tsiggss test to the SIG(0) removal Test that SIG(0) signer is NOT sent to the external socket for authorization. It MUST NOT be considered a valid signature by any chance. Also check that the signer's name does not appear in authsock.pl output. (cherry picked from commit cf8838085905171fbc00747eb210e8b8284ca0e1) |
=?utf-8?b?UGV0ciDFoHBhxI1law==?= <pspacek@isc.org> | no | 2024-05-17 | ||
| 0014-Adapt-the-upforwd-test-to-the-SIG-0-removal.patch | Adapt the upforwd test to the SIG(0) removal Change the check so that update with SIG(0) is expected to fail. (cherry picked from commit 5f7558f6dbb0527c08caf281299245ab8de268cd) |
Aram Sargsyan <aram@isc.org> | no | 2024-05-21 | ||
| 0015-Clear-qctx-zversion.patch | Clear qctx->zversion Clear qctx->zversion when clearing qctx->zrdataset et al in lib/ns/query.c:qctx_freedata. The uncleared pointer could lead to an assertion failure if zone data needed to be re-saved which could happen with stale data support enabled. (cherry picked from commit 179fb3532ab8d4898ab070b2db54c0ce872ef709) |
Mark Andrews <marka@isc.org> | no | 2024-01-16 | ||
| 0016-Clear-DNS_FETCHOPT_TRYSTALE_ONTIMEOUT.patch | Clear DNS_FETCHOPT_TRYSTALE_ONTIMEOUT When calling dns_resolver_createfetch in resolver.c with a callback of resume_dslookup, clear DNS_FETCHOPT_TRYSTALE_ONTIMEOUT from options as DNS_EVENT_TRYSTALE is not an expected event type and triggers a REQUIRE. (cherry picked from commit 6faea6da3d646557d234d63ddd5d524d222e8082) |
Mark Andrews <marka@isc.org> | no | 2024-04-03 | ||
| 0017-Add-a-limit-to-the-number-of-RRs-in-RRSets.patch | Add a limit to the number of RRs in RRSets Previously, the number of RRs in the RRSets were internally unlimited. As the data structure that holds the RRs is just a linked list, and there are places where we just walk through all of the RRs, adding an RRSet with huge number of RRs inside would slow down processing of said RRSets. Add a configurable limit to cap the number of the RRs in a single RRSet. This is enforced at the database (rbtdb, qpzone, qpcache) level and configured with new max-records-per-type configuration option that can be configured globally, per-view and per-zone. (cherry picked from commit 3fbd21f69a1bcbd26c4c00920e7b0a419e8762fc) |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-03-01 | ||
| 0018-Add-test-for-not-loading-and-not-transfering-huge-RR.patch | Add test for not-loading and not-transfering huge RRSets Add two new masterformat tests - the 'huge' zone fits within the ns1 limit and loads on the primary ns1 server, but must not transfer to the ns2 secondary, and the 'uber' zone should not even load on the primary ns1 server. (cherry picked from commit cee9ad81db6e5a1167b311e5c2f42cf65ba457cd) |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-05-23 | ||
| 0019-Add-a-test-for-not-caching-large-RRset.patch | Add a test for not caching large RRset Send a recursive query for a large (2500 record) RRset, which should fail when using the default max-records-per-type setting of 100, but succeed when the cap is disabled. (cherry picked from commit 8e3efb4e06ba68cc3f9bc5be2bacb2596bd74cb3) |
Evan Hunt <each@isc.org> | no | 2024-05-23 | ||
| 0020-Disable-Windows-checks-in-the-misc-job.patch | Disable Windows checks in the misc job We don't care about the Windows symbols not the Windows configure anymore. |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-07-29 | ||
| 0021-Add-a-limit-to-the-number-of-RR-types-for-single-nam.patch | Add a limit to the number of RR types for single name Previously, the number of RR types for a single owner name was limited only by the maximum number of the types (64k). As the data structure that holds the RR types for the database node is just a linked list, and there are places where we just walk through the whole list (again and again), adding a large number of RR types for a single owner named with would slow down processing of such name (database node). Add a configurable limit to cap the number of the RR types for a single owner. This is enforced at the database (rbtdb, qpzone, qpcache) level and configured with new max-types-per-name configuration option that can be configured globally, per-view and per-zone. (cherry picked from commit 00d16211d6368b99f070c1182d8c76b3798ca1db) |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-05-25 | ||
| 0022-fix-a-memory-leak-that-could-occur-when-signing.patch | fix a memory leak that could occur when signing when signatures were not added because of too many types already existing at a node, the diff was not being cleaned up; this led to a memory leak being reported at shutdown. (cherry picked from commit 2825bdb1ae5be801e7ed603ba2455ed9a308f1f7) |
Evan Hunt <each@isc.org> | no | 2024-05-31 | ||
| 0023-Be-smarter-about-refusing-to-add-many-RR-types-to-th.patch | Be smarter about refusing to add many RR types to the database Instead of outright refusing to add new RR types to the cache, be a bit smarter: 1. If the new header type is in our priority list, we always add either positive or negative entry at the beginning of the list. 2. If the new header type is negative entry, and we are over the limit, we mark it as ancient immediately, so it gets evicted from the cache as soon as possible. 3. Otherwise add the new header after the priority headers (or at the head of the list). 4. If we are over the limit, evict the last entry on the normal header list. (cherry picked from commit 57cd34441a1b4ecc9874a4a106c2c95b8d7a3120) |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-06-17 | ||
| 0024-Add-a-test-for-not-caching-large-number-of-RRsets.patch | Add a test for not caching large number of RRsets Send a recursive query for a large number of RRsets, which should fail when using the default max-types-per-name setting of 100, but succeed when the cap is disabled. (cherry picked from commit 7e4530f847c8dc541c5e5bf9f790deed520aaa16) |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-05-28 | ||
| 0025-Add-test-for-not-loading-many-RRsets-per-name-on-a-s.patch | Add test for not-loading many RRsets per name on a secondary This tests makes sure the zone with many RRsets per name is not loaded via XFR on the secondary server. (cherry picked from commit 4cfeed912a5e7440f04cb088a461ff47305da2e7) |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-05-28 | ||
| 0026-Test-variable-rename-a-rrcount.patch | Test variable rename a->rrcount (cherry picked from commit 338b45ae713cded921fd3e5494ca38bd59ff9ee8) |
=?utf-8?b?UGV0ciDFoHBhxI1law==?= <pspacek@isc.org> | no | 2024-05-29 | ||
| 0027-Test-variable-rename-i-_attempt.patch | Test variable rename i->_attempt (cherry picked from commit 13417eb277cc8a30ee4ddbb6fc02442b0d8e6d3c) |
=?utf-8?b?UGV0ciDFoHBhxI1law==?= <pspacek@isc.org> | no | 2024-05-29 | ||
| 0028-Test-owner-name-rename-a-b-c-d-e-number-txt.patch | Test owner name rename: a b c d e -> <number>-txt (cherry picked from commit 6ce03f75d1935c2e1991e9c0a01c49b0099a58cb) |
=?utf-8?b?UGV0ciDFoHBhxI1law==?= <pspacek@isc.org> | no | 2024-05-29 | ||
| 0029-masterformat-rename-zone-names-to-reflect-intended-m.patch | masterformat: rename zone names to reflect intended meaning (cherry picked from commit d34bfb1eeaa2f8faab80b1620b992b5495e6f88c) |
=?utf-8?b?UGV0ciDFoHBhxI1law==?= <pspacek@isc.org> | no | 2024-05-29 | ||
| 0030-Remove-duplicated-empty-zone-files.patch | Remove duplicated empty zone files (cherry picked from commit 1456b4fc7778b851256107dbc79fb67d45f752f5) |
=?utf-8?b?UGV0ciDFoHBhxI1law==?= <pspacek@isc.org> | no | 2024-05-29 | ||
| 0031-Log-error-when-update-fails.patch | Log error when update fails The new "too many records" error can make an update fail without the error being logged. This commit fixes that. (cherry picked from commit 558923e5405894cf976d102f0d246a28bdbb400c) |
Matthijs Mekking <matthijs@isc.org> | no | 2024-06-03 | ||
| 0032-Add-more-tests-for-adding-many-RR-types-to-the-datab.patch | Add more tests for adding many RR types to the database More reclimit tests that test various scenarios adding combinations of priority and non-priority RR types into the database. |
=?utf-8?b?T25kxZllaiBTdXLDvQ==?= <ondrej@isc.org> | no | 2024-06-17 | ||
| 0033-Limit-the-additional-processing-for-large-RDATA-sets.patch | Limit the additional processing for large RDATA sets When answering queries, don't add data to the additional section if the answer has more than 13 names in the RDATA. This limits the number of lookups into the database(s) during a single client query, reducing query processing load. Also, don't append any additional data to type=ANY queries. The answer to ANY is already big enough. |
Ondřej Surý <ondrej@isc.org> | no | upstream, https://gitlab.isc.org/isc-projects/bind9/-/commit/9dc22c65e813c3e16781fb34a5199c6124938c1b |
Showing 1 to 33 of 33 entries
All known versions for source package 'bind9'
- 1:9.21.6-1 (experimental)
- 1:9.20.7-1 (sid, trixie)
- 1:9.18.33-1~deb12u2 (bookworm, bookworm-security)
- 1:9.18.24-1~bpo11+1 (bullseye-backports)
- 1:9.16.50-1~deb11u3 (bullseye-security)
- 1:9.16.50-1~deb11u2 (bullseye)