Jump-start your project by learning from devs who
write Windows drivers and file systems every day.
Take an OSR seminar!

OSR is Hiring! Click here to find out more.

Windows Internals & Software Drivers Lab, Santa Clara, CA 5-9 August, 2013
Kernel Debugging & Crash Analysis for Windows Lab, Santa Clara, CA 9-13 September, 2013
Upcoming OSR Seminars:
Writing WDF Drivers for Windows Lab, Boston, MA 7-11 October, 2013
Developing File Systems for Windows, Seattle, WA 5-8 November, 2013


Go Back   OSR Online Lists > ntdev
Welcome, Guest
You must login to post to this list
  Message 1 of 4  
15 Jun 12 12:54
Hans-Jürgen Reindt
xxxxxx@kobil.de
Join Date: 15 Jun 2012
Posts To This List: 11
smclib and UMDF

Hello, I'm about to implement an UMDF smartcard reader driver. In the course of "collecting" all needed Interfaces and APIs I found no user mode pendant to the smclib (which is only for kernel mode) to handle IOCTLs. Do I have to implement it all by myself or are there other possibilities with UMDF to manage the smartcard states and the reader? Microsoft has released an UMDF driver for CCID devices on Vista and Windows 7. If Microsoft used the smclib, how did they solve the problem ? I appreciate any help on this topic. Thank you in advance, Hans.
  Message 2 of 4  
18 Jun 12 09:33
deMarsKamel
xxxxxx@hotmail.com
Join Date: 03 Nov 2010
Posts To This List: 80
RE: smclib and UMDF

Hello Hans, For use the SMCLib, you need to use the Winscard.dll in user mode. After for the UMDF driver, you just need to call ioDeviceControl for trigger all callBack ( sCardPower, sCardTransmit, and so on .... ). Open the SMCLIB.h for extract all IOCTL dedicated to smartcard function. I hope to help you, ps : sorry for my bad english, Best regards, Kamel
  Message 3 of 4  
19 Jun 12 10:30
Hans-Jürgen Reindt
xxxxxx@kobil.de
Join Date: 15 Jun 2012
Posts To This List: 11
RE: smclib and UMDF

Kamel, thank you for the reply. Please correct me if I'm wrong in the following. I suppose you mean BOOL WINAPI DeviceIoControl(...) from kernel.lib . The way I understand this function, it expects an installed device to communicate with. To install a device I already need a driver. And therefor i asked the question above. The winscard.dll is, as far as I know, used by applications and by the Smartcard-Service. If I call this DLL from my UMDF driver, somewhere below this layer I still need a driver to service my hardware (all the IOCTLs including the vendor specific ones). The inbox usbccid/WUDFccid driver will support a great part of the IOCTLs and for the rest I'll need at least an upper filter driver ontop of the inbox driver (supplied from Microsoft). This might yield in a complicated installation and I cannot use this solution for XP, which is a drawback. It should be more handsome when I own the complete (UMDF) driver code, and thats what I aim for. I found similar conclusions in an older thread on NTDEV (http://www.osronline.com/showThread.cfm?link=194779). But meanwhile we have Windows 8 RC and I wonder if there are new possibilities concerning UMDF smarcard reader drivers. From my current knowledge it seems to me that I will have to move to KMDF when I want to do it with only one driver (one project). To (re)implement the smclib seems to me too much time consuming. Has somebody an alternative idea? A way to access the smclib from UMDF? I appreciate any help on this topic. Thank you , Hans.
  Message 4 of 4  
26 Jun 12 04:22
Karthikeyan M
xxxxxx@yahoo.com
Join Date: 12 Mar 2010
Posts To This List: 16
RE: smclib and UMDF

I beleive MS has ported the SMCLIB to user mode. If possible try to get in touch with MS they will be able to help you on this. As far as porting SMCLIB you can get the whole source code of SMCLIB from Windows CE evaluation kit.
Posting Rules  
You may not post new threads
You may not post replies
You may not post attachments
You must login to OSR Online AND be a member of the ntdev list to be able to post.

All times are GMT -5. The time now is 22:56.


Copyright ©2012, OSR Open Systems Resources, Inc.
Based on vBulletin Copyright ©2000 - 2005, Jelsoft Enterprises Ltd.
Modified under license