github/RRG-Proxmark3
1
0
Fork 0
mirror of https://github.com/RfidResearchGroup/proxmark3.git synced 2024-12-03 18:50:19 -08:00
Code Issues Packages Projects Releases Wiki Activity
master
RRG-Proxmark3/tools/hitag2crack/crack3
History
iceman1001 482a6464a2 style. we use calloc
2024-01-07 20:47:07 +01:00
..
.gitignore Bring hitag2crack tools in main Makefiles 2020-05-23 13:33:32 +02:00
ht2crack3.c style. we use calloc 2024-01-07 20:47:07 +01:00
ht2crack3test.c Bring hitag2crack tools in main Makefiles 2020-05-23 13:33:32 +02:00
Makefile Bring hitag2crack tools in main Makefiles 2020-05-23 13:33:32 +02:00
README.md Bring hitag2crack tools in main Makefiles 2020-05-23 13:33:32 +02:00

README.md

ht2crack3

Build

make clean
make

Run

You'll need a file consisting of 136 (or more) nR aR pairs. These are the encrypted nonces and challenge response values. They should be in hex with one pair per line, e.g.: 0x12345678 0x9abcdef0

./ht2crack3 UID NRARFILE

UID is the UID of the tag that you used to gather the nR aR values. NRARFILE is the file containing the nR aR values.

Tests

If you happen to know the key and want to check that all your nR aR values are valid (for high-powered demonstrations only, really) then you can use the ht2crack3test program to check them. It's otherwise massively pointless and a complete waste of space.

./ht2crack3test NRARFILE KEY UID