[Hamdy BS]

hi dear,
Thank you, we think you've some trouble in your emailing service, we're not able to send you emails, see the attached screenshot:

---

+ 0  |  - 0

[Hamdy BS]

Hello,
Thank you, a clear answer.
We will be thankful if you could provide any links to the library or the SDK of the UCODE DNA which allow the authentication, read, write operations.

---

+ 0  |  - 0

[Hamdy BS]

Perfect, thank you!

---

+ 0  |  - 0

[Hamdy BS]

Hello,
No sir, we mean the UHF one, UCODE DNA, the one with the 10 meters range.

---

+ 0  |  - 0

[Hamdy BS]

UCODE NDA UCODE DNA

---

+ 0  |  - 0

[Hamdy BS]

Hi support Team,
Exactly as you mentioned,

the call back works, but the card detection do not. The Ultralight C is an unknown card type

, you are right.

Regards

---

+ 0  |  - 0

[Hamdy BS]

Thank you dear,

Recently we got access to the docstore so we were able to read more about DESFire EV1 and DESFire EV2, and we were able to better interpret the issue with the method ".setAuthenticationRequiredForFileManagement(boolean authenticationRequiredForFileManagement)" of the class "EV2ApplicationKeySettings.Builder", which is the main cause of the trouble, so with the same following code:

desFireEV2.selectApplication(0);

desFireEV2.authenticateEV2First(0, PiccMasterKey, new byte[]{0, 0, 0, 0, 0, 0});

desFireEV2.format();



EV2ApplicationKeySettings.Builder appsetbuilderEV2 = new EV2ApplicationKeySettings.Builder();

EV2ApplicationKeySettings appSettings = appsetbuilderEV2

        .setAppKeySettingsChangeable(true)

        .setAppMasterKeyChangeable(true)

        .setAuthenticationRequiredForFileManagement(true) 

        .setAuthenticationRequiredForDirectoryConfigurationData(true)

        .setMaxNumberOfApplicationKeys(3)

        .setActiveKeySetVersion(0)

        .setKeyTypeOfApplicationKeys(KeyType.AES128)

        .build();



desFireEV2.createApplication(appId01, appSettings);

desFireEV2.selectApplication(appId01);

desFireEV2.authenticateEV2First(0, PiccMasterKey(), new byte[]{0, 0, 0, 0, 0, 0});



desFireEV2.ev2ChangeKey(0, 1, KeyType.AES128, PiccMasterKey, ReadKey, (byte) 0x0);

desFireEV2.ev2ChangeKey(0, 2, KeyType.AES128, PiccMasterKey, WriteKey, (byte) 0x0);



desFireEV2.createFile(fileNo, new DESFireFile.StdDataFileSettings(

        IDESFireEV1.CommunicationType.Enciphered, (byte) 0x1, (byte) 0x2, (byte) 0xf, (byte) 0xf, fileSize));



desFireEV2.selectApplication(appId01);



desFireEV2.authenticateEV2First(2, WriteKey, new byte[]{0, 0, 0, 0, 0, 0});

desFireEV2.writeData(fileNo, 0, "https://www.alpha-lab.com.tn".getBytes());

Will throw the following exception at the last line, at the ".writeData() method":

com.nxp.nfclib.exceptions.InvalidResponseLengthException: Authentication Error

So creating an app with setting its "AuthenticationRequiredForFileManagement" to true, ".setAuthenticationRequiredForFileManagement(true)", then creating a file with setting its read and write key to a specific key, will make the file inaccessible for read and write with rising the Authentication Error exception.

Now, does using the methods "authenticateEV2First()" and "authenticateEV2NonFirst()" will solve this issue or not, the development team can test it once they will resolve the first issue.

Note: we tried the same code without changing the keys but we got the same exception.
Note: We reported the two issues in the same topic because they are related to each other, so maybe the development team can debug and resolve them at the same release.

Best Regards

---

+ 0  |  - 0

[Hamdy BS]

Hi support team,
Thank you for your prompt reply,
We updated the gradle file as follow:

compile ('taplinx-android:nxpnfcandroidlib:1.3@aar'){ transitive = true }

Then we made a clean build, we uninstalled and reinstalled the app, but unfortunately the exception remain.

Regards

---

+ 0  |  - 0

[Hamdy BS]

QUESTION UPDATE:
The method we are talking about is ".setAuthenticationRequiredForDirectoryConfigurationData(true/false)" and it is not ".setAuthenticationRequiredForApplicationManagement()".
We are not able to edit the question above, so sorry for the mistake and please consider this correction.

Regards

---

+ 0  |  - 0

[Hamdy BS]

Sorry, since i cannot update my answer, i will correct it here, i meant:
While inverting the order, setting AUTH1 after AUTH0 has erased the AUTH0 configuration for me.

---

+ 0  |  - 0

[Hamdy BS]

I think i figured it out,
The order of execution is important,
AUTH1 must be setted first:

The correct order that worked for me:
-ultralightC.configurationMemoryAccess(0, (byte)1); //AUTH1
-ultralightC.configurationMemoryAccess(8, (byte)0); //AUTH0

While inverting the order, setting AUTH0 after AUTH1 has erased the AUTH1 configuration for me.

---

+ 0  |  - 0

[Author]

Posts