b14c0546c1
In the second test we are looking for key files and extract the key id numbers. Because keys can be in different directories, we needed to change the maxdepth when searching for keys. For the second kasp system test, check that 'dnssec-keygen -k' (default policy) creates valid files, the 'get_keyids' returned more than one keytag, namely the ones that are inside the keys/ directory, that were created for the predecessor test, check that 'dnssec-keygen -k' (configuredd policy) creates valid files. This caused the system test to spew out errors that key files were missing (we were looking for key files in the current directory, but when looking for key id numbers we included the keys/ directory). It could also cause the next test to fail, check that 'dnssec-settime' by default does not edit key state file, because the STATE_FILE environment variable was overwritten with the key file path of one of the keys that were created with the configured policy. We fix this by adjusting the maxdepth for the test in question. Other tests don't need adjusting because they use unique zone names.
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.
The test setup for the KASP tests.
ns1 is reserved for the root server.
ns2 is running primary service for ns3.
ns3 is an authoritative server for the various test domains.
ns4 and ns5 are authoritative servers for various test domains related to views.
ns6 is an authoritative server that tests changes in dnssec-policy (algorithm
rollover).