This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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 2190084 - RFE: enhance error message "error in libcrypto" when key is too small
Summary: RFE: enhance error message "error in libcrypto" when key is too small
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: openssh
Version: 9.1
Hardware: All
OS: Linux
medium
medium
Target Milestone: rc
: ---
Assignee: Dmitry Belyavskiy
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-04-27 05:43 UTC by Renaud Métrich
Modified: 2023-09-20 00:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-09-20 00:12:47 UTC
Type: Story
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-10528 0 None None None 2023-05-02 09:42:13 UTC
Red Hat Issue Tracker   RHEL-5289 0 None Migrated None 2023-09-20 00:09:41 UTC
Red Hat Issue Tracker RHELPLAN-155889 0 None None None 2023-04-27 05:47:01 UTC
Red Hat Knowledge Base (Solution) 7009799 0 None None None 2023-04-27 05:43:19 UTC

Description Renaud Métrich 2023-04-27 05:43:20 UTC 
Description of problem:

After enabling FIPS on a system, the minimal length for RSA keys is 2048 bits.
If the user's RSA key length is 1024 bits, the following non-explicit/non-helpful message gets printed:
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------
debug1: Server accepts key: /root/.ssh/id_rsa RSA SHA256:mZrafjEjVNCD8qhXqmUf+D6JRUtW1JnkBVcXnDAwr30
debug3: sign_and_send_pubkey: RSA SHA256:mZrafjEjVNCD8qhXqmUf+D6JRUtW1JnkBVcXnDAwr30
debug3: sign_and_send_pubkey: signing using rsa-sha2-256 SHA256:mZrafjEjVNCD8qhXqmUf+D6JRUtW1JnkBVcXnDAwr30
debug1: identity_sign: sshkey_sign: error in libcrypto
sign_and_send_pubkey: signing failed for RSA "/root/.ssh/id_rsa": error in libcrypto
-------- 8< ---------------- 8< ---------------- 8< ---------------- 8< --------

It would be great to print details on the error, instead of getting a generic error, which makes it hard to troubleshoot.

Version-Release number of selected component (if applicable):

openssh-clients

How reproducible:

Always

Steps to Reproduce:
1. Create a 1024 bits RSA key
2. Switch to FIPS
3. Try connecting

Actual results:

Generic error message

Expected results:

"Invalid key length" or similar message

Additional info:

To reproduce, make sure crypto-policies-20220223-1.git5203b41.el9_0.1.noarch is used, because this package doesn't enforce 2048 bits for RSA (newer packages do).
Comment 4 RHEL Program Management 2023-09-20 00:07:12 UTC 
Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.
Comment 5 RHEL Program Management 2023-09-20 00:12:47 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.