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