Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change driver for the '3BDF18008131FE7D006B020C0182011101434E53103180FC' token #423

Closed
defacto64 opened this issue Jul 2, 2021 · 2 comments
Assignees

Comments

@defacto64
Copy link

Hello,

the smartcard with ATR=="3BDF18008131FE7D006B020C0182011101434E53103180FC" is an "Athena ASEPCOS-TS/CNS 1.82" type of token, and should therefore be driven by the 29a2bd60c4b841c686be68d2874c0c02 driver, otherwise some functionalities (e.g. digital signatures) are inaccessible.

The above ATR is currently mapped to the generic opensc-pkcs11 driver, preventing full exploiting of the card. Besides, even when the card is only used for client authentication, the underlying file system can come in variations that are not correctly handled by opensc-pkcs11 even when digital signatures certs are not present, while they're supported by the proprietary (IDProtect Client) driver.

microshine added a commit to PeculiarVentures/webcrypto-local that referenced this issue Jul 3, 2021
@microshine
Copy link
Collaborator

I changed the driver for that ATR

https://github.com/PeculiarVentures/webcrypto-local/blob/master/packages/cards/lib/card.json#L309-L311

The new version of JSON is available in @webcrypto-local/cards@1.6.6

It'll be added to Fortify@1.8.2

@microshine microshine mentioned this issue Jul 5, 2021
@donskov donskov mentioned this issue Jul 5, 2021
@defacto64
Copy link
Author

The updated card.json is okay, thank you Stephan.

@rmhrisk rmhrisk closed this as completed Jul 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants