The recommended way for NESCM to communicate with the smart card is by using PC Smart Card interfaces (PC/SC). When using PC/SC interfaces, the smart card middleware vendor provides a Windows Cryptographic Service Provider (CSP). The method automatically detects the uses of the proper CSP.
CSP with PC/SC interfaces works with most smart card middleware on Windows.
If CSP with PC/SC interfaces communication is failing or you know that your smart card vendor doesn’t provide a CSP, you might want to try a PKCS#11 library. When you use a PKCS#11 library, you must specify the correct library (DLL) name. PKCS#11 libraries are vendor-specific, so you need to check with your vendor for the name of the library.
If the library file is not present in the default system path, you must provide the file path of the library file.
Table A-1 lists common PKCS#11 libraries:
Table A-1 Common Vendors and PKCS#11 Libraries
|
Vendor |
PKCS#11 Library Name |
|---|---|
|
ActivCard |
acpkcs211.dll |
|
Netsign |
core32.dll |
|
GemPlus |
gclib.dll |
|
eToken |
eTpkcs11.dll |
|
Cryptovision |
cvP11.dll |
|
Rainbow iKey* |
ckdk201.dll (Only the PKCS#11 mode is functional for iKey devices) |
For information on choosing the smart card interface, see Smart Card Interface.