Research, development and trades concerning the powerful Proxmark3 device.
Remember; sharing is caring. Bring something back to the community.
"Learn the tools of the trade the hard way." +Fravia
Time changes and with it the technology
Proxmark3 @ discord
Users of this forum, please be aware that information stored on this site is not private.
Pages: 1
(deleted)
Last edited by samburner3 (2017-08-22 06:11:18)
have to use the hf mf wrbl commands, since the hf mf restore commands ignore the keys inside the dumpdata file and just put in F's.
hf mf restore command reads the keys inside the dumpkeys.bin file and writes them to the new card. No need to use hf mf wrbl commands to set the keys.
If you see FFFFFFFFFFFF keys in the new card this can have two reasons:
You are trying to read the keys with a rdbl command and access conditions don't allow to read the respective key (note: this is always true for Key A). This will display as "FFFFFFFFFFFF".
You had "FFFFFFFFFFFF" keys in the dumpkeys.bin file
(deleted)
Last edited by samburner3 (2017-08-22 06:10:59)
a) What keys are used to actually authenticate to write to the card?
hf mf restore uses key A = FFFFFFFFFFFF to write to the card
I know this error is due to access conditions.
Exactly. But this means that you don't write to a blank card. Access Conditions on blank cards allow writing the sector trailer with key A (transport configuration). Please note the capitalized "BLANK" in the help text of hf mf restore:
Restore MIFARE classic binary file to BLANK tag
(deleted)
Last edited by samburner3 (2017-08-22 06:10:42)