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
You are not logged in.
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.
I was reading on the old Google code issues list and this one triggers some ideas.
As it is now, the "hf mf restore" uses the default key A 0xffffffffffff to write to the tag.
If the tag doesn't have this set then the restore command fails.
https://code.google.com/p/proxmark3/issues/detail?id=37
I don't know how many uses the this command anymore but a choice to use the default key or use the keys from the keydump instead might be useful.
UsbCommand c = {CMD_MIFARE_WRITEBL, {FirstBlockOfSector(sectorNo) + blockNo, keyType, 0}};
memcpy(c.d.asBytes, key, 6);
the suggested fix on the google code is another hardcoded solution, but I think an inparameter solution would be nicer.
PrintAndLog("Usage: hf mf restore [card memory]");
PrintAndLog(" [card memory]: 0 = 320 bytes (Mifare Mini), 1 = 1K (default), 2 = 2K, 4 = 4K");
|
PrintAndLog("Usage: hf mf restore [card memory] -u <A|B> <KEY>");
PrintAndLog(" [card memory] : 0 = 320 bytes (Mifare Mini), 1 = 1K (default), 2 = 2K, 4 = 4K");
PrintAndLog(" -u : use keys from dumpkeys.bin file when writing to tg");
PrintAndLog(" <A|B> <KEY> : use following keytype and key when writing to tag");
Offline
Hi,
this feature would be a huge improvement to the PM3.
Due lack of programming skills, I hope here is someone in the board who could do this....
Offline
One can wish, It's not a big change to implement this behavior on the client.
Offline