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 1637182 - SHA256 fingerprint support
Summary: SHA256 fingerprint support
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libssh
Version: 7.6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Martin Pitt
QA Contact: Nobody
URL:
Whiteboard:
Depends On:
Blocks: 1585191
TreeView+ depends on / blocked
 
Reported: 2018-10-08 20:49 UTC by Martin Pitt
Modified: 2018-11-28 08:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-28 08:01:31 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:3712 0 None None None 2018-11-28 08:01:37 UTC

Description Martin Pitt 2018-10-08 20:49:34 UTC
Description of problem: libssh 0.8 introduces some API to generate and show SHA256 fingerprints of host keys. The current 0.7 version only offers MD5 and SHA1, both of which are cryptographically broken now. Trying to use them causes assertion errors in OpenSSL when enabling FIPS mode (see bug 1585191).

To solve that in Cockpit, I just sent https://github.com/cockpit-project/cockpit/pull/10241 to use SSH_PUBLICKEY_HASH_SHA256 and 
ssh_get_fingerprint_hash() instead of ssh_get_hexa() (as SHA256 FPs are shown as base64 instead of hex by ssh, and hex keys are rather unwieldy at that length).

But to fix this cockpit-ssh bug in RHEL 7, I'd need these new APIs backported.

In https://bugzilla.redhat.com/show_bug.cgi?id=1585191#c13, Andreas already put a backport patch for SSH_PUBLICKEY_HASH_SHA256. Hopefully ssh_get_fingerprint_hash() is also not too intrusive to backport?

Comment 2 Andreas Schneider 2018-10-09 08:18:47 UTC
Anderson, could you please take care of this? The patches have all been backported to the v0-7 branch of libssh upstream.

Comment 5 Martin Pitt 2018-10-28 13:39:17 UTC
I pushed SHA256 support patches to dist-git, plus the fix for the "interactive keyboard" authentication (bug 1640812). I locally mockbuilt libssh and cockpit with the corresponding fix, and everything works -- I get SHA256 fingerprints, and it does not crash in FIPS mode.

Comment 13 errata-xmlrpc 2018-11-28 08:01:31 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, 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-2018:3712


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