To work with the smart card support in Microsoft Windows operating systems, smart card readers and cards should be compatible with Interoperability Specification for ICCs and Personal Computer Systems. Smart card readers and device drivers should also be Plug and Play compliant.
Issues with Card Minidriver Certification Kit (CMCK) June 2007 Release
The following issues have been found in CMCK since its release in the June 2007 Client release of the Windows Logo Kit (WLK 1.0.c). | • | Missing CardGetContainerInfo test case for non-authenticated user. CardGetContainerInfo must return container information even if the caller is not authenticated. Currently, no test case covers this requirement. | | • | CardSignData CARD_PADDING_PSS test does not ensure the key size is sufficient for the hash algorithm used. The CardSignData test for padding uses the maximum key size supported by the card. However, if your card minidriver uses the supplied pad data callback and supports a maximum RSA key size of less than 1024 bits, then the CardSignData test fails certain combinations of the CALG_SHA_XXX hash algorithms and PSS padding. | | • | CardSignData positive and PaddingInfoSupport tests. When testing CardSignData with the CARD_BUFFER_SIZE_ONLY flag, the version of the signing information structure is incorrectly set to CARD_SIGNING_INFO_BASIC_VERSION. Support for this flag is configurable in the cmck_config.xml file, so the test can be skipped by omitting this flag. | | • | NoMemoryLeaks uses an AT_SIGNATURE key to decrypt data. In the NoMemoryLeaks test, an AT_SIGNATURE key is used to decrypt data. |
Smart Card Smart Card and Biometric Device Specifications Input Developer References
| |
