[1349] in Kerberos_V5_Development
SAP and Krb5 status
daemon@ATHENA.MIT.EDU (Theodore Y. Ts'o)
Sat Jun 22 17:55:59 1996
Date: Sat, 22 Jun 1996 17:55:52 -0400
From: "Theodore Y. Ts'o" <tytso@MIT.EDU>
To: pbh@MIT.EDU
Cc: krbdev@MIT.EDU, tregan@MIT.EDU
OK, here's the status of how far I've gotten with the SAP and Krb5
project.
(1) Arlington contains a snapshot of the latest kerbsrc.tar and
kerbsrc-nt.tar files. Whether you want to use kerbsrc.tar and
kerbsrc-nt.tar is soley on whether you are compiling on a FAT or VFAT
filesystem. In other words, if you want to compile the krb5 for win16
on an NT machine, just grab kerbsrc-nt.tar, unpack it, and compile it
using the 16-bit compiler.
(1a) As an aside, if you want to try compiling things for Win-32, just
unpack kerbsrc-nt.tar, unpack in on Win 95 or Win NT machine, and then
do a nmake/c using the 32-bit compiler. I've hacked wconfig.exe so it
can automatically sense that the 32-bit compiler is being used and set
up the Makefiles appropriately. Current status of the Win-NT port is
that we're building all of the .OBJ files without any major warnings,
but I haven't modified things to build the .DLL files, and the
windows-specific programs in \windows are a complete disaster. They're
going to require a lot of work before they will compile under both
win-16 and win-32....
(2) In order to build sapkrb5.dll, do the win-16 krb5 build normally.
Then put the version server stuff in \vers; if you want the version
server stuff elsewhere, edit lib\makefile and lib\makefile.in and change
VERS_DIR to point somewhere else (note that in makefile.in it's the line
that begins with ##DOSVERS_DIR). Finally, in the lib directory, type
"nmake sapkrb5.dll". The actual calls to the version server library are
in lib\win_glue.c, which is specially compiled with the appropriate
#ifdef for sapkrb5.dll.
(3) The SAPGUI 3.0d with the external security hooks has been installed
on lost-crusade. The install tree from which I did the install is in
\tytso\sap. It installed everything into \sapgui on the machine.
sapkrb5.dll should be installed in \sapgui --- this is controlled by the
environment variable SNC_LIB, which is set in autoconf.bat.
(4) The krb5 tree is also on lost-crusade, in \tytso\krb5. The built
clients and libraries can be found in \tytso\kbin, or for easy access in
the tytso program folder. (The SAP icons are also in the tytso program
folder.)
(5) The snapshot of the version server library and sources which you had
given me is in \vers on lost-crusade. I installed the vs.dll which you
had given me in \net\mit; the old vs.dll that was in \net\mit was
renamed to vsdll.old.
(6) I've verified sapkrb5.dll, and there are definitely ascii strings
corresponding to the calls to the version server. However, when I run
the sapgui client with security turned on, it isn't calling the version
server; I'm not sure why. Using the X-Ray debug tool, which monitors
winsock calls, I don't see any evidence that we're making any version
server network calls at all.
Well, I think that's it. If you have any questions, just send me
e-mail; I'll be reading e-mail at least 1-2 times a day.
- Ted
