It seems since the openssl 3 GA release back in September there's not been a single successful openssl build[1], and a number of bugs [2], and even more CVEs [3][4]. Why aren't these being dealt with in a semi reasonable fashion? The last actual successful build is now over 6 months ago. The latest on is remotely exploitable [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=109 [2] https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&classification=Fedora&component=openssl&list_id=12493381&product=Fedora&product=Fedora%20EPEL [3] https://www.openssl.org/news/vulnerabilities-3.0.html [4] https://lwn.net/Articles/887970/
Proposed as a Blocker for 36-beta by Fedora user pbrobinson using the blocker tracking app because: Remotely exploitable CVE that affects all variants of Fedora due to openssl
I confirm that it should be considered as a blocker.
Dmitry: will you be able to get an F36 build done today? I'm trying to pull together a Beta compose and it'd be nice to have that in it.
Dear Adam, Unfortunately, no. will do my best to finalize it till Friday, though not sure yet.
+4 for Beta FE and Final blocker in https://pagure.io/fedora-qa/blocker-review/issue/674 , waiting for Beta blocker votes to clean up to finalize that metadata.
BetaBlocker vote is now at -3 (+3 / -6) so rejecting it; marking as accepted Beta FE, accepted Final blocker.
FEDORA-2022-30744868ee has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-30744868ee
FEDORA-2022-30744868ee has been pushed to the Fedora 36 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-30744868ee` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-30744868ee See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2022-30744868ee has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report.