[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Pending OpenSSH release: contains Kerberos/GSSAPI changes

To: Jeffrey Hutzelman <jhutz@cmu.edu>
Subject: Re: Pending OpenSSH release: contains Kerberos/GSSAPI changes
From: Sam Hartman <hartmans@mit.edu>
Date: Sat, 31 Jan 2004 12:12:53 -0500
Cc: "Wachdorf, Daniel R" <drwachd@sandia.gov>, "'Darren Tucker'" <dtucker@zip.com.au>, kerberos@mit.edu, krbdev@mit.edu, heimdal-discuss@sics.se, ietf-ssh@NetBSD.org, OpenSSH Devel List <openssh-unix-dev@mindrot.org>
In-Reply-To: <20040130224824.GL18744@binky.central.sun.com> (NicolasWilliams's message of "Fri, 30 Jan 2004 16:48:25 -0600")
References: <AC89BDA1E3CCBC42B9CA5B50FE7934D3066F1122@es10snlnt.sandia.gov><1448470000.1075499031@minbar.fac.cs.cmu.edu><20040130224824.GL18744@binky.central.sun.com>
Sender: owner-heimdal-discuss@sics.se
User-Agent: Gnus/5.1002 (Gnus v5.10.2) Emacs/21.1 (gnu/linux)

I'd prefer client MAY mutual auth rather than client SHOULD NOT mutual
auth.

If the server does not implement gss-keyex then a sufficiently clever
client can get some of the benefits of gss-keyex in some situations by
requesting mutual.

Prev by Date: Re: Pending OpenSSH release: contains Kerberos/GSSAPI changes
Prev by thread: Re: Pending OpenSSH release: contains Kerberos/GSSAPI changes
Next by thread: gss_krb5_ccache_name
Index(es):
- Date
- Thread