bind9/bin/tests/system/mkeys
Michał Kępień b85007e0a6 Move code handling key loading errors into a common function
Some values returned by dstkey_fromconfig() indicate that key loading
should be interrupted, others do not.  There are also certain subsequent
checks to be made after parsing a key from configuration and the results
of these checks also affect the key loading process.  All of this
complicates the key loading logic.

In order to make the relevant parts of the code easier to follow, reduce
the body of the inner for loop in load_view_keys() to a single call to a
new function, process_key().  Move dstkey_fromconfig() error handling to
process_key() as well and add comments to clearly describe the effects
of various key loading errors.
2019-03-19 17:14:18 +01:00
..
ns1 remove "dnssec-enable" from all system tests 2019-03-14 23:30:13 -07:00
ns2 remove "dnssec-enable" from all system tests 2019-03-14 23:30:13 -07:00
ns3 remove "dnssec-enable" from all system tests 2019-03-14 23:30:13 -07:00
ns4 remove "dnssec-enable" from all system tests 2019-03-14 23:30:13 -07:00
ns5 remove "dnssec-enable" from all system tests 2019-03-14 23:30:13 -07:00
ns6 remove "dnssec-enable" from all system tests 2019-03-14 23:30:13 -07:00
ns7 remove "dnssec-enable" from all system tests 2019-03-14 23:30:13 -07:00
clean.sh Add tests for mkeys with unsupported algorithm 2019-02-20 19:44:33 -08:00
README Add tests for mkeys with unsupported algorithm 2019-02-20 19:44:33 -08:00
setup.sh Add tests for mkeys with unsupported algorithm 2019-02-20 19:44:33 -08:00
tests.sh Move code handling key loading errors into a common function 2019-03-19 17:14:18 +01:00

Copyright (C) Internet Systems Consortium, Inc. ("ISC")

See COPYRIGHT in the source root or http://isc.org/copyright.html for terms.

This is for testing managed-keys, in particular with problems
with RFC 5011 Automated Updates of DNSSEC Trust Anchors.

ns1 is the root server that offers new KSKs and hosts one record for
testing. The TTL for the zone's records is 2 seconds.

ns2 is a validator that uses managed-keys.  "-T mkeytimers=2/20/40"
is used so it will attempt do automated updates frequently. "-T tat=1"
is used so it will send TAT queries once per second.

ns3 is a validator with a broken key in managed-keys.

ns4 is a validator with a deliberately broken managed-keys.bind and
managed-keys.jnl, causing RFC 5011 initialization to fail.

ns5 is a validator which is prevented from getting a response from the
root server, causing key refresh queries to fail.

ns6 is a validator which has unsupported algorithms, one at start up,
one because of an algorithm rollover.