Stable now and works as expected. Thank you!
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Nov 24 2020
Nov 19 2020
I'm still having problems with 2.2.24. Now the card removal is detected correctly, but the initialization fails.
Sep 28 2020
This is also what I found out with my tests with the libvirt usb: removing and redirecting back the device got it working again.
Sep 26 2020
Ok. Tried to test this with master, but failed. I got it compiled and installed, and it actually detected the first removal after reboot/suspend/reader attach/whatever reason, but after that when I inserted the card back, it didn't function anymore. I suppose you also tried that? I mean that's the use case, I suppose: to be able to remove/insert the card reliably all day long.
Sep 24 2020
Nice, thanks! If I want to try this fix, should I just compile the master tree?
Sep 23 2020
I also don't want to leave my card in the reader authenticated for a full day, it just doesn't sound like a good practice to me. I also very often just forget about the card, so it just sits there, keys open for use.
Sep 17 2020
This is everything lsusb knows about the device:
Just wanted to add to my initial findings:
- I was not using proprietary drivers (libscmccid.so.5.0.35), because the installer script fails to install on default CentOS 8 pcsc-lite. So the distribution pcsc-lite also doesn't have this issue.
- Fastest way to test this condition is to just detach/attach the reader device.
- Proprietary drivers doesn't support secure pin entry!
Sep 14 2020
Thanks for prompt answer!