Forum › MIFARE SDK › DesfireFire Personalization, Authentication › Reply To: DesfireFire Personalization, Authentication
Hi,
1) I am not sure as to why it is not. I think you should change your DEFAULT MASTER KEY to something what you want, otherwise everyone who detects that you use DESFire will first try to authenticate with DEFAULT MASTER KEY, which means, that person can erase your card or even do other changes if you weren't carefull.
2) You determine the number of keys you have during application creation procedure in KeySettingsTwo --> check the JavaDoc you'll notice it. Once you create an application with 5 keys (for example) they are all 00's. Once you apply changeKey method, they will change to the keys you defined in KeyStore.
Hope it helps.
David
1) I am not sure as to why it is not. I think you should change your DEFAULT MASTER KEY to something what you want, otherwise everyone who detects that you use DESFire will first try to authenticate with DEFAULT MASTER KEY, which means, that person can erase your card or even do other changes if you weren't carefull.
2) You determine the number of keys you have during application creation procedure in KeySettingsTwo --> check the JavaDoc you'll notice it. Once you create an application with 5 keys (for example) they are all 00's. Once you apply changeKey method, they will change to the keys you defined in KeyStore.
Hope it helps.
David
+ 0
|
- 0