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.
The requested changes are not accepted upstream, but the requested functionality
is important for enterprise-class deployments. This request therefore aims at
working with upstream on enabling GSSAPI support in OpenSSH or to find an
alternative solution.
+++ This bug was initially created as a clone of Bug #443472 +++
> What is the exact nature of the problem trying to be solved with this
> request?
Please consider including the GSSAPI Key Exchange features in our
OpenSSH packages.
> What, if any, business requirements are satisfied by this request? (What
> is the use case context?)
OpenSSH contains support out of the box for GSSAPI user authentication
using the 'gssapi-with-mic' mechanism, which is fine for small sites
with small kerberos deployments.
Larger sites, have requested that the key exchange patches be
included with Red Hat's OpenSSH rpm. Currently, many are rolling their
own version of OpenSSH with these patches:
http://www.sxw.org.uk/computing/patches/openssh.html> List the functional requirement(s) for performing the action(s) that are
> not presently possible. Please focus on describing the problem related
> requirements without projecting any specific solution.
GSSAPI key exchange will let customers use their existing key management
infrastructure (e.g. Kerberos), without having to distribute ssh host keys
everywhere. Sites with larger Kerberos deployments will benefit from this
the mos because ssh host key maintenance quickly becomes a nightmare.
With GSSAPI key exchange, servers do not need ssh host keys when being
accessed by clients with valid credentials.
> Each functional requirement must have clear acceptance criteria so Red Hat
> understands what success looks like.
Be able to successfully perform, in SSH, server and user authentication
via GSSAPI without having to use gobs of maps of ssh host keys.
There is an actual RFC published on OpenSSH Key exchange:
http://www.digipedia.pl/rfc/rfc4462.html
Event posted on 04-15-2010 11:05am EDT by kbaxley
I can most likely get my customer to help with testing once the Beta rolls
out.
This event sent from IssueTracker by kbaxley
issue 96013
Comment 16releng-rhel@redhat.com
2010-11-15 14:33:40 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.