Writing a CSP
This section outlines the steps used to write, test, and implement a custom cryptographic service provider (CSP).
Before writing a CSP for use with a smart card, consider writing a Smart card modules that acts as a plug-in for the Microsoft Base Smart Card Cryptographic Service Provider
Before writing a CSP, a writer must accomplish two tasks:
- Select the cryptographic algorithms and data formats to be included.
- Obtain implementations for each algorithm and data format.
After these tasks have been accomplished, a custom CSP can be created.
To create a custom CSP
- Create the CSP DLL that exposes the CryptoAPI functions.
- Write the CSP setup program that creates the appropriate registry entries.
- Test the CSP, or for Windows 2000, Test signing the CSP.
- Get the CSP signed.
- Test the officially signed CSP. This is the same as step 4, except that the official signature and release version of the operating system are used.
Private Key Caching
If the CSP you are writing will cache private keys, there are certain registry settings that your CSP must use to determine whether and how the private keys are cached. For more information, see Private Key Caching Constants.
Send comments about this topic to Microsoft
Build date: 9/7/2011
