Open kranidiotis opened 5 years ago
@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 to do is to create a way to ignore it?
If it is what PKCS#11 library do you use with it?
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 even if it can be used for signing as its not uniquely identifiable. We need to do some testing once we get more info from @kranidiotis.
It is an ACR122 NFC Card reader that reads an IDPrime MD 3840
ATR: 3B 80 80 01 01
ATR: 3B 80 80 01 01
Possibly identified card (using /usr/share/pcsc/smartcard_list.txt): 3B 80 80 01 01 ISO 14443 Type B without historical bytes Electronic Passport Spanish passport (2012) Canadian Passport
Sat Apr 6 20:41:52 2019 Reader 0: ACS ACR122U 00 00
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:
{
"cards": [{
"atr": "3B80800101",
"name": "Gemalto IDPrime MD 3840",
"driver": "39b3d7a3662c4b48bb120d008dd18648"
}]
}
If you're on a Mac the steps to update the card mapping are:
In theory, if the above conditions are met the card should work.
If not please try the driver "993988460d8f49a2ac519a2935f11533".
The thing that gives me pause is that the ATR is a generic one. I would have expected the 3840 ATR to be either:
3B 8F 80 01 80 31 80 65 B0 85 03 00 EF 12 0F FE 82 90 00 72
3B 7F .. 00 00 80 31 80 65 B0 .. .. .. .. 12 0F FE 82 90 00
Based on https://github.com/LudovicRousseau/pcsc-tools/blob/master/smartcard_list.txt
Maybe this is because it's over the NFC interface? can you insert the card into a card reader slot also?
This was reported here also : https://github.com/PeculiarVentures/fortify/issues/155
Reader name: ACS ACR122U 00 00 ATR: 3B80800101
Smart card ATR parsing 3B80800101