Pending OpenSSH release: contains Kerberos/GSSAPI changes
Wachdorf, Daniel R
drwachd at sandia.gov
Fri Jan 30 18:25:34 EST 2004
1 - RFC states GSS_C_MUTUAL_FLAG SHOULD not be used. The current open ssh
server requires that it be used.
2 - RFC also allow for gss mechanisms that don't have GSSAPI integrity.
Servers can then choose to disallow it. As far as I can tell from the code,
any client which doesn't (or cant) have the GSS_C_INTEG_FLAG set cannot
connect. I can't test this because Kerberos-gssapi uses integrity.
From: Ben Lindstrom [mailto:mouring at etoh.eviladmin.org]
Sent: Friday, January 30, 2004 4:11 PM
To: Wachdorf, Daniel R
Cc: 'Sam Hartman'; 'Jeffrey Hutzelman'; krbdev at mit.edu; ietf-ssh at NetBSD.org;
kerberos at mit.edu; heimdal-discuss at sics.se; OpenSSH Devel List
Subject: RE: Pending OpenSSH release: contains Kerberos/GSSAPI changes
On Fri, 30 Jan 2004, Wachdorf, Daniel R wrote:
> It could be a problem. If someone has implemented a client and doesn't do
> mutual auth (as the standard says they should), they could be broken.
This right here is the key to me. If someone is not following the RFC.
Then I say let them complaint to their vendor.
Again I ask.. As the code stands are *WE* in RFC compliance? If not we
need it fixed.
As for what to base it off of. Pick a recent snapshot. Not as if the
GSSAPI-WITH-MIC code has drasticly changed in the last few days.
More information about the krbdev