bind9/bin/tests/system/mkeys
Tom Krizek 2f5bf6d971
Add pytest functions for shell system tests
In order to run the shell system tests, the pytest runner has to pick
them up somehow. Adding an extra python file with a single function
for the shell tests for each system test proved to be the most
compatible way of running the shell tests across older pytest/xdist
versions.

Modify the legacy run.sh script to ignore these pytest-runner specific
glue files when executing tests written in pytest.
2023-05-22 14:11:39 +02:00
..
ns1 Add islands of trust to mkeys test 2023-02-14 10:10:05 +11:00
ns2 Use DEFAULT_HMAC for rndc 2022-07-07 10:11:42 +10:00
ns3 Fix mkeys to work with DEFAULT_ALGORITHM properly 2022-08-10 12:46:06 +02:00
ns4 Add islands of trust to mkeys test 2023-02-14 10:10:05 +11:00
ns5 Add islands of trust to mkeys test 2023-02-14 10:10:05 +11:00
ns6 mkeys: use $() instead of back quotes 2022-08-09 15:45:11 +02:00
ns7 Use DEFAULT_HMAC for rndc 2022-07-07 10:11:42 +10:00
clean.sh Add islands of trust to mkeys test 2023-02-14 10:10:05 +11:00
README Update the copyright information in all files in the repository 2022-01-11 09:05:02 +01:00
setup.sh Add islands of trust to mkeys test 2023-02-14 10:10:05 +11:00
tests.sh Add islands of trust to mkeys test 2023-02-14 10:10:05 +11:00
tests_sh_mkeys.py Add pytest functions for shell system tests 2023-05-22 14:11:39 +02:00

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

SPDX-License-Identifier: MPL-2.0

This Source Code Form is subject to the terms of the Mozilla Public
License, v. 2.0.  If a copy of the MPL was not distributed with this
file, you can obtain one at https://mozilla.org/MPL/2.0/.

See the COPYRIGHT file distributed with this work for additional
information regarding copyright ownership.

This is for testing 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 initializing key in trust-anchors.

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.

ns7 is a validator with multiple views configured.  It is used for
testing per-view rndc commands and checking interactions between options
related to and potentially affecting RFC 5011 processing.