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

Fix check next key event check in kasp test

Browse Source 
Prevent intermittent false positives on slow platforms by subtracting
the number of seconds which passed between key creation and invoking
'rndc dnssec -checkds'.

This particularly fails for the step3.csk-roll2.autosign zone because
the closest next key event is when the zone signatures become
omnipresent. Running 'rndc dnssec -checkds' some time later means
that the next key event is in fact closer than the calculated time
and thus we need to adjust the expected time by the time already
passed.

(cherry picked from commit 262b52a154)
This commit is contained in:
Matthijs Mekking
2020-08-10 17:09:44 +02:00
parent 571b73260c
commit 9b69ab4c38
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

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

@@ -3682,8 +3682,13 @@ dnssec_verify
# successor signatures. This is the retire interval: Dsgn plus the
# maximum zone TTL plus the zone propagation delay plus retire-safety. For the
# csk-roll2 policy that means: 12h (because 1d validity and refresh within
# 12 hours) + 1d + 1h + 1h = 38h = 136800 seconds.
check_next_key_event 136800
# 12 hours) + 1d + 1h + 1h = 38h = 136800 seconds. Prevent intermittent false
# positives on slow platforms by subtracting the number of seconds which
# passed between key creation and invoking 'rndc dnssec -checkds'.
now="$(TZ=UTC date +%s)"
time_passed=$((now-start_time))
next_time=$((136800-time_passed))
check_next_key_event $next_time
#
# Zone: step4.csk-roll2.autosign.