Read the README.WIN32.txt file first. 

	After doing the nmake -f gsi.mak the .\out32
	will have all the executables, libs and dlls. 
	The .\inc32 will have the header files 

	The gsilib32.dll, gssapi32.dll, gaalib32.dll  and 
	gsigss32.dll can be copied to \windows or some other 
	directory in the path. 
	(But first see below if you have Kerberos installed.)

Other files of interest for WIN32:
   

	x509.bat - Used to set the environment variables which can be used 
		to find the files. You will need to customize this for your
		environment. This can be called for autoexec.bat for testing. 

		See the wgpi on how to use the registry instead. 

	ssleay.conf - Configuration file used to get the first certificate. 

	certreq.bat - Used to generate a user key and request. Calls ssleay
		with the ssleay.conf 

	42864e48.0 - The certificate of the Globus CA. This is used to check
		signatures of other certificates. 

	gaa\ca-signing-policy.conf.in - File to verify a CA is following 
			its policies of signing only certificate of the proper 
			form. You may need to edit this if you add other CA 
			certificates. 
 
	grid-proxy-init.exe - Program to get a short term certificate using 
		your certificate. Uses the environment variables as set byi
		x509.bat or the registry.

	grid-proxy-destroy.exe - Program to destroy the shortterm certificate. 

	wgpi - Windows GUI version of globus-proxy-init. Can be used 
		to set the file names into the registry. See the options button. 
		This needs to be built seperatly as a VC++ project. 

	scload - loads a certificate and key onto a smartcard. 

Steps to install:

	Copy the out32\*.dll to c:\windows or keep in your path. 
	(See below if you already have Kerberos GSSAPI gssapi32.dll 
	 installed.)

	If you want to use the environment instead of the registry, 
	edit the x509.bat file, so it points at your home directory. 
	There will eventially be two files and a directory there.
	usercert.pem, userkey.pem and certificates. 
	
	Create the globus and globus\certificates as defined in x509.bat

	Copy the 42864e48.0 file to the globus\certificates\42864e48.0 
	
	Copy the gaa\ca-signing-policy.conf.in to the 
	globus\certificates\ca-signing-policy.conf

	run the certreq.bat script. Respond with your organization name,
	like Argonne National Laboratory, Your department, like ECT, and
	your name like Doug Engert. This will create two files,
	newkey.pem and newreq.pem. 

	Mail the newreq.pem to ca@globus.org
	
	Copy newkey.pem to globus\userkey.pem

	When the CA returns the certificate, save it as globus\usercert.pem
	The full e-mail maybe saved, as the extra stuff is treaded as comments. 
	(The real certificate is the lines ---BEGIN... ---END) 
 
	Add a call to the x509.bat from autoexec.bat, or add the lines to it.
How to use:

	Run the wgpi (Windows Grid Proxy Init) Select Options and set 
	the above file names which you set in the x509.bat. This will 
	add them to the Registry, so the X509.bat is not needed. 

	Or 
	   
	Have the x509.bat set the environment, run the grid-proxy-init
	from a DOS window. This will create the X509_USER_PROXY file. 

	Run an applications which uses the gssapi, like SecureCRT
	from VanDyke, http://www.vandyke.com
  
	The Environment variables take presedence over the Registry. 


Notes for using Smartcard:

	The WGPI now has the option to do the fololowing for you:
	If you want to use the PKCS#11 smartcard, use regedit to add 
	the following key to the registry:

         [HKEY_CURRENT_USER\Software\Globus\GSI]
	     "PKCS11.DLL"="Core32.dll"

	Where Core32.dll is the name of the Smartcard Vendor's 
	Netscape Security Module which is a PKCS#11 DLL. 
	Core32.dll is the Litronic NetSign name. 

	When using a Smartcard, use: SC::<name> for the x509_user_cert
	and the x509_user_key. <name> is the label of the object on 
	the card, See the Netscape Security for the name, or dump the card. 
	Our Globus card handed out at SC98 used Globus for the <name>. 

Notes for those who want to use Kerberos and the GSI. 

	Both Kerberos and GSI have a gssapi32.dll. To allow
	you to select at execution time, you can use the gssapi32c.dll
	instead. You need to do the following:

		rename the Kerberos gssapi32.dll to gssapi32k5.dll
		copy the GSI gssapi32.dll        to gssapi32gsi.dll
		copy the GSI gssapi32c.dll       to gssapi32.dll

	This is a temporary measure. The GSSAPI Mechglue should
	address this in the future. 

	(This might even work with a DCE gssapi32.dll is there is one. 
	 See the gssapi_ssleay\gss_mech_choose.c for more info.)


 Douglas E. Engert  <DEEngert@anl.gov>
 Argonne National Laboratory
 9700 South Cass Avenue
 Argonne, Illinois  60439 
 (630) 252-5444
