[Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid

Steve Langasek steve.langasek at canonical.com
Sun May 17 04:26:33 UTC 2020


Confirmed that the autopkgtests have passed with the new version in
-proposed, for all series.  Marking v-done so that this isn't listed as
a candidate for removal from -proposed.

** Tags removed: verification-needed verification-needed-bionic verification-needed-eoan verification-needed-xenial
** Tags added: verification-done-bionic verification-done-eoan verification-done-xenial

-- 
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:
  Fix Released
Status in openssh source package in Precise:
  New
Status in openssh source package in Trusty:
  New
Status in openssh source package in Xenial:
  Fix Committed
Status in openssh source package in Bionic:
  Fix Committed
Status in openssh source package in Disco:
  Won't Fix
Status in openssh source package in Eoan:
  Fix Committed
Status in openssh source package in Focal:
  Fix Released

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