upstream: what bozo decided to use 2020 as a future date in a regress

test?

OpenBSD-Regress-ID: 3b953df5a7e14081ff6cf495d4e8d40e153cbc3a

Origin: upstream, https://anongit.mindrot.org/openssh.git/commit/?id=ff31f15773ee173502eec4d7861ec56f26bba381
Last-Update: 2020-01-09

Patch-Name: regress-2020.patch

2 files changed, 2 insertions, 2 deletions

diff --git a/regress/cert-hostkey.sh b/regress/cert-hostkey.sh
index 86ea62504..844adabcc 100644
--- a/regress/cert-hostkey.sh
+++ b/regress/cert-hostkey.sh
@@ -252,7 +252,7 @@ test_one() {
 test_one "user-certificate"     failure "-n $HOSTS"
 test_one "empty principals"     success "-h"
 test_one "wrong principals"     failure "-h -n foo"
-test_one "cert not yet valid"   failure "-h -V20200101:20300101"
+test_one "cert not yet valid"   failure "-h -V20300101:20320101"
 test_one "cert expired"         failure "-h -V19800101:19900101"
 test_one "cert valid interval"  success "-h -V-1w:+2w"
 test_one "cert has constraints" failure "-h -Oforce-command=false"
diff --git a/regress/cert-userkey.sh b/regress/cert-userkey.sh
index 38c14a698..5cd02fc3f 100644
--- a/regress/cert-userkey.sh
+++ b/regress/cert-userkey.sh
@@ -338,7 +338,7 @@ test_one() {
 test_one "correct principal"    success "-n ${USER}"
 test_one "host-certificate"     failure "-n ${USER} -h"
 test_one "wrong principals"     failure "-n foo"
-test_one "cert not yet valid"   failure "-n ${USER} -V20200101:20300101"
+test_one "cert not yet valid"   failure "-n ${USER} -V20300101:20320101"
 test_one "cert expired"         failure "-n ${USER} -V19800101:19900101"
 test_one "cert valid interval"  success "-n ${USER} -V-1w:+2w"
 test_one "wrong source-address" failure "-n ${USER} -Osource-address=10.0.0.0/8"