How MIFARE Uses Cookies

[gpagliaroli]

The card is in SL1 or SL3?
If it is in SL1, the authentication to compatible sectors is the same as using Classic, using 14443-3.
Now if the card is in SL1, and it is required to authenticate to Sector 0x9003, it is first required to execute a RATS and then a FirstAuth (using 14443-4).

---

+ 0  |  - 0

[gpagliaroli]

Hi Diego,

My advice is that you check the Historicals Bytes in the ATS, after running the ActivateCard. They are unique for each type of card.

regards,
Germán.

---

+ 0  |  - 0

[gpagliaroli]

Hi Diego,

You can find the firmware on this link, http://cache.nxp.com/documents/software/239410.zip. (This is found in the link indicated in the download option.)

Regards,
Germán.

---

+ 0  |  - 0

[gpagliaroli]

If you have a mobile phone with nfc and the card in question, you can use the Tag Info NXP app, with which you can get information about the chip you have.

https://play.google.com/store/apps/details?id=com.nxp.taginfolite&hl=en

---

+ 0  |  - 0

[gpagliaroli]

In the case of 7 bytes of UID, the same are unique, so it would not be possible to find those you mention bytes 0x00 values.
Moreover, you can find in a public document NXP (MIFARE and handling of UIDs), answer to your query.

Regards,
Germán.

---

+ 0  |  - 0

[gpagliaroli]

I have not used QT, but searching the internet can find several examples.
A special feature is that AES is a highly optimized and fast to implement encryption and there are routines for such small microcontrollers as 8-bit algorithm.
I hope I have helped you.

---

+ 0  |  - 0

[gpagliaroli]

Hi,

Each block Mifare Classic 1KB, has 16 bytes long (128 bits), so that it is possible to use any method for convenience 128 bit encryption.

Among the most used you could do with 3DES or AES, but I would be inclined to use AES. These algorithms allow use as Data multiples of 16 bytes in length and the key should be 16 bytes in length.

You should only be used as Data encryption block of 16 bytes and should preferably use a key that is diversified by the uid and block number. This will see different cards in different data for the same message.

With this you could encrypt each block separately or a better option might be you encrypt the 3 blocks with AES, but in CBC mode where encryption is chained.

I hope to help you with what you request.

---

+ 0  |  - 0

[gpagliaroli]

Not understand the question correctly.
A What do you mean if all is done by the MFRC522 hanshake and delivers data (that data speak? Or commands referees to you?)
Please can you clarify a little more consultation so we can help you?

---

+ 0  |  - 0

[gpagliaroli]

Thank you very much for such a clear answer!
I used the APP TagInfo to verify whether or not support Mifare Classic, only when you have to look for phones that support is really difficult.

Germán.

---

+ 0  |  - 0

[Author]

Posts