Re: [FYI PATCH] restrict pcscd to a single USB port / path
Ludovic, greetings --
On Wed, Mar 27, 2013 at 3:45 PM, Ludovic Rousseau
<[hidden email]> wrote:
> The MUSCLE list  is a better place to talk about PC/SC and pcsc-lite.
Ok. If I have anything else to add, I'll subscribe and submit there.
>> My current project had the requirement to only recognize the crypto
>> token on a specific USB port.
> Why do you have this requirement?
Well, the short answer is: because that's what the customer asked for.
Longer answer is that this device also offer USB-over-IP capabilities,
on a different USB port; without being able to distinguish between the
two, it would be hard to say whether the device is supposed to use the
crypto token directly, or if it is supposed to make it available over
TCP/IP and not use it itself.
Weak, but that's how the thing is designed, and that's what the spec says.
> It may be a good idea and I may included it in mainline. But I do not
> yet understand why someone would need this.
This device was originally specified years ago; if we ever get a
chance to do a v2, we hope that we can get rid of some of the cruft.
But for now, I'm stuck with the spec as written.
Thanks again for your feedback, and everyone's work on the code already.