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.

(cherry picked from commit 24e07ae98e02858bf677fdbe3c4fd5112b502cae)

diff --git a/bin/tests/system/kasp/tests.sh b/bin/tests/system/kasp/tests.sh
index ce168511397a2fb8d0348e810b2149674bb957fa..ba8e031c96685aa2a8edf3a107156b2c719866e1 100644 (file)
--- a/bin/tests/system/kasp/tests.sh
+++ b/bin/tests/system/kasp/tests.sh
@@ -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)