Doug Engert

Good to hear it works. The problem with OpenSC was finding the PKCS15 files. https://github.com/OpenSC/OpenSC/issues/2591#issuecomment-1213001492 If you want to look for the starting location, you can get a trace from...

> would you like more info ? Yes, the log looks like you ran an OpenSC program. What we need to to ruin one of their commands. Or try something...

If their PKCS11 module works, I would suggest using it. On any PKCS11 application you can point to their module. It would also mean that your IT people could help...

Some what helpful. It at lease says it is a "CardOS V5.3, 2014" But that just says what OS it has. It does not say how they initialized the file...

I agree with @popovec I also think the card driver should be able to turn this off especially if the card does not have some update counter. Even if card...

What token do you have? `opensc-tool -a` will show the ATR. You can lookup the ATR at: https://smartcard-atr.apdu.fr/ Does the token work on any other system? Does it have keys...

Problem appears to be "Security status not satisfied". In line 2429 "card.c:733:sc_update_binary: called; 128 bytes at index 0" an attempt to write to the card ends in line 2466 card...

Also see: https://github.com/OpenSC/OpenSC/issues/2018#issuecomment-621100431 and use of --use-default-transport-key

Look at `/usr/share/opensc/entersafe.profile` to see what is the syntax error. https://github.com/OpenSC/OpenSC/blob/master/src/pkcs15init/profile.c#L1298 (Unfortunately it does not listed the line number.)

Although d06f23e89 does not log pin commands to avoid exposing the PIN unless debug >= SC_LOG_DEBUG_PIN