ComputerSurge/bind9
3
0
Fork 0
Code Pull Requests 1 Activity

Fix kasp test set_keytime

Browse Source 
While the creation and publication times of the various keys
in this policy are nearly at the same time there is a chance that
one key is created a second later than the other.

The `set_keytimes_algorithm_policy` mistakenly set the keytimes
for KEY3 based of the "published" time from KEY2.

(cherry picked from commit 24e07ae98e)
This commit is contained in:
Matthijs Mekking
2020-07-01 13:19:24 +02:00
committed by Mark Andrews
parent a10f754c60
commit de02eb55b5
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
bin/tests/system/kasp/tests.sh
View File

@@ -1371,8 +1371,8 @@ set_keytimes_algorithm_policy() {
# Second ZSK (KEY3).
created=$(key_get KEY3 CREATED)
set_keytime "KEY3" "PUBLISHED" "${published}"
set_keytime "KEY3" "ACTIVE" "${published}"
set_keytime "KEY3" "PUBLISHED" "${created}"
set_keytime "KEY3" "ACTIVE" "${created}"
# Key was pregenerated.
if [ "$1" == "pregenerated" ]; then
keyfile=$(key_get KEY3 BASEFILE)