If you have both /dev/bus/usb and /proc/bus/usb that is a bug in your
system config and can trigger this. udev will start two processes,
one tries the /dev/bus/usb device, one tries the /proc/bus/usb device,
and the one who can claim the interface wins.
remove either /dev/bus/usb or /proc/bus/usb or edit the openct udev
script in /lib/udev to ignore requests for one of those two.
but for most users it is not important at all which reader has their
smart card (e.g. if you use opensc-pkcs#11 and the application simply
looks at all slots), so this is a minor problem from my point of view.
still for low level tools like openct-tool, opensc-took, pkcs15-init
etc. you need to enter the reader number, so it might be annoying.
This is an annoyance because my ssh-agent gets confused across
unplug/replugs when the card changes identifiers, and i have to reload
the keys for it.
If i can help in debugging this at all, please let me know.
true. for some reason this never happends on my machines. maybe ubuntu
does something different? if you only have /dev/bus or /proc/bus
but not both, and the problem still happends, then there is a big
problem and we need to debug it. but for the time being I guess it
is the dual /dev/bus and /proc/bus that is causing the problems.
Regards, Andreas
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
