Use a dedicated CHANGES entry for SIG(0) removal

As opposed to the main branch (where the SIG(0) was changed), it has
been removed from the maintenance branches. Use a different changes
number to indicate there was a different solution of the issue.
This commit is contained in:
Nicki Křížek 2024-06-11 10:10:01 +02:00
parent ec3e15da3a
commit 4fd679054f
No known key found for this signature in database
GPG key ID: 01623B9B652A20A7

View file

@ -1,10 +1,10 @@
6404. [security] Remove SIG(0) support from named as a countermeasure
for CVE-2024-1975. [GL #4480]
6403. [security] qctx-zversion was not being cleared when it should have
been leading to an assertion failure if it needed to be
reused. (CVE-2024-4076) [GL #4507]
6402. [security] Remove SIG(0) support from named as a countermeasure
for CVE-2024-1975. [GL #4480]
6401. [security] An excessively large number of rrtypes per owner can
slow down database query processing, so a limit has been
placed on the number of rrtypes that can be stored per