Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2091694

Summary: FIPS compliance of signature APIs used by OpenSSH
Product: Red Hat Enterprise Linux 9 Reporter: Alicja Kario <hkario>
Component: opensshAssignee: Dmitry Belyavskiy <dbelyavs>
Status: CLOSED ERRATA QA Contact: Marek Havrila <mhavrila>
Severity: medium Docs Contact:
Priority: medium    
Version: 9.0CC: cllang, dbelyavs, jjelen, mhavrila
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: openssh-8.7p1-30.el9 Doc Type: No Doc Update
Doc Text:
If this bug requires documentation, please select an appropriate Doc Type value.
Story Points: ---
Clone Of:
: 2092503 (view as bug list) Environment:
Last Closed: 2023-11-07 08:52:54 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 2092503    

Description Alicja Kario 2022-05-30 18:06:35 UTC
Description of problem:
OpenSSH uses the EVP_Sign* and EVP_Verify* APIs for signature generation and verification. Unfortunately the only FIPS compliant APIs for signature generation and verification are the EVP_DigestSign* and EVP_DigestVerify* APIs.

Version-Release number of selected component (if applicable):
openssh-8.7p1-8.el9

How reproducible:
always

Steps to Reproduce:
1. inspect sources or run with openssl version that disables the non-FIPS compliant APIs

Actual results:
non compliant APIs used

Expected results:
only compliant APIs used

Additional info:

Comment 7 Dmitry Belyavskiy 2022-12-08 15:01:03 UTC
What should be done:
In the function sshkey_calculate_signature/sshkey_verify_signature we should use the DigestSignInit/Update/Final API

ECDSA_do_sign/verify calls should be eliminated from both SSH and ssh_pam (leave just in sk-dummy.c)
It can be done via reconstructing EVP_PKEY object and dealing with it and new API

DH/ECDH key exchanges should be rewritten to use EVP_PKEY API

The keys created via EVP_PKEY_set1_* functions follow the legacy code path. It means we have to recreate non-legacy EVP_PKEY objects from components.

Comment 18 errata-xmlrpc 2023-11-07 08:52:54 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (openssh bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2023:6622