[2326] in Kerberos_V5_Development

home help back first fref pref prev next nref lref last post

Re: Further gss v2 support in K5 rel 1 updates

daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Thu Mar 27 17:47:10 1997

Date: Thu, 27 Mar 1997 17:45:56 -0500
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: "Theodore Y. Ts'o" <tytso@MIT.EDU>
Cc: Andrew Gray <agray@osf.org>, "'krbdev@mit.edu'" <krbdev@MIT.EDU>
In-Reply-To: Theodore Y. Ts'o's message of Thu, 27 Mar 1997 15:04:49 -0500,
	<9703272004.AA22440@dcl.MIT.EDU>

   Date: Thu, 27 Mar 1997 15:04:49 -0500
   From: "Theodore Y. Ts'o" <tytso@MIT.EDU>

   I hadn't originally planned to support prot_ready_state, but having
   looked into the code, it's actually pretty easy to support.  So yes, you
   can expect to see it in the foreseeable future.

While I was stuck in a boring meeting (tm), I implemented
prot_ready_flag, trans_flag, gss_export_name(), and
gss_duplicate_name().  I haven't tested it yet, but the functions are
pretty simple.

   The functions which we still need to implement for GSSAPI V2 complaince
   are:

   gss_cannonicalize_name()  ---- trivial, since we have a
				   single-mechanism implementation

   gss_export_name()	---- not much work, we just have to find
   gss_import_name()	---- time to do it

This last was a typo; gss_import_name() should be gss_duplicate_name().

							- Ted
home help back first fref pref prev next nref lref last post