RfidResearchGroup/proxmark3
1
1
Fork 0
mirror of https://github.com/RfidResearchGroup/proxmark3.git synced 2024-09-21 15:56:21 +08:00
Code Issues Packages Projects Releases Wiki Activity
proxmark3/tools/hitag2crack/crack3
History
iceman1001 022eacecdc format
2020-03-13 14:37:49 +01:00
..
.gitignore hitag2crack stuff from RFidlar repo 2020-01-16 11:11:14 +01:00
HardwareProfile.h style 2020-03-09 16:44:07 +01:00
hitagcrypto.c cppcheck func name 2020-03-13 14:14:30 +01:00
hitagcrypto.h style 2020-03-09 16:44:07 +01:00
ht2crack3.c format 2020-03-13 14:37:49 +01:00
ht2test.c style 2020-03-09 16:44:07 +01:00
Makefile hitag2crack stuff from RFidlar repo 2020-01-16 11:11:14 +01:00
readme.md hitag2crack stuff from RFidlar repo 2020-01-16 11:11:14 +01:00
rfidler.h style 2020-03-09 16:44:07 +01:00
util.h hitag2crack stuff from RFidlar repo 2020-01-16 11:11:14 +01:00
utilpart.c style 2020-03-09 16:44:07 +01: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 ht2test program to check them. It's otherwise massively pointless and a complete waste of space.

./ht2test NRARFILE KEY UID