readme.txt

微软出的CSPDK

=======================================================================================
                Microsoft Cryptographic Service Provider Development Kit
=======================================================================================

        (c) Copyright Microsoft Corporation, 1999 - 2001

This document provides installation instructions for the Microsoft Cryptographic
Service Provider Developement Kit (CSPDK).


======================
1.0  Package Contents
======================

This CSPDK contains:

README.TXT              - This file.
CSPSIGN.EXE             - Program to test sign your CSP.
CSP.DLL                 - Sample CSP.
CSP.SIG                 - Resource based signature for CSP.DLL.
TESTCSP.EXE             - Sample application to test the sample CSP.
CSPINSTL.EXE            - Sample application to install the sample CSP.
\WIN98
        ADVAPI32.DL_    - Modified ADVAPI32.DLL for use on Windows 98.
\WINME
        ADVAPI32.DL_    - Modified ADVAPI32.DLL for use on Windows Millennium.
\NT4\SP3
        ADVAPI32.DL_    - Modified ADVAPI32.DLL for use on Windows NT 4.0 with
                          SP3.
\NT4\SP4
        ADVAPI32.DL_    - Modified ADVAPI32.DLL for use on Windows NT 4.0 with
                          SP4.
\NT4\SP6
        ADVAPI32.DL_    - Modified ADVAPI32.DLL for use on Windows NT 4.0 with
                          SP6.
\WIN2K
        ADVAPI32.DL_    - Modified ADVAPI32.DLL for use on Windows 2000.
\WIN2K\SP1
        ADVAPI32.DL_    - Modified ADVAPI32.DLL for use on Windows 2000 with
                          SP1.
\WIN2K\SP2
        ADVAPI32.DL_    - Modified ADVAPI32.DLL for use on Windows 2000 with
                          SP2.
\CSP
        CSP.C           - Source for the sample CSP.
        AUTOREG.CPP     - Code to self-register this CSP.
        CSP.DEF
        CSP.RC
        CSP.SIG
        RESOURCE.H
\TESTCSP
        TESTCSP.C       - Source for the sample application to test the sample
                          CSP.
\CSPINSTL
        CSPINSTL.C      - Source for the sample application to install the
                          sample CSP.  Using self-registration is preferred, but
                          this is included for backwards compatibility.
\WINCE
        COREDLL.DL_     - Modified COREDLL.DLL for use on Windows CE.
\WINCE\CSP
        CSP.CPP         - Source for the sample CSP.
        CSP.DEF
        MAKEFILE
        SOURCES
\TESTCSP
        TESTCSP.CPP     - Source for the sample application to test the sample
                          CSP.
        MAKEFILE
        SOURCES
\CSPINSTL
        CSPINSTL.CPP    - Source for the sample application to install the
                          sample CSP.
        MAKEFILE
        SOURCES
\DOCS
        SCARDCSP.DOC    - Supplimentary documentation for building a Smart Card
                          based CSP to work with Windows 2000 logon.

\SDKINC
        WINCRYPT.H      - Some older SDK's may not have the CSPDK.H file.  Use
        CSPDK.H           these header files only if your SDK does not contain
                          the CSPDK.H file.


====================================
2.0  CSP Signatures on Windows 2000
====================================

In Windows 2000 the signatures for CSPs can be stored as a resource in the CSP
DLL.  This eliminates the possibility that the signature in the registry will
get out of sync with the CSP DLL.  Storing the signature in the registry is
still supported.  A new version of the signing tool (cspsign.exe) is included on
the disk.

To store the signature in the CSP DLL, you must create a resource in the CSP
DLL.  The resource number must be set to 0x29A and a size of 144 bytes.  Use
cspsign.exe with the 'c' option to sign the DLL.  If the CSP DLL must also work
on Windows 98 or Windows NT 4.0, you may also supply an output signature file
with the 'c' option.  This results in your CSP being signed for all possible
platforms.


===============================
3.0  Installation Instructions
===============================

To install the ADVAPI32.DLL on your Windows 98, Windows NT 4.0 or Windows 2000
computer:

1. Go to the %systemroot%\system32 folder (windows\system for Windows 98).
2. Rename the current advapi.dll to advapi32.bak
3. Expand the appropriate ADVAPI32.DLL for your test platform to the
   %systemroot%\system32 folder (windows\system for Windows 98).
4. Copy the cspsign.exe to the %systemroot%\system32 folder (windows\system for
   Windows 98).
5. Reboot.

Note that on Windows 2000, it may be necessary to do this from DOS or a second
copy of the operating system, in order to bypass the System File Protection
service.

To try the sample CSP and applications:

1. Copy CSP.DLL, CSPINSTL.EXE and TESTCSP.EXE to the %systemroot%\system32
   folder (windows\system for Windows 98).
2. Sign the sample CSP by running the following command line:

   cspSign s csp.dll csp.sig    (Windows 98 and Windows NT 4.0 registry based
                                signature)
   cspSign c csp.dll            (Windows 2000 for DLL resource based signature)
   cspSign c csp.dll csp.sig    (Both)

3. Install the sample CSP by running the command, "regsvr32 csp.dll".
   Alternatively, the old CSPINSTL.EXE program may also be used.
4. Run the sample application by running TESTCSP.EXE

To install the COREDLL.DLL (create a new image with the COREDLL.DLL in the
CSPDK) on your Windows CE computer:

1. Go to the %_FLATRELEASEDIR% folder.
2. Rename coredll.dll to coredll.bak
3. Copy and expand both coredll.dll and cspsign.exe from the CSPDK disk to the
   %_FLATRELEASEDIR% folder.
4. Run makeimg

To try the sample CSP and applications:

1. Copy CSP.DLL, CSPINSTL.EXE and TESTCSP.EXE to the %_FLATRELEASEDIR% folder.
2. Sign the sample CSP by running the following command line:

   cspSign s csp.dll csp.sig

3. Install the sample CSP by running CSPINSTL.EXE
4. Run the sample application by running TESTCSP.EXE

Note: To set the name of the CSP, its provider type and filename, edit
inc\csp.h.


================================
4.0  Adding a CSP to Windows CE
================================

In order to install a Cryptographic Service Provider to Windows CE, certain
entries must be added to the registry.  These registry changes can be made in
the platform.reg file when the CSP is pre-installed in the firmware of a CE
device.  If the CSP is being installed on an existing CE device, an installation
program may be needed to make these changes.

The example registry entries below show the changes needed to add a type 2
(PROV_RSA_SIG) CSP named "XYZ Crypto Service Provider" implemented in
xyzcsp.dll.  The "Signature" is a binary entry containing the output of the
signing tool.


[HKEY_LOCAL_MACHINE\Comm\Security\Crypto\Defaults\Provider\XYZ Crypto Service Provider]
    "Image Path"="\\Windows\\xyzcsp.dll"
    "Type"=dword:00000002
; ******** Different signature for each processor *******************
IF _TGTCPU=i486
"Signature"=hex:17,5e,5c,b3,dd,70,11,21,c7,23,9a,77,48,c0,2b,2f,\
                23,d3,40,c4,60,0c,15,87,e9,0b,a2,0b,b8,78,29,25,\
                09,92,3a,97,65,29,af,4e,3f,97,c8,57,e0,a3,c7,aa,\
                ce,ac,41,33,d2,2e,08,12,4a,4e,01,9a,1d,57,da,13,\
                e2,02,53,85,57,cb,56,d9,82,57,f1,df,b3,5b,65,19,\
                4b,4c,37,75,04,40,d1,0a,25,3f,67,b1,ea,b2,20,1c,\
                52,63,3c,f7,99,85,60,26,85,1b,e0,e9,49,66,01,3c,\
                ac,ad,2c,a3,6f,66,10,f1,9b,bb,8a,4c,24,e7,68,85,\
                00,00,00,00,00,00,00,00
ENDIF


If the CSP is going to be the default provider of a particular type, the
following entry must also be made:

[HKEY_LOCAL_MACHINE\Comm\Security\Crypto\Defaults\Provider Types\Type 002]
"Name"="XYZ Crypto Service Provider"