|
I can confirm what Jan has observed, no change. It still does not
prompt for a pin. debug1: pkcs11_start_helper: starting /usr/lib/openssh/ssh-pkcs11-helper -vvv debug3: pkcs11_init: called, interactive = 0 debug1: process_add debug3: process_add: add /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so debug1: provider /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so: manufacturerID <OpenSC Project> cryptokiVersion 2.20 libraryDescription <OpenSC smartcard framework> libraryVersion 0.26 debug1: provider /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so slot 0: label <PIV_II> manufacturerID <piv_II> model <PKCS#15 emulated> serial <3412b080a610d7e8> flags 0x40d pin required debug1: pkcs11_provider_finalize: provider "/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so" refcount 1 valid 1 debug1: pkcs11_provider_unref: provider "/usr/lib/x86_64-linux-gnu/opensc-pkcs11.so" refcount 1 debug1: pkcs11_add_provider: provider /usr/lib/x86_64-linux-gnu/opensc-pkcs11.so returned no keys debug1: pkcs11_add_provider: no keys; terminate helper debug1: read eof On 10/10/25 10:27, Jan Nordholz wrote:
Hi Colin, just grabbed 10.2p1-1 from incoming. No change in behavior, enumeration of pkcs11 keys fails with "pin required" as it did with 10.1p1-2, only having the keys added to the agent makes the connection succeed. Jan |