From 4fd679054f940fe5bf49a424f6d2863d2404ec3e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Nicki=20K=C5=99=C3=AD=C5=BEek?= Date: Tue, 11 Jun 2024 10:10:01 +0200 Subject: [PATCH] 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. --- CHANGES | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/CHANGES b/CHANGES index 626c497404..9bf06426d0 100644 --- a/CHANGES +++ b/CHANGES @@ -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