Open maxben14 opened 6 years ago
Correct. Parity errors are only displayed in hf list
(and you should ignore them for encrypted data). Tag answers are not checked for parity errors.
close?
Let's keep this as a reminder (like #12).
yes. as for me - I dont want to make proxmark a "standard reader" (i made some of them) Its just reader with big "field of look" and development tool and as for me dont need to check all the conditions.
... and as a development tool I would expect that it is able to analyze incoming data for parity errors. There should always be an option to ignore it though.
agree with @pwpiwi
I'm developing a classic 1k emulator. I'm writing the firmware for atmega and testing the results on the proxmark. The Proxmark does not check the parity bits in the card responses during the block read operation.
Example read block: hf mf rdbl 0 a a0a1a2a3a4a5 --block no:0, key type:A, key:a0 a1 a2 a3 a4 a5
db# READ BLOCK FINISHED
isOk:01 data:dc cf ee 01 fc 08 04 00 62 63 64 65 66 67 68 69
I try from my emulator on comand read block send encrypt answer 16 bytes and crc 2 bytes with parity random bits and proxmark don't show me error parity bits.