Utimaco Bind 9, Руководство по интеграции

Страница: 11 / 20

3. Additionally Microsoft Visual Studio is required to build OpenSSL and BIND. Microsoft Visual
Studio 2005 (Visual Studio 8) with Service Pack 1 and Service Pack 1 Update for Windows
Vista
5
is used here.
4. Set necessary environment variables for running Visual Studio from the command line, run the
following command from the command line:
”C:\Program Files\Microsoft\Visual Studio 8\Common7\
Tools\vsvars32.bat”
5. Configure OpenSSL as follows:
cd openssl-0.9.8l
perl Configure VC-WIN32 \
--pk11-libname=c:/windows/system32/cs2_pkcsll.dll \
--pk11-flavor=crypto-accelerator
The given pk11-libname parameter points to the path of the PKCS#11 library, pk11-flavor de-
termines which kind of PKCS#11 engine (provided by the patch) is used - sign-only or crypto-
accelerator. The optional prefix parameter would point to the directory where the libraries and
the OpenSSL configuration file are additionally copied during the installation of OpenSSL.
6. Build OpenSSL with these command line tools
ms\do_masm
nmake -f ms\ntdll.mak
7. Check the availability of the engine before you install BIND running the command:
out32dll\openssl.exe engine pkcs11 -t
If the previuous check isn’t successfully, test the accessibility of the PKCS#11 slot first.
p11tool slot=0 GetSlotInfo
The folder out32dll now contains the PKCS#11 enabled OpenSSL libraries for BIND.
8. Make the modified OpenSSL suite available in c:\usr\local\ssl or to the directory specified by
the prefix parameter in configuration by running the command:
nmake -f ms\ntdll.mak install
5
Service Pack 1 and Service Pack 1 Update for Windows Vista - http://support.microsoft.com/kb/929470
Page 11