I found Your e-mail at rdesktop mailing list.
I'm also developing smart card redirection.
I created sniffer that filters packets associated with smart cards, I know that
theese packets go through driver channel and then all of them should be passed
to device_control function. I also found that in some of them there are APDU
messages that can be send directly to the card reader, but between driver
channel and apdu messages there are at least one more layer which I don't
understand. As You wrote in Your e-mail it can be RPC/COM/DCOM
Do You have any more informations about that ? Where did You find it is a kind
of RPC ? maybe I will find any more informations there ? Do You know any
knowledge base about smart cards redirection ?
Thanks in advance for any help.
----- Original Message -----
> I've tried to do smart card redirection some time ago, but I wasn't very
> Here's some info on what I found out about SCARD-redirection:
> The server is communicating with the sc resource manager at the client, not
directly to a device driver (at least not initially) as with the other
redirections (disk/serial etc). So the mechanism used is not IRP's but some
form of IPC (RPC/COM/DCOM?) encapsulated in a redirection packet. The
parameters are NDR encoded (Network Data Representation, which is used by MS
for RPC/COM/DCOM). So to do scard redirection first there must be NDR routines,
which requires knowledge of the MS IDL compiler. I understand Samba4 has NDR-
routines, but I haven't had the time to look at them. I wasn't able to find
much useful information about NDR on the web either, because this is pretty MS-
> Hope this helps...
Get latest updates about Open Source Projects, Conferences and News.