Closed iceman1001 closed 5 years ago
Ok MCT is a nice tool for mobile read/write card. I also want to support the MCT format.
@kgamecarter Great addition! Now I only need a MCT dump file to test/verify it with ( @ikarus23 ?)
Converting back and forward looks great. ...may add a refresh button, right-click, or after a convertion to update the file explorer...
whoops.. converting a Ultralight bin dump to EML or MCT .. will try to make a classic formatted....
ok. refresh after converting works now.
MCT is a tool only for classic , so just only classic format.
Eml convertion code is copied from https://github.com/iceman1001/ChameleonMini-rebootedGUI/blob/1a345a9ee73312745cc4908b50945ed7142cd455/ChameleonMiniGUI/UserControls/UcExplorer.cs#L301 Does Ultralight also have EML format? If so. I need a Ultralight EML sample.
:) the UL/NTAG dumps are more complex in one sense. I have bin for it, the json is not done yet... ...if you don't want to add json in pm3 client for hf mfu dump
ok it's 4 byte per line.
...the old dumps was 4byte, but then we added a block of special data in the beginning of the dump file
The special data does not seem to match EML format. needs a better format for mfu_dump_t
I know... hence the urge to get JSON for it :)
Alrighty then. hf mfu dump new json dump format in proxmark3 client.
If I download dump from ChameleonMini to JSON. I will miss special data?
as of this moment I don't think the Chameleon uses the special data. It really should though. Better look in the firmware repo. Or @bogiton , do you know ?
As of now, I think it can only load / convert JSON format. not save it.
How about we just set those special fields as empty?
The only extra thing we save are the counters for UL, right after the memory blocks. I had a check added for this in the DownloadAndSaveDump method.
But do we have access to Version, Signature etc?
Nope, just the memory block bytes. Signature is hard-coded I think.
The binary dump & json blocks only end of user memory? No include lock bytes and configurations page?
There are so many different variants of Ultralight / NTAG etc class tags so keeping track of each cards memory layout is hard. Not to mention locking mechanisms. The pm3 client dumps all blocks it can read.
if pm3 client can figure out default pwd/pack, it adds those for known tag formats. Not all formats.
The MCT tool has its own format, it would be nice if the GUI could support it aswell
https://github.com/ikarus23/MifareClassicTool/issues/217
@kgamecarter Maybe your magic touch?