From 24e07ae98e02858bf677fdbe3c4fd5112b502cae Mon Sep 17 00:00:00 2001 From: Matthijs Mekking Date: Wed, 1 Jul 2020 13:19:24 +0200 Subject: [PATCH] Fix kasp test set_keytime 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. --- bin/tests/system/kasp/tests.sh | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/bin/tests/system/kasp/tests.sh b/bin/tests/system/kasp/tests.sh index 5528d5b8e6..5f92cf7f5e 100644 --- a/bin/tests/system/kasp/tests.sh +++ b/bin/tests/system/kasp/tests.sh @@ -1370,8 +1370,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)