Thanks. I am really trying to track down why the CSP fails to find the requested container under certain conditions when our reader driver is used. This has occurred on two 3rd party SC middleware packages so far.
My understanding is that the when CryptAcquireContext is called, its implementation is supposed to look at all the containers is knows of. In both of these cases each of the vendors tools can read the card information, but functions like Run As Other User fail when a cert is used on our virtual reader driver.
Nik Twerdochlib
Software Developer
+1.601.607.8309 O
+1.866.522.8678 F
BOMGAR | Enterprise Remote Support™
One of the Fastest-Growing Technology Companies in America | Technology Fast 500™
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@microsoft.com
Sent: Friday, May 25, 2012 3:58 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] CSP for Smart Card
The latest document for smart card CSPs is here: http://msdn.microsoft.com/en-us/library/ms953432.aspx
If you implement a vendor CSP, then the MS Base SC CSP would not be used as the smart card (but not the reader) would be registered in the smart card database to use the vendor’s CSP.
Note that Microsoft strongly discourages vendors implementing their own smart cards CSPs and rather prefer using the in-box CSP/KSP with a vendor mini-driver. It’s easy to do the wrong thing in a CSP and in many cases, it could prevent getting a software logo (I don’t know all the requirements).
-Jeff
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer