AuthenticateEV2First with key 0x00

Zenoncode — Tue, 12 Jan 2021 14:47:25 GMT

Hi,

I'm trying to read and write to NTAG424 NFCs with a react native app.

There are no known libraries out there that can help me out, so I'm writing it from scratch in JavaScript. My question is related to one of the steps in the AuthenticateEV2First.

When creating the C-APDU in the Cmd.AuthenticatePart2, there are two zeroes padded at the end. This makes it a total of 76 digits long. Is there any reason why this is done? If so, is there anywhere where I can find more information about it?

I'm currently using "NTAG 424 DNA and NTAG 424 DNA TagTamper features and hints" as my sole source of information.

Thanks in advance

Zenon

Re: AuthenticateEV2First with key 0x00

Jonathan_Iglesias — Tue, 12 Jan 2021 20:29:13 GMT

Hi @Zenoncode

Hope you are doing great, first of all we have some libraries that might help you one is in C which is our NFC reader library, available in our webpage also we have out taplinx SDK https://www.mifare.net/es/productos/tools/taplinx/ please check it and might be good for you and your application.

for more explanation about how the commands are constructed please use always the datasheet 10.4.1

https://www.nxp.com/docs/en/data-sheet/NT4H2421Gx.pdf

in the datasheet it is explained each command, how is constructed and what are the possible answers to it, the features and hints document have examples of how to implement some commands or process so you can check an actual process with real values so you can replicate it and confirm your process gets the same answer.

Jonathan

topic Re: AuthenticateEV2First with key 0x00 in NFC

AuthenticateEV2First with key 0x00

Re: AuthenticateEV2First with key 0x00