[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
Setting series as wontfix due to end of standard support. This should be fixed from bionic and on. ** Changed in: openssh (Ubuntu Precise) Status: New => Won't Fix ** Changed in: openssh (Ubuntu Trusty) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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: Won't Fix Status in openssh source package in Trusty: Won't Fix Status in openssh source package in Xenial: Fix Released Status in openssh source package in Bionic: Fix Released Status in openssh source package in Disco: Won't Fix Status in openssh source package in Eoan: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
This bug was fixed in the package openssh - 1:7.6p1-4ubuntu0.5 --- openssh (1:7.6p1-4ubuntu0.5) bionic-security; urgency=medium * SECURITY REGRESSION: User enumeration issue (LP: #1934501) - debian/patches/CVE-2018-15473.patch: updated to fix bad patch backport. -- Marc Deslauriers Wed, 11 Aug 2021 14:02:09 -0400 ** Changed in: openssh (Ubuntu Bionic) Status: Fix Committed => Fix Released ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-15473 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 Released Status in openssh source package in Bionic: Fix Released Status in openssh source package in Disco: Won't Fix Status in openssh source package in Eoan: Fix Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
This bug was fixed in the package openssh - 1:8.0p1-6ubuntu0.1 --- openssh (1:8.0p1-6ubuntu0.1) eoan; urgency=medium * Apply upstream patch to stop using 2020 as a future date in regress tests. LP: #1859013 -- Dimitri John Ledkov Thu, 09 Jan 2020 23:53:27 + ** Changed in: openssh (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 Released 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 Released 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
This bug was fixed in the package openssh - 1:7.2p2-4ubuntu2.10
---
openssh (1:7.2p2-4ubuntu2.10) xenial; urgency=medium
* Fix deadlock when AuthorizedKeysCommand produces a large output.
(LP: #1877454)
- d/p/authkeyscommand-deadlock-01.patch: Make sure to call fclose(2)
and assign NULL to the file handler used to read
"Authorized{Keys,Principal}Command" directives.
- d/p/authkeyscommand-deadlock-02.patch: Consume entire output
generated by the command pointed by
"Authorized{Keys,Principal}Command" in order to avoid sending a
SIGPIPE to the process.
openssh (1:7.2p2-4ubuntu2.9) xenial; urgency=medium
* Apply upstream patch to stop using 2020 as a future date in regress
tests. LP: #1859013
-- Sergio Durigan Junior Wed, 13 May
2020 10:12:28 -0400
** Changed in: openssh (Ubuntu Xenial)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, 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 Released
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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
Hello Dimitri, or anyone else affected, Accepted openssh into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/openssh/1:7.2p2-4ubuntu2.10 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-xenial. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-xenial ** Tags added: verification-needed verification-needed-xenial ** Tags removed: block-proposed-xenial verification-needed verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
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 Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
focal has -5 now ** Changed in: openssh (Ubuntu Focal) Status: New => Fix Released ** Changed in: openssh (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
disco is EOL ** Changed in: openssh (Ubuntu Disco) Status: New => Won't Fix ** Changed in: openssh (Ubuntu Eoan) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, 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 -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1859013] Re: openssh tests use "not valid yet" certificate from 2020, which is now valid
** 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
Touch seeded packages, 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
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
