Forum › MIFARE SDK › Cannot create DESFire EV1 aplication with AES key › Reply To: Cannot create DESFire EV1 aplication with AES key
Hi Taplink Support,
I have the same issue as Anmol. After changing the PICC key successful from default key (2K3DES) to custom key (AES), but it still shows DES key when checking by the TagInfo android app. However the custom key works fine when re-authentication. // The same code it does not work for Desfire EV1 but works for Desfire EV2.
byte keyNo = (byte) 0x80;
byte keyVersion = 0x00;
Thanks
I have the same issue as Anmol. After changing the PICC key successful from default key (2K3DES) to custom key (AES), but it still shows DES key when checking by the TagInfo android app. However the custom key works fine when re-authentication. // The same code it does not work for Desfire EV1 but works for Desfire EV2.
byte keyNo = (byte) 0x80;
byte keyVersion = 0x00;
Thanks
+ 0
|
- 0