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 1816226 - Weak GSSAPI key exchange methods enabled by default [openssh]
Summary: Weak GSSAPI key exchange methods enabled by default [openssh]
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: openssh
Version: 8.4
Hardware: Unspecified
OS: Unspecified
medium
unspecified
Target Milestone: rc
: 8.0
Assignee: Jakub Jelen
QA Contact: Ondrej Moriš
URL:
Whiteboard:
Depends On: 1666781
Blocks: 1816253
TreeView+ depends on / blocked
 
Reported: 2020-03-23 15:29 UTC by Jakub Jelen
Modified: 2024-03-25 15:46 UTC (History)
6 users (show)

Fixed In Version: openssh-8.0p1-5.el8
Doc Type: Enhancement
Doc Text:
Feature: New GSSAPI key exchange methods using SHA2 from RFC 8732 are enabled by default. Reason: RHEL 8 contains implementation of the new GSSAPI key exchange methods since 8.0, but only the SHA1 were enabled by default because the specification was not finalized. Now, the specification is published so the new methods are enabled by default (which also depends on a change in crypto policies). Result: The new SHA2-based GSSAPI key exchange methods are available and usable by default.
Clone Of: 1666781
: 1816253 (view as bug list)
Environment:
Last Closed: 2020-11-04 01:32:00 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4439 0 None None None 2020-11-04 01:32:10 UTC

Description Jakub Jelen 2020-03-23 15:29:52 UTC 
+++ This bug was initially created as a clone of Bug #1666781 +++

The build of OpenSSH in Fedora carries patches to enable GSSAPI key exchange.  Hurrah, when this is used, the need to manually verify host keys is removed.

The manual says that the default value for setting GSSAPIKexAlgorithms is “gss-gex-sha1-,gss-group14-sha1-”.  However, https://datatracker.ietf.org/doc/draft-ietf-curdle-ssh-kex-sha2/ says that gss-gex-sha1- is weak and "SHOULD NOT be used".  I suggest that it be disabled by default, and that some of the newer methods such as gss-curve25519-sha256-, gss-nistp256-sha256-, gss-group14-sha256-
be enabled by default instead.

--- Additional comment from Jakub Jelen on 2019-01-16 16:28:20 CET ---

Hello and thank you for your interest. This is indeed planned, but we are waiting for finalizing and approving the draft defining the new gssapi key exchange methods before enabling them to the world:

https://tools.ietf.org/html/draft-ietf-curdle-gss-keyex-sha2-08

Generally, the GEX methods are not advised these days and once we will have something better, we will certainly try to disable them.

Actually I am not quite sure if I saw your referenced draft before, but it looks like it is stalled, the current version expired and it does not look like moving forward to be accepted as a RDC any time soon. Actually it does not say anything new to me.

I will leave this bug open to keep track of things and make sure I will update the list when the drafts will get approved.

--- Additional comment from Jakub Jelen on 2020-03-23 15:27:14 CET ---

FYI, the RFC 8732 was published so I would like to enable these soon in Fedora.

[1] https://tools.ietf.org/html/rfc8732

--- Additional comment from Jakub Jelen on 2020-03-23 16:24:34 CET ---

First step is enabling them in Crypto policy. The issue was filled here as it does not look like completely straight-forward:

https://gitlab.com/redhat-crypto/fedora-crypto-policies/-/issues/19
Comment 8 errata-xmlrpc 2020-11-04 01:32:00 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-2020:4439
Note You need to log in before you can comment on or make changes to this bug.