Add support for '3bd218008131fe58c90316' token

[gatzec]

Reader name: Gemalto USB Shell Token V2 (37AED46F) 00 00
ATR: 3BD218008131FE58C90316

{
   "cards": [{
   	"atr": "3BD218008131FE58C90316",
   	"name": "Token name",
   	"driver": "9997BC25EC2540D916AA47755629CD927C42013B"
   }],
   "drivers": [{
   	"id": "9997BC25EC2540D916AA47755629CD927C42013B",
   	"name": "Driver name",
   	"file": {
   		"windows": "path/to/pkcs11.dll",
   		"osx": "path/to/pkcs11.dylib"
   	}
   }]
}

Smart card ATR parsing 3BD218008131FE58C90316

[gatzec]

Any chance of adding support for this card?

[Kharya1337]

Thank you for reaching out and for your patience in waiting for a response. Apologies for the delay.

Based on the provided details, we’d like to gather additional information to better understand and address the issue with your smart card. Specifically, could you please clarify the following?

1. Who manufactures the card (e.g., Gemalto, Thales, etc.)?
2. What middleware is being used with the card (if any)?
3. What is the name and path of the PKCS#11 library included with that middleware?

With this information, we will do our best to identify the source of the issue and ensure compatibility with your card.

Thank you again for your cooperation!

[gatzec]

Hi,
I don't know if such answers will be satisfactory:

1. "Gemalto USB Shell Token V2 (37AED46F) 00 00"
2. Fortify / Setasign
3. Error: /usr/bin/opensc-pkcs11.so: cannot open shared object file: No such file or directory\n at PKCS11.load (/snapshot/fortify-app/node_modules/pkcs11js/index.js:275:11)\n at Module.load (/snapshot/fortify-app/node_modules/graphene-pk11/build/cjs/module.js:12:13)\n at new OpenSC (/snapshot/fortify-app/node_modules/@webcrypto-local/server/build/index.js:1859:50)\n at CardWatcher.getCardObject (/snapshot/fortify-app/node_modules/@webcrypto-local/server/build/index.js:2123:32)\n at PCSCWatcher.<anonymous> (/snapshot/fortify-app/node_modules/@webcrypto-local/server/build/index.js:2060:35)\n at PCSCWatcher.emit (node:events:513:28)\n at PCSCWatcher.emit (/snapshot/fortify-app/node_modules/@webcrypto-local/core/build/index.js:25:22)\n at PCSCWatcher.emit (/snapshot/fortify-app/node_modules/@webcrypto-local/server/build/index.js:2022:22)\n at Timeout._onTimeout (/snapshot/fortify-app/node_modules/@webcrypto-local/server/build/index.js:1981:38)\n at listOnTimeout (node:internal/timers:569:17)

[gatzec]

Regarding point 2, I also use setasign software.

[Kharya1337]

Thank you for providing additional details.

Based on the information you’ve shared, it seems the issue is related to the inability to locate the PKCS#11 library (/usr/bin/opensc-pkcs11.so). This typically occurs when the middleware library is either missing or incorrectly configured.

Steps to Troubleshoot:

1. Check PKCS#11 Library Path:
   Confirm that the library path /usr/bin/opensc-pkcs11.so exists. On some systems, the correct path might differ (e.g., /usr/lib/opensc-pkcs11.so). You can locate it with:

   find /usr -name opensc-pkcs11.so  

   Update the configuration to use the correct path if needed.

2. Test Middleware Functionality:
   Use the pkcs11-tool command-line utility to confirm the middleware is functional. Example:

   pkcs11-tool --module /path/to/opensc-pkcs11.so --list-slots  

Additional Questions:

To better assist you, could you please provide the following details?

• Fortify Version: Which version of Fortify are you using?
• Card Configuration: What version of the ~/.fortify/card.json file are you using?
• Logs File: Could you share the logs file for this issue? This will help us identify any additional context or specific errors.