Doug Engert

https://github.com/OpenSC/OpenSC/actions/runs/8007038458/job/21870535578?pr=3042 ran OK Thu, 22 Feb 2024 15:44:52 GMT to Thu, 22 Feb 2024 15:44:52 GMT about an hour ago.

This may be related to #2843 To help identify your ePass2003 type can you run: `opensc-tool --card-driver default -a --send-apdu 00:CA:01:86:00`

PIV specs also have a "pin_policy" which says if global or local pin can be be used and other things if SM is used: line 424: `unsigned int pin_policy; /*...

Thanks for the review. I would also request any developers (MyEID?) who might want to use the NIST PIV SM in some other card driver also comment on their plans....

https://github.com/OpenSC/OpenSC/pull/3098/commits/388929c3c2ad6c754c4efb8fd79e6601793f096c works. I will look closer at what code in sm-nist could be removed and at squashing many of the commits. If you want I can post an opensc-debug log.

Cool.

This problem maybe in other card drivers, as some also use the reader_lock_obtained feature. https://github.com/OpenSC/OpenSC/blob/master/src/libopensc/card-piv.c#L6139-L6143 added by f6b4a2e658 does have a TODO that this code might be called recursively. Looks...

You mentioned the word "suspend" in the original issue. What OS are you using and is this "sleep" or "hibernate". These present special situations as while in sleep or hibernation...

You may need to link OpenSC with boringssl as there maybe a conflict if Chrome is using boringssl and OpenSC is using OpenSSL.

We live in a smart card jungle: - applets that can be loaded on almost any card, so the way to identify the applet is not by ATR, but by...