[Muscle] Driver for remote card reader

[Ludovic Rousseau]

On 25/10/06, Peter Koch <pk_opensc at gmx.net> wrote:
> Dear MUSCLE mailing list:

Hello,

> This is a windows related questing,

Argh!         :-)

> I would like to write a driver for a (virtual) card reader that will talk to a (real) card reader on a remote system. I'm trying to do this OS-independent. So it should be possible to connect to a card reader on a Windows-system from a unix system and vice-versa.
>
> So far I'm almost finished with an ifd_handler for pcsclite and a server-programm that has to run on the machine where the real card reader is located. I do know (at least in theory) how to write the server-programm such that it can be compiled under both unix and windows.
>
> But how do I write an ifd_handler under windows?
>
> I just got the Microsoft DDK from a friend. Do I have to write a WDM-driver (which would be a real pain for a unix-focussed person like me)? Or do I mistake writing a Windows-Driver with writing an IFD-Handler? I was hoping that writing an IFD_handler would be comparable to writing a GINA-dll or a PKCS#11-dll (which I have done in the past - without the need to use the DDK). But I cannot find any documentation about  the "Windows Smart Card Reader IFD-Handler API".
>
> Where can I find some sample source?
>
> What do you think about all this? All hints or comments are greatly appreciated.

I don't know if what you want to do is possible. If the reader is
already detected and used by Windows you should not have the
opportunity to use the _same_ reader with _another_ driver at the same
time. Or the reader will only be accessible using your redirection
driver, even for a local use? Or no local use will ever be possible?

You may end up redesigning a resource manager like pcsc-lite. Maybe a
better approach is to proxy the PC/SC calls from the client to the
server.

The PC/SC API should be easy to wrap in RPC calls. I don't know if
WIndows as xrd(3) and rpc(3) calls.

Bye,

-- 
  Dr. Ludovic Rousseau