openssh tests use "not valid yet" certificate from 2020, which is now valid
Bug #1859013 reported by
Dimitri John Ledkov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openssh (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Won't Fix
|
Undecided
|
Unassigned | ||
Trusty |
Won't Fix
|
Undecided
|
Unassigned | ||
Xenial |
Fix Released
|
Undecided
|
Unassigned | ||
Bionic |
Fix Released
|
Undecided
|
Unassigned | ||
Disco |
Won't Fix
|
Undecided
|
Unassigned | ||
Eoan |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
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:/
CVE References
tags: | added: update-excuse |
description: | updated |
description: | updated |
tags: | added: block-proposed-bionic block-proposed-disco block-proposed-eoan block-proposed-xenial |
description: | updated |
To post a comment you must log in.
disco is EOL