[Pcsclite-muscle] How to Identify USB devices on linux/ubuntu/debian

[Uv Wildner]

Exactly, 

however, I seem to have no control which reader with which card goes to each container. 
As I mentioned before I am worried that this will kill a few of our test cases... 
I will come back when I need and/or found a better solution. 



From: "Ludovic Rousseau" <ludovic.rousseau at gmail.com> 
To: "pcsclite-muscle" <pcsclite-muscle at lists.alioth.debian.org> 
Sent: Monday, January 30, 2017 4:59:23 PM 
Subject: Re: [Pcsclite-muscle] How to Identify USB devices on linux/ubuntu/debian 



2017-01-30 14:41 GMT+01:00 Uv Wildner < uv.wildner.ext at openlimit.com > : 



I see, the stack introduces a level of abstraction which discards this information. 

I will try to workaround this by reinitializing the crypto parts each time. 
I hope I can cover all my test cases like this. 

So for the use case: 

In an automated test setup I will be running a number of containerized systems needing exactly one card reader containing the right card. 

On the host level I am assigning a USB device to the container , inside the container I am just using the first card available. 



So each container will see exactly 1 smart card reader at the USB level. 
Each container will have its own pcscd. 
pcscd executed inside the container will list exactly 1 smart card reader at the PC/SC level. 

Am I right? 


BQ_BEGIN

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. 

Thanks a lot for the quick & efficient support!!! 

BQ_END

You are welcome. 

Bye 
-- 
Dr. Ludovic Rousseau 

_______________________________________________ 
Pcsclite-muscle mailing list 
Pcsclite-muscle at lists.alioth.debian.org 
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pcsclite-muscle 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pcsclite-muscle/attachments/20170130/775d3b40/attachment-0001.html>