[233] in installers
Re: kclnt32.dll
daemon@ATHENA.MIT.EDU (Dave Hardy)
Fri Feb 19 12:31:31 1999
Date: Fri, 19 Feb 1999 12:30:33 -0500
To: installers@mit.edu
From: Dave Hardy <TOONCES@MITVMC.MIT.EDU> (by way of Regina Gogol <rlgogol@mit.edu>)
Cc: TOONCES@MITVMC.MIT.EDU, DB2DBA-L@mitvma.mit.edu
On Thu, 18 Feb 1999 07:42:04 EST you said:
>As some of you will recall we've had, essentially, this same issue
>in the past. In October of '96 we debugged ESClient problems that
>were being experienced on some installations and determined that
>the kclient.dll was being installed in the \eudora directory where
>ESClient could not find it. After discussions with various folks
>it was agreed that kclient.dll should be located in the \net\mit
>directory and that the Eudora installer should be modified to put
>it there rather than in the \eudora directory. There was concern
>that having multiple copies of this .dll would lead to problems
>'down the road' when an update to kerberos was necessary - hence
>it was prefered that all applications utilize one copy of the file
>which would be stored in a standard location.
Does anyone know if any current I/S installers install kclnt32.dll at
all? I dug it up from the latest (1997, I think) Kerberos 4 main
distribution where it was buried about 4 levels deep in directories with
the other KRB4 binaries.
Does the latest MINK or EUDORA install it in \net\mit? I agree that's
probably the best place for it, if ESClient will find it.
There might be some options here, like having our own copy of kclnt32,
fixing the problem, and calling it something else, if whatever's keeping
it from being found can be resolved. Alternatively, maybe the kclnt32
routines could be bundled into the ESClient.DLL. I'd need to find out if
there are tools out there that can grab a routine from one DLL and put
them into another, or play with the source code (if present for KClnt32)
etc... and this could make us incompatible if the Kerberos 4 servers are
changed down the road, but that could happen anyway (like what happened
with the last Kerberos 4 release where a new field was added to the data
structure for the Kerberos ticket, which, of course, broke the routines
that use that structure directly).
Doing these things by next Wednesday though, may be another story. :)
Has anyone tried putting KClnt32.DLL into \net\mit, making sure it's the
only one on the system, and then adding \net\mit to the NT "path"
environment variable? That doesn't work here on Windows 98, but Windows
98 is still, at least somewhat, DOS-based (i.e. runs AUTOEXEC.BAT at
startup) where NT is not. I hope to be able to at least try this idea on
NT by then.
Dave Hardy | Owner: Discus-L(Discus fish), Stripes(Angelfish)
toonces@mitvmc.mit.edu | Co-Owner: CASTRECL (Musical Theatre recordings)
-----------------------|-------------------------------------------------
Cambridge, MA, USA | Host of WMBR's Second Stage and Cabaret Corner |
