Ondřej Surý dcd1f5b842 Remove dnssec-must-be-secure feature ... The dnssec-must-be-secure feature was added in the early days of BIND 9 and DNSSEC and it makes sense only as a debugging feature. There are no reasons to keep this feature in the production code anymore. Remove the feature to simplify the code.		2024-12-09 13:10:21 +01:00
..
bar.db.in	Remove dnssec-must-be-secure feature	2024-12-09 13:10:21 +01:00
child.nsec3.example.db.in	Alter autosign system test	2023-07-20 11:04:23 +02:00
child.optout.example.db.in	Alter autosign system test	2023-07-20 11:04:23 +02:00
dst.example.db.in	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
example.db.in	Remove dnssec-must-be-secure feature	2024-12-09 13:10:21 +01:00
insecure.secure.example.db.in	Alter autosign system test	2023-07-20 11:04:23 +02:00
keygen.sh	revise test for ENT NSEC3 cleanup	2024-03-06 10:49:02 +01:00
named.conf.in	change allow-transfer default to "none"	2024-06-05 10:50:06 -07:00
nsec3-with-ent.db.in	revise test for ENT NSEC3 cleanup	2024-03-06 10:49:02 +01:00
private.secure.example.db.in	Update the copyright information in all files in the repository	2022-01-11 09:05:02 +01:00
Xbar.+013+59973.key	autosign: use FIPS compatible algorithms and key sizes	2022-08-09 16:22:19 +02:00
Xbar.+013+59973.private	autosign: use FIPS compatible algorithms and key sizes	2022-08-09 16:22:19 +02:00
Xbar.+013+60101.key	autosign: use FIPS compatible algorithms and key sizes	2022-08-09 16:22:19 +02:00
Xbar.+013+60101.private	autosign: use FIPS compatible algorithms and key sizes	2022-08-09 16:22:19 +02:00