Describe the bug
When I run 'hf mf auto' on a Mifare Magic Card UID, it did not exist correctly.
When run on a real mifare classic, it worked as expected.
To Reproduce
Steps to reproduce the behavior:
Place UID Majic Card on proxmark
run "hf mf auto"
Expected behavior
Regardless of if the card can support a test or not, exit cleanly.
sample output
[usb] pm3 --> hf mf auto
[!] no known key was supplied, key recovery might fail
[+] loaded 23 keys from hardcoded default array
[=] running strategy 1
[=] Chunk: 0.9s | found 30/32 keys (23)
[=] running strategy 2
[=] Chunk: 0.9s | found 30/32 keys (23)
[+] target sector: 0 key type: A -- found valid key [FF FF FF FF FF FF ] (used for nested / hardnested attack)
[+] target sector: 0 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 2 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 2 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 3 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 3 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 4 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 4 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 5 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 5 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 6 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 6 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 7 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 7 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 8 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 8 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 9 key type: A -- found valid key [00 00 00 00 00 00 ]
[+] target sector: 9 key type: B -- found valid key [00 00 00 00 00 00 ]
[+] target sector: 10 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 10 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 11 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 11 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 12 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 12 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 13 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 13 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 14 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 14 key type: B -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 15 key type: A -- found valid key [FF FF FF FF FF FF ]
[+] target sector: 15 key type: B -- found valid key [FF FF FF FF FF FF ]
[-] Nested attack failed, trying again (1/10)
[!] Button pressed. Aborted.
[usb] pm3 -->
Notes:
All keys Except Sector "1" where found.
Button was not pressed.
LEDs A,C and D left on. - Pressing button does clear the LEDs back to all off.
Desktop (please complete the following information):
OS: Windows
inside proxmark3 client run the following commands and paste the output here.
hw version
[usb] pm3 --> hw version
[ Proxmark3 RFID instrument ]
[ CLIENT ]
client: RRG/Iceman/psk-test/v4.9237-861-g20d55ec9-dirt...-unclean 2020-08-31 18:19:40
compiled with MinGW-w64 8.2.0 OS:Windows (64b) ARCH:x86_64
[ PROXMARK3 RDV4 ]
external flash: present
smartcard reader: present
[ PROXMARK3 RDV4 Extras ]
FPC USART for BT add-on support: absent
[ ARM ]
bootrom: RRG/Iceman/master/c49bfa08 2020-05-06 17:25:38
os: RRG/Iceman/psk-test/v4.9237-861-g20d55ec9-dirt...-unclean 2020-08-30 19:40:13
compiled with GCC 7.3.1 20180622 (release) [ARM/embedded-7-branch revision 261907]
[ FPGA ]
LF image built for 2s30vq100 on 2020-07-08 at 23: 8: 7
HF image built for 2s30vq100 on 2020-07-08 at 23: 8:19
HF FeliCa image built for 2s30vq100 on 2020-07-08 at 23: 8:30
[ Hardware ]
--= uC: AT91SAM7S512 Rev A
--= Embedded Processor: ARM7TDMI
--= Nonvolatile Program Memory Size: 512K bytes, Used: 288552 bytes (55%) Free: 235736 bytes (45%)
--= Second Nonvolatile Program Memory Size: None
--= Internal SRAM Size: 64K bytes
--= Architecture Identifier: AT91SAM7Sxx Series
--= Nonvolatile Program Memory Type: Embedded Flash Memory
Describe the bug When I run 'hf mf auto' on a Mifare Magic Card UID, it did not exist correctly. When run on a real mifare classic, it worked as expected.
To Reproduce Steps to reproduce the behavior:
Expected behavior Regardless of if the card can support a test or not, exit cleanly.
sample output
Notes: All keys Except Sector "1" where found. Button was not pressed. LEDs A,C and D left on. - Pressing button does clear the LEDs back to all off.
Desktop (please complete the following information):
hw version
[+] Displaying LF tuning graph. Divisor 88 is 134.83 kHz, 95 is 125.00 kHz.