RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1952941 - Kronosnet: Port to OpenSSL 3.0
Summary: Kronosnet: Port to OpenSSL 3.0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: kronosnet
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: beta
: ---
Assignee: Christine Caulfield
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1958021
TreeView+ depends on / blocked
 
Reported: 2021-04-23 15:41 UTC by Sahana Prasad
Modified: 2022-02-08 03:29 UTC (History)
8 users (show)

Fixed In Version: kronosnet-1.21-2.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-08 03:29:05 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Sahana Prasad 2021-04-23 15:41:44 UTC
This bug is used to track the readiness of Kronosnet with OpenSSL 3.0

currently the build fails with some porting issues:

https://kojihub.stream.rdu2.redhat.com/koji/taskinfo?taskID=218620

Kindly fix them to ensure this package builds with OpenSSL 3.0, as we will introduce OpenSSL 3.0 in RHEL-9 very soon.

OpenSSL 3.0 package to test with:
http://download.eng.bos.redhat.com/rhel-9/nightly/RHEL-9-Beta/RHEL-9.0.0-20210414.0/compose/BaseOS/x86_64/os/Packages/openssl-3.0.0-0.alpha13.1.el9.x86_64.rpm

If you ave any further queries, kindly mail

rhel-crypto 

Thank you

Comment 1 Fabio Massimo Di Nitto 2021-04-23 17:49:16 UTC
Upstream fix already exist and will be part of the next stable release that will be done in 2/3 days.

https://github.com/kronosnet/kronosnet/commit/0453dfe46b4b256183a09e55d19cf18fb66f4e61

Cheers
Fabio

Comment 2 Sahana Prasad 2021-04-29 09:38:44 UTC
Fabio, great. Thanks for the information.

You can try to downstream those patches and test with :

(There is no sidetag yet)

https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1571383

I will notify you where there is a sidetag.

Comment 3 Fabio Massimo Di Nitto 2021-05-03 04:51:29 UTC
(In reply to Sahana Prasad from comment #2)
> Fabio, great. Thanks for the information.

https://bugzilla.redhat.com/show_bug.cgi?id=1954551 is already built.

> 
> You can try to downstream those patches and test with :
> 
> (There is no sidetag yet)
> 
> https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1571383
> 
> I will notify you where there is a sidetag.

Chrissie maintains kronosnet downstream, I am upstream. We have been testing with openssl 3.0-alpha13 for a while using Debian Experimental, tho of course we will double check with our builds.


Note You need to log in before you can comment on or make changes to this bug.