[Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
Dimitri John Ledkov
launchpad at surgut.co.uk
Thu Jan 9 23:56:15 UTC 2020
** Tags added: block-proposed-bionic block-proposed-disco block-
proposed-eoan block-proposed-xenial
** Description changed:
- openssh tests use "not valid yet" certificate from 2020, which is now
- valid
+ [Impact]
- https://anongit.mindrot.org/openssh.git/commit/?id=ff31f15773ee173502eec4d7861ec56f26bba381
+ * regression testsuite uses 1st of January 2020 as the date in the
+ future, however that is now in the past making autpkgtests fail.
- this causes autopkgtest regression suite fail in 2020
+ [Test Case]
- grep 20200101 -r .
- ./openssh-7.6p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure "-h -V20200101:20300101"
- ./openssh-7.6p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure "-n ${USER} -V20200101:20300101"
- ./openssh-7.2p2/regress/cert-hostkey.sh:test_one "cert not yet valid" failure "-h -V20200101:20300101"
- ./openssh-7.2p2/regress/cert-userkey.sh:test_one "cert not yet valid" failure "-n ${USER} -V20200101:20300101"
- ./openssh-6.6p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure "-h -V20200101:20300101"
- ./openssh-6.6p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure "-n ${USER} -V20200101:20300101"
- ./openssh-5.9p1/regress/cert-hostkey.sh:test_one "cert not yet valid" failure "-h -V20200101:20300101"
- ./openssh-5.9p1/regress/cert-userkey.sh:test_one "cert not yet valid" failure "-n ${USER} -V20200101:20300101"
+ * Autopkgtest must pass
+
+ [Regression Potential]
+
+ * Testsuite assertion update only
+
+ [Other Info]
+
+ This is a staged update to be rolled up with any other openssh update in
+ the future.
fixed in debian https://tracker.debian.org/news/1092767/accepted-
openssh-181p1-4-source-into-unstable/
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to openssh in Ubuntu.
https://bugs.launchpad.net/bugs/1859013
Title:
openssh tests use "not valid yet" certificate from 2020, which is now
valid
Status in openssh package in Ubuntu:
New
Status in openssh source package in Precise:
New
Status in openssh source package in Trusty:
New
Status in openssh source package in Xenial:
New
Status in openssh source package in Bionic:
New
Status in openssh source package in Disco:
New
Status in openssh source package in Eoan:
New
Status in openssh source package in Focal:
New
Bug description:
[Impact]
* regression testsuite uses 1st of January 2020 as the date in the
future, however that is now in the past making autpkgtests fail.
[Test Case]
* Autopkgtest must pass
[Regression Potential]
* Testsuite assertion update only
[Other Info]
This is a staged update to be rolled up with any other openssh update
in the future.
fixed in debian https://tracker.debian.org/news/1092767/accepted-
openssh-181p1-4-source-into-unstable/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1859013/+subscriptions
More information about the foundations-bugs
mailing list