Forum › MIFARE SDK › Problem authenticating against a new application to create a file (EV2 tag) › Reply To: Problem authenticating against a new application to create a file (EV2 tag)
Hello Diego,
Your approach looks good. The selection of AID=0 is only required, if you create a new application. After creation you select this application and authenticate with the default key (00…00) to card key #0. Now you create the file. If you set key permissions, e.g.: write key is key #1, you have to authenticate with key #1 before you can write.
The 2K3DES key is the default Master PICC key for a new card. I recommend to change it to an AES128 key and use always AES128 keys for files. So create an application always with the AES128 key type.
Here is a similar code snippet of what you want to do:
https://www.mifare.net/support/forum/topic/desfire-ev1-cannot-create-files-other-than-value-file/
Please scroll down for the example code.
The TapLinx team
Your approach looks good. The selection of AID=0 is only required, if you create a new application. After creation you select this application and authenticate with the default key (00…00) to card key #0. Now you create the file. If you set key permissions, e.g.: write key is key #1, you have to authenticate with key #1 before you can write.
The 2K3DES key is the default Master PICC key for a new card. I recommend to change it to an AES128 key and use always AES128 keys for files. So create an application always with the AES128 key type.
Here is a similar code snippet of what you want to do:
https://www.mifare.net/support/forum/topic/desfire-ev1-cannot-create-files-other-than-value-file/
Please scroll down for the example code.
The TapLinx team
+ 0
|
- 0