Forum › MIFARE SDK › Set keys and do authentication to DESFire using MIFARE advanced SDK › Reply To: Set keys and do authentication to DESFire using MIFARE advanced SDK
Hi,
at first: the DESFire EV1 supports 128-bit AES. You should initialize the key with
You can use the key version if you want to change keys later and to ensure the correct key is used. At the begin of your application usually the key version is 0.
The master key is the key number 0. This key is set to default for a blank card. It is a good practice to let the master key for administrative purposes and define your own keys for your application. If you define for example key 1 and key 2, you can use this keys for the file access in your application. Set the read access to 1 (using key 1) and write access to 2 (using key 2) and the change access to F (not allowed to change). A key is set with the changeKey command. You should always change the default master key before you release the card.
Kind regards,
The MIFARE Team
at first: the DESFire EV1 supports 128-bit AES. You should initialize the key with
KEYSTORE_KEY_TYPE_AES128You can use the key version if you want to change keys later and to ensure the correct key is used. At the begin of your application usually the key version is 0.
The master key is the key number 0. This key is set to default for a blank card. It is a good practice to let the master key for administrative purposes and define your own keys for your application. If you define for example key 1 and key 2, you can use this keys for the file access in your application. Set the read access to 1 (using key 1) and write access to 2 (using key 2) and the change access to F (not allowed to change). A key is set with the changeKey command. You should always change the default master key before you release the card.
Kind regards,
The MIFARE Team
+ 0
|
- 1