Ryan Hurst
Ryan Hurst
Can you tell us more about this token, for example it’s make and model. What PKCS11 library you use with it.
Where is the library installed on your operating system; the fully qualified path would help.
``` { "cards": [{ "atr": "3bff1300008131fe450031b9640444ecc17394018082900012", "name": "Croatian eID", "driver": "9007F496D91C254C5C2F84453B“ }], "drivers": [{ "id": "9007F496D91C254C5C2F84453B", "name": "Croatian eID", "file": { "linux": "/usr/local/lib/pkcs11/libEidPkcs11.dylib" } }] } ``` In theory if...
It seems like the P11 library doesnt support KR_MECHANISM_INVALID:112\n at Error (native) C_GetMechanismInfo. We need @microshine to confirm what we can do.
@sdzakic please run the test app and share output
It’s unclear which “list” your referring to. I am not sure what “A3” is. If logging is enabled you can see all interactions, including what P11 libraries are loaded for...
@kranidiotis Can you give us some more information, is this a token that can be used for cryptographic operations like document signing? If not, maybe the right thing for us...
It looks like this may be a generic ATR for NFC cards supposedly compliant with ISO 14443 Type B? If so it may not be possible to use with Fortify...
Interesting; since it is an IDPrime based cared it may work with SafeNet SAC client. @kranidiotis do you use this middleware? If so I think this will work: ``` {...
This was reported here also : https://github.com/PeculiarVentures/fortify/issues/155