<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 12pt; color: #000000"><div>I see, the stack introduces a level of abstraction which discards this information. <br></div><div><br data-mce-bogus="1"></div><div><div>I will try to workaround this by reinitializing the crypto parts each time. <br>I hope I can cover all my test cases like this. <br></div><div><br></div></div><div>So for the use case:<br><br>In an automated test setup I will be running a number of containerized systems needing exactly one card reader containing the right card. <br></div><div><br data-mce-bogus="1"></div><div>On the host level I am assigning a USB device to the container , inside the container I am just using the first card available. <br></div><div><br data-mce-bogus="1"></div><div>When the (usb) device - card mapping is going wrong I will end up in encryption problems when the wrong card with the wrong key is connected to my current container. </div><div><br data-mce-bogus="1"></div><div>Thanks a lot for the quick & efficient support!!!</div><div><br data-mce-bogus="1"></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Ludovic Rousseau" <ludovic.rousseau@gmail.com><br><b>To: </b>"pcsclite-muscle" <pcsclite-muscle@lists.alioth.debian.org><br><b>Sent: </b>Monday, January 30, 2017 2:19:53 PM<br><b>Subject: </b>Re: [Pcsclite-muscle] How to Identify USB devices on linux/ubuntu/debian<br></div><br><div data-marker="__QUOTED_TEXT__"><div dir="ltr">2017-01-30 13:28 GMT+01:00 Uv Wildner <<a href="mailto:uv.wildner.ext@openlimit.com" target="_blank">uv.wildner.ext@openlimit.com</a>>:<br>> Hello,<br><br>Hi,<br> <br>> so the API does not provide for the USB device information. That's too bad. :(<br><br>A smart card reader is not always a USB device.<br>When PC/SC was designed smart card readers were serial devices connected to a serial port.<br><br>> I wonder where that information about the device to card reader mapping gets lost, as it obviously is needed somewhere in the stack?!?!<br><br>The information is present in pcsc-lite and in the CCID driver.<br>For example pcscd calls libccid with a parameter like "usb:08e6/3437:libudev:0:/dev/bus/usb/001/002"<br><a href="http://pcsclite.alioth.debian.org/api/group__IFDHandler.html#gabb9fe35a68fa080ce9397f0b830b1e7e" target="_blank">http://pcsclite.alioth.debian.org/api/group__IFDHandler.html#gabb9fe35a68fa080ce9397f0b830b1e7e</a><br><br>My question was and still is: why do you need this information at the application level?<br><br>Bye<br><br>--<br> Dr. Ludovic Rousseau</div>
<br>_______________________________________________<br>Pcsclite-muscle mailing list<br>Pcsclite-muscle@lists.alioth.debian.org<br>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pcsclite-muscle<br></div></div></body></html>