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 1952937 - freerdp: Port to OpenSSL 3.0
Summary: freerdp: Port to OpenSSL 3.0
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: freerdp
Version: CentOS Stream
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: beta
: ---
Assignee: Ondrej Holy
QA Contact: Martin Krajnak
URL:
Whiteboard:
Depends On:
Blocks: 1958021
TreeView+ depends on / blocked
 
Reported: 2021-04-23 15:36 UTC by Sahana Prasad
Modified: 2021-12-07 21:47 UTC (History)
5 users (show)

Fixed In Version: freerdp-2.2.0-8.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-12-07 21:44:43 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github FreeRDP FreeRDP pull 7008 0 None open Fix FIPS mode support and build with OpenSSL 3.0 2021-05-12 11:30:48 UTC

Description Sahana Prasad 2021-04-23 15:36:47 UTC
This bug is used to track the readiness of freerdp with OpenSSL 3.0

currently the build fails with some porting issues:

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

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

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 Ondrej Holy 2021-04-26 15:39:42 UTC
Just note that the only problem seems to be the "FIPS_mode_set" and "FIPS_mode" functions, which have been removed from OpenSSL 3.0 and the https://wiki.openssl.org/index.php/OpenSSL_3.0 document describes some ways how to fix that.

Comment 2 Sahana Prasad 2021-04-29 09:36:43 UTC
we have a FIPS compatibility downstream patch that supports
# define FIPS_mode() EVP_default_properties_is_fips_enabled(NULL)

There is no sidetag yet,
kindly use this build
https://brewweb.engineering.redhat.com/brew/buildinfo?buildID=1571383
I will notify you where there is a sidetag.

Comment 3 Ondrej Holy 2021-04-29 13:03:32 UTC
Ah, that explains why the RHEL build log contains only FIPS_mode_set failure, whereas the Fedora one contains also FIPS_mode failure. However, this downstream patch doesn't help here, since FIPS_mode_set needs to be replaced anyway. Just I am not super sure what is the right way, can the plain EVP_set_default_properties(NULL, "fips=yes") call be used as a replacement for FIPS_mode_set?

Comment 5 Ondrej Holy 2021-05-17 07:28:06 UTC
The proposed upstream fix has been merged so I think that we can backport it now.


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