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 2023744 - enable diffie-hellman-group14-sha256 in libssh
Summary: enable diffie-hellman-group14-sha256 in libssh
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: crypto-policies
Version: 8.6
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Alexander Sosedkin
QA Contact: Ondrej Moriš
Jan Fiala
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-11-16 12:27 UTC by Alexander Sosedkin
Modified: 2022-05-10 16:38 UTC (History)
2 users (show)

Fixed In Version: crypto-policies-20211116-1.gitae470d6.el8
Doc Type: Enhancement
Doc Text:
.Crypto policies support `diffie-hellman-group14-sha256` You can now use the `diffie-hellman-group14-sha256` key exchange (KEX) algorithm for the `libssh` library in RHEL system-wide cryptographic policies. This update also provides parity with OpenSSH, which also supports this KEX algorithm. With this update, `libssh` has `diffie-hellman-group14-sha256` enabled by default, but you can disable it by using a custom crypto policy.
Clone Of:
Environment:
Last Closed: 2022-05-10 15:22:45 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CRYPTO-5325 0 None None None 2021-11-16 17:15:38 UTC
Red Hat Issue Tracker RHELPLAN-102925 0 None None None 2021-11-16 12:28:32 UTC
Red Hat Product Errata RHBA-2022:2044 0 None None None 2022-05-10 15:22:50 UTC

Description Alexander Sosedkin 2021-11-16 12:27:58 UTC 
Description of problem: libssh gained support for diffie-hellman-group14-sha256 in 0.9.4. We have 0.9.4 since 8.3, yet haven't enabled the algorithm in crypto-policies.

Version-Release number of selected component (if applicable): crypto-policies-20210617-1.gitc776d3e.el8
How reproducible: always
Steps to Reproduce: look at the policies
Actual results: no diffie-hellman-group14-sha256 in libssh configs
Expected results: diffie-hellman-group14-sha256 in libssh configs where openssh has it

Additional info:
* https://www.libssh.org/2020/04/09/libssh-0-9-4-and-libssh-0-8-9-security-release
* https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/commit/03870400c7f837e2af9cc637a3bdbb5991d95873
Comment 10 errata-xmlrpc 2022-05-10 15:22:45 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 (crypto-policies 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-2022:2044
Note You need to log in before you can comment on or make changes to this bug.