Classic 1k (4byte uid) Authentication procedure.

[Stanislav Granovskiy]

Hello.

Sotty for my English first!

I'm stuck on Authentication procedure with my Classic 1k Card. I don't understand what i need to do after i resive a NT.

-> db9d
-> 010F [Reset]
-> B7 [Version]
010F113D2D302C002A8D2B3E148326701540 [Init]
-> 0952010C0D87 [Send REQA]
-> 8989 [Read REQA]
09930920010C0D80 [Anticol]
-> 8989898989 [Read UID]
09930970099009F6090B09C509A801030100 [Calculate CRC]
-> A2A1 [GET CRC]
09930970099009F6090B09C509A809CE096F010C0D80 [Select]
-> 898989 [Read SAK]
0960090009F5097B010C0D80 [Auth block 30]
-> 89898989 [Answer]
<- AF117C77

So, i have a NT = AF117C77, A Key = FF FF FF FF FF FF, UID = 90F60BC5
In datasheet no info, io found some details here
http://slideplayer.com/slide/2161165/8/images/20/Authentication+&+initialization.jpg
but i can't unders what to do.
Pls, HELP! 5 Dayes on this.. :(

---

+ 0  |  - 0

[TapLinx Support]

Hi Stanislav,

Can you please concretize your issue in more detail? Which reader do you use? PC/SC reader or a chip solution? Which driver is used?

The TapLinx team

---

+ 0  |  - 0

[Stanislav Granovskiy]

Thank you for your attention to the matter.
The problem is solved.
I did not immediately realize that crypto1 was a private protocol. :)

P.S. I use mfrс522 directly connected to UART via a self-made ttl to usb adapter based on ch340.
Thanks for the attention.

---

+ 0  |  - 0

[TapLinx Support]

Hi Stanislav,

Yes, Crypto 1 is a proprietary NXP cipher, but it is supported by all NXP reader ICs.

The TapLinx team

---

+ 0  |  - 0

[Author]

Posts