]> git.ipfire.org Git - thirdparty/bind9.git/commit
rollover-going-insecure: From setup.sh to pytest bootstrap
authorMatthijs Mekking <matthijs@isc.org>
Fri, 28 Nov 2025 09:43:42 +0000 (10:43 +0100)
committerMatthijs Mekking <matthijs@isc.org>
Mon, 22 Dec 2025 15:25:12 +0000 (15:25 +0000)
commit40330867b156e9d6d4c639340f8daa2b76995fee
tree93883cf62ffbce6b3703c524d68593e236bbc131
parent5c499eb2c510c13be45c18239cea3f6be53f21e4
rollover-going-insecure: From setup.sh to pytest bootstrap

Symlink ns1 and ns2 to rollover/ns1 and rollover/ns2.
Symlink ns3/template.db.j2.manual to rollover/ns3/template.db.j2.manual.

Since the bootstrapping is done before the templates are rendered
automatically, replace @DEFAULT_ALGORITHM@ in ns3/kasp.conf.j2 to
ecdsa256 and rename to ns3/kasp.conf.

Now we have to fake different lifetimes, so adjust fake_lifetime
to update a single key.

Note that we have changed the setup slightly: We also sign the
step2 zones, but with post validation disabled. This is more
accurate because we need to test that the public keys and signatures
are being removed from the zone.

(cherry picked from commit cc4244f38411cfb67aed6467994ac85002ac8756)
bin/tests/system/rollover-going-insecure/ns1 [new symlink]
bin/tests/system/rollover-going-insecure/ns2 [new symlink]
bin/tests/system/rollover-going-insecure/ns3/kasp.conf [moved from bin/tests/system/rollover-going-insecure/ns3/kasp.conf.j2 with 78% similarity]
bin/tests/system/rollover-going-insecure/ns3/template.db.in [deleted symlink]
bin/tests/system/rollover-going-insecure/ns3/template.db.j2.manual [new symlink]
bin/tests/system/rollover-going-insecure/ns3/trusted.conf.j2 [new symlink]
bin/tests/system/rollover-going-insecure/setup.sh [deleted file]
bin/tests/system/rollover-going-insecure/tests_rollover_going_insecure_initial.py
bin/tests/system/rollover-going-insecure/tests_rollover_going_insecure_reconfig.py
bin/tests/system/rollover/setup.py