[2304] in Kerberos_V5_Development

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

Re: Kerberos v5 and NT

daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Wed Mar 12 15:39:18 1997

Date: Wed, 12 Mar 1997 15:37:26 -0500
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: "Terry Malosh" <9531MALO@UCSBVM.ucsb.edu>
Cc: <krbdev@MIT.EDU>
In-Reply-To: Terry Malosh's message of Wed, 12 Mar 97 11:15:55 PST,
	<9703121917.AA00404@MIT.EDU>

   Date:     Wed, 12 Mar 97 11:15:55 PST
   From: "Terry Malosh (Profs = TAM, x3521)" <9531MALO@UCSBVM.ucsb.edu>

   I was wondering what version of NT you were having delays in integrating
   Kerberos with ... 3.51, 4.0, ... or are you just trying to integrate to
   4.0?

We're only integrating with 4.0, and the main reason for delay is that
we're making some fundamental changes in how functions are separated
into DLL's.  

In the ALPHA 1 snapshot, all of the functions were in the KRB5_32.DLL;
in our new snapshot, we've broken them out into a number of different
DLL's.  The reason for doing this is to make it possible for an
application (such as our MIT Leash program, which manages Kerberos
tickets) to simultaneously link against a Kerberos V4 and V5 library.
The delay is waiting for Paul Hill, who has coordinated all of the V4
Windows development, to agree that we've actually gotten the com_err
functions separated out correctly, since com_err is shared by both the
V4 and V5 libraries.

						- Ted

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