On 02/01/06, Peter Williams <[EMAIL PROTECTED]> wrote:
> Im missing something. But it is interesting.
>
> The request is : identify the current bus/node/lun supporting a connection
> to a CCID instance
> The proposed solution is: identify the PID/VID ("USB identification serial
> numbers") reported by the CCID firmware?The initial request was not very clear. Your point is interesting. > There is surely nothing to validate the PID/VID reported by the remote CCID, > unless PC/SC starts requiring the PID/VID to be signed by a controlling > authority, so the report can be verified as authoritative. The PID/VID is a static information returned by the reader to the driver. If you do not trust the driver I don't know what you can do. Or what do you mean by "validate the PID/VID"? > Then one might > ask: is this even addressing the original need to know: on which (trusted) > bus is the CCID bound? That is an easy question: when libusb is used the bus/node identification is sent by pcscd to the driver so they both use the same device. You can see it in the logs as: hotplug_libusb.c:404:HPAddHotPluggable() Adding USB device: 002:072 bus = 002 node = 072 This information is defined by libusb and the format is OS specific. Bye, -- Dr. Ludovic Rousseau _______________________________________________ Muscle mailing list [email protected] http://lists.drizzle.com/mailman/listinfo/muscle
