Add CLI commands to dump and clone tag

[rickNmorty2]

Note: based on PR #199

Thanks to @taichunmin implementation of fchk, this PR adds the following commands:

• hf mf dump to dump the content of a tag from a dictionary of keys:

  
  [USB] chameleon --> hf mf dump -h
  --------------------------------------------------------------------------------
  hf mf dump

Mifare Classic dump tag

usage: hf mf dump [-h] [-t {bin,hex}] -f DUMP_FILE -d DIC

options: -h, --help show this help message and exit -t {bin,hex}, --dump-file-type {bin,hex} Dump file content type -f DUMP_FILE, --dump-file DUMP_FILE Dump file to write data from tag -d DIC, --dic DIC Read keys (to communicate with tag to dump) from .dic format file

---

Example:

[USB] chameleon --> hf mf dump --dic keys.dic -f dump.bin

* `hf mf clone` to clone the content of a dump to a tag:

[USB] chameleon --> hf mf clone -h

hf mf clone

Mifare Classic clone tag from dump

usage: hf mf clone [-h] [-t {bin,hex}] [-a CLONE_ACCESS] -f DUMP_FILE -d DIC

options: -h, --help show this help message and exit -t {bin,hex}, --dump-file-type {bin,hex} Dump file content type -a CLONE_ACCESS, --clone-access CLONE_ACCESS Write ACL from original dump too (/!\ could brick your tag) -f DUMP_FILE, --dump-file DUMP_FILE Dump file containing data to write on new tag -d DIC, --dic DIC Read keys (to communicate with tag to write) from .dic format file

---

Example:

[USB] chameleon --> hf mf clone -f dump.bin --dic keys.dic

Note that by default, the `clone` command does not copy the ACL to avoid bricking the tag, but it could be enforced with `--clone-access`.

[github-actions[bot]]

Built artifacts for commit 8a02d6f4f84b84ebc4a4605503b5c843045339e5

Firmware

• Ultra APP DFU Package
• Ultra binaries
• Lite APP DFU Package
• Lite binaries

Client

• Linux
• macOS
• Windows

[GameTec-live]

may i suggest the addition of another option, something like --plain, which then just exports in the good ol one key per line format?

[taichunmin]

I can add the export option to my PR. But I think the .key and .dic format is better then custom format. because proxmark3 doesn't support custom format.

[taichunmin]

I already add the export option in PR #199

I also change the option from -f, -b and --hex to --key and --dic.

[GameTec-live]

I can add the export option to my PR. But I think the .key and .dic format is better then custom format. because proxmark3 doesn't support custom format.

ah, oki... With that one key per line i did mean .dic btw...

[xianglin1998]

So this PR is finished?

[xianglin1998]

You are the author of the export feature idea, so you can add a item to CHANGELOG.md after this PR is closed.

[github-actions[bot]]

You are welcome to add an entry to the CHANGELOG.md as well

[rickNmorty2]

I merged main into this and fixed/changed a few things to comply with PR #199 by @taichunmin.

From my point of view, ready to [be more tested and] merge.

[taichunmin]

The dic file usually has comment lines. https://github.com/RfidResearchGroup/proxmark3/blob/master/client/dictionaries/mfc_default_keys.dic

Maybe you can use the code: https://github.com/RfidResearchGroup/ChameleonUltra/blob/main/software/script/chameleon_cli_unit.py#L922