Closed VortixDev closed 3 years ago
That is the process for hf mfdes createaid
. You need to authenticate first and the auth command turns on the field.
Most desfire commands needs a auth first. So this is by design.
Either we implement auth for each command, which means a messy command line,
or we split it up and might suffer from ppl who forget they have the field on.
Its not super well documented the way that we operated the DESFire on a Pm3. Feel free to make a note / blogpost about it.
I do mean that a note_on_desfire.md would be great.
Describe the bug The HF field is not being activated for transmission when running the
hf mfdes createaid
command, according to the warning (I can also replicate this withhf mfdes formatpicc
, and have not tested others):To Reproduce Run the example command for
hf mfdes createaid
(hf mfdes createaid -a 123456 -f 1111 -k 0E -l 2E --name Test
).Expected behavior The field should be activated prior to any attempt to transmit.
Additional information Using
hf 14a raw -sk 00
to activate the field before running thehf mfdes createaid
command leads to the command executing successfully. It should be noted that, although the field stays on after thehf 14a raw
command is run, the command will still fail with "No APDU response" if the card is withdrawn from the field beforehf mfdes createaid
is ran (even if brought back into the field before executing), albeit without the "HF field is off" warning. A successful run is shown below.Diagnostic information
OS: Kali Linux
hw version
hw status
data tune
(*) Q factor must be measured without tag on the antenna
[+] Displaying LF tuning graph. Divisor 88 (blue) is 134.83 kHz, 95 (red) is 125.00 kHz.