Skip to content
This repository has been archived by the owner on Sep 3, 2024. It is now read-only.

ATR Not Recognized Safenet 5300 Tokens #565

Open
PeterGS123 opened this issue Jan 4, 2024 · 3 comments
Open

ATR Not Recognized Safenet 5300 Tokens #565

PeterGS123 opened this issue Jan 4, 2024 · 3 comments

Comments

@PeterGS123
Copy link

Safenet now offers USB-C tokens which are currently not fully recognized by Fortify. I can see the token in the software but it shows as "read only" mode. The device shows as "SCard Windows API."

I have seen this before and it usually means that Fortify does not recognize the ATR for this device. Could you please look into this and add the ATR to the SCard.json like you have done in the past?

In the fortify logs I see the following information:
CryptoAPI","level":"info","message":"certStorage/exportCert","source":"server-api","timestamp":"2024-01-04T16:34:04.608Z"}
{"atr":"3bff9600008131fe4380318065b0846160fb120ffd8290000c","level":"info","message":"cardReader/insert","reader":"SafeNet eToken 5300 C 0","source":"server-api","timestamp":"2024-01-04T16:34:04.613Z"}

image

@PeterGS123
Copy link
Author

as a test I updated my local card.json file with the following information and now the token is working on my fortify:

   {
  "atr": "3bff9600008131fe4380318065b0846160fb120ffd8290000c",
  "name": "SafeNet eToken 5300",
  "driver": "39b3d7a3662c4b48bb120d008dd18648"
},

@microshine
Copy link
Collaborator

I've updated the card.json file. @webcrypto-local/[email protected] includes SafeNet eToken 5300 token. @donskov please publish the card.json file for Fortify app.

@donskov
Copy link
Collaborator

donskov commented Jan 8, 2024

@microshine The file is updated and should be available by fetching. A version of the application has not changed.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants