Tom Krizek 0d88cd444b Reproducer for CVE-2023-2911 ... The conditions that trigger the crash: - a stale record is in cache - stale-answer-client-timeout is 0 - multiple clients query for the stale record, enough of them to exceed the recursive-clients quota - the response from the authoritative is sufficiently delayed so that recursive-clients quota is exceeded first The reproducer attempts to simulate this situation. However, it hasn't proven to be 100 % reproducible, especially in CI. When reproducing locally, the priming query also seems to sometimes interfere and prevent the crash. When the reproducer is ran twice, it appears to be more reliable in reproducing the issue. (cherry picked from commit f617512d37)		2023-07-25 10:34:33 +02:00
..
check	deprecate delegation-only and root-delegation only	2023-03-23 14:09:53 -07:00
confgen	Update sources to Clang 15 formatting	2022-11-29 09:14:07 +01:00
delv	Update sources to Clang 15 formatting	2022-11-29 09:14:07 +01:00
dig	dighost.c: don't call check_if_done() twice successively	2023-05-10 11:41:35 +00:00
dnssec	Remove trailing whitespace from all text files	2023-06-13 16:13:16 +02:00
named	Restore the ability to read legacy K*+157+* files	2023-06-29 10:32:10 +10:00
nsupdate	nsupdate: set network manager default timeout values	2023-04-03 16:19:18 +00:00
plugins	Remove 'inst != NULL' from cleanup check in plugin_register	2023-04-05 10:27:52 +10:00
rndc	set the default rndc read timeout to 60 seconds	2023-05-05 11:46:55 +02:00
tests	Reproducer for CVE-2023-2911	2023-07-25 10:34:33 +02:00
tools	named-rrchecker: have fatal cleanup	2023-02-07 11:15:21 +11:00
Makefile.am	Remove native PKCS#11 support	2021-09-09 15:35:39 +02:00