Ryan Hurst
Ryan Hurst
@FlorianKnibbe did you get this card working otherwise?
If possible we would like to verify it works and get it added. Do you have the path to the PKCS#11 library you use with this card?
@madanprabhud what PKCS#11 library do you use with this token? What path is that file found in?
If this is really an ePass2003 it might work with this addition to cards.json If so you can update cards.json with: ``` { "cards": [{ "atr": "3B9F958131FE9F006646530501001171DF000006000015", "name": "Feitian ePass2003",...
Fortify maps cards to the middleware/drivers from the card manufacturer to the card based on a ID that the card has. In this blob: ``` { "cards": [{ "atr": "3B9F958131FE9F006646530501001171DF000006000015",...
Each ATR gets mapped to a PKCS#11 library. In the original bug you will see something that looks similar to this: ``` { "cards": [{ "atr": "3B9F958131FE9F006646530501001171DF000006000015", "name": "Feitian ePass2003",...
@abrbhat There is a menu item that produces logs:  Can you get those logs and share them here?
Strange, it seems that version of opensc at least does’t like that version of that card. Are you using this card with other middleware? For example via a CSP?
It seems to me that since your on Windows the token should have worked in Fortify with just the CSP there. Was the CSP not installed before?
And if you reverted the card.jaon, removes the opensc install and had the updated CSP Fortify worked?