On 16/01/07, Alon Bar-Lev <[EMAIL PROTECTED]> wrote:
On 1/16/07, Ludovic Rousseau <[EMAIL PROTECTED]> wrote:
> > This causes problems with PKCS#11 providers that fix the reader list
> > when C_Initialize is called.
>
> So it is a bug in the PKCS#11 provider. No?
No.
PKCS#11 specification states a static reader map...
I don't find this in the specification. It is true only if you map one
reader on one slot. But the PKCS#11 provider may also have virtual
slots (slots not directly connected to a reader).
> You do not have to modify pcscd. Just write a driver that will fake a
> reader. The driver will return "no card" if the reader is not
> connected, and will return "card present" if the reader is connected.
True... Using serial interface configure in /etc/reader.conf, right?
Using the serial interface is simpler since the driver will be called
even if no reader is present.
It is different with a USB driver since pcscd will call he driver only
when a reader corresponding to the driver ProductID and MaunfacturerID
stored in Info.plist is connected. But you could use the ProductID and
MaunfacturerID of the always connected USB mouse for example so the
driver is always called.
But how does the feature of hotplug help such implementation?
It does not help in this case.
Can you please explain?
I don't want the driver to poll the USB bus, now that pcscd support
the hotplug event, I would like it to pass the event also to the
driver so it know to scan the USB bus only when needed.
What you could do is use udev to generate an event used by the driver.
For hotplug I use SIGUSR1. SIGUSR2 is still free.
I think it is a bad idea to provide a virtual reader at the PC/SC
layer when the problem can be solved with a virtual slot at the
PKCS#11 layer. The problem is not in PC/SC but in the PKCS#11
provider (and/or PKCS#11 API).
Bye,
--
Dr. Ludovic Rousseau
_______________________________________________
Muscle mailing list
[email protected]
http://lists.drizzle.com/mailman/listinfo/muscle
