[BACK]Return to README-WIN32 CVS log [TXT][DIR] Up to [local] / src / kerberosIV / src
File: [local] / src / kerberosIV / src / Attic / README-WIN32 (download)

Revision 1.1.1.1 (vendor branch), Fri Feb 25 15:31:57 2000 UTC (24 years, 3 months ago) by hin
Branch: KTH
CVS Tags: OPENBSD_3_3_BASE, OPENBSD_3_3, OPENBSD_3_2_BASE, OPENBSD_3_2, OPENBSD_3_1_BASE, OPENBSD_3_1, OPENBSD_3_0_BASE, OPENBSD_3_0, OPENBSD_2_9_BASE, OPENBSD_2_9, OPENBSD_2_8_BASE, OPENBSD_2_8, OPENBSD_2_7_BASE, OPENBSD_2_7, KRB4_1_1_1, KRB4_1_0_8, KRB4_1_0_4, KRB4_1_0_2, KRB4_1_0
Changes since 1.1: +0 -0 lines 

Importing KTH Kerberos4 version 1.0
(art@ ok)

It should be possible to build several of the libraries and the GUI
telnet ``voodoo'' on Win95/NT.  In case you don't want to try there
are binaries available at
ftp://ftp.pdc.kth.se/pub/krb/binaries/i386-unknown-winnt4.0.

In case you want to build from source and possibly hack some on them
yourself here's a short guide:

You need to build the libraries (DLLs) first and in this order:

lib/roken
lib/des
lib/krb
lib/kclient

And then the two applications:

appl/krbmanager
appl/voodoo

In each case there is a Visual-C++ generated makefile with the name
*.mak in the corresponding directory.  You might be able to load that
into Microsoft whatever Studio and you might be able to just run nmake
on them.

Once you have ended up with 4 DLLs and 2 EXEs you only have to place
them in a directory in your PATH and start voodoo.

In case it doesn't work, you have discovered bugs or added some more
features the mail address to use is <kth-krb-bugs@nada.kth.se>