Hello there.
How can I get rid of the following error?
─$ miLazyCracker
Found Mifare Classic Mini tag
ISO/IEC 14443A (106 kbps) target:
ATQA (SENS_RES): 00 04
* UID size: single
* bit frame anticollision supported
UID (NFCID1): fd a1 2b 74
SAK (SEL_RES): 09
* Not compliant with ISO/IEC 14443-4
* Not compliant with ISO/IEC 18092
Fingerprinting based on MIFARE type Identification Procedure:
* MIFARE Mini 0.3K
* SmartMX with MIFARE 1K emulation
Other possible matches based on ATQA & SAK values:
Try to authenticate to all sectors with default keys...
Symbols: '.' no key found, '/' A key found, '\' B key found, 'x' both keys found
[Key: ffffffffffff] -> [.....]
[Key: a0a1a2a3a4a5] -> [/....]
[Key: d3f7d3f7d3f7] -> [/....]
[Key: 000000000000] -> [/....]
[Key: b0b1b2b3b4b5] -> [/....]
[Key: 4d3a99c351dd] -> [/....]
[Key: 1a982c7e459a] -> [/....]
[Key: aabbccddeeff] -> [/....]
[Key: 714c5c886e97] -> [/....]
[Key: 587ee5f9350f] -> [/....]
[Key: a0478cc39091] -> [/....]
[Key: 533cb6c723f6] -> [/....]
[Key: 8fd0a4f256e9] -> [/....]
Sector 00 - Found Key A: a0a1a2a3a4a5 Unknown Key B
Sector 01 - Unknown Key A Unknown Key B
Sector 02 - Unknown Key A Unknown Key B
Sector 03 - Unknown Key A Unknown Key B
Sector 04 - Unknown Key A Unknown Key B
Using sector 00 as an exploit sector
Card is not vulnerable to nested attack
MFOC not possible, detected hardened Mifare Classic
Trying HardNested Attack...
libnfc_crypto1_crack a0a1a2a3a4a5 0 A 16 B mfc_fda12b74_foundKeys.txt
Found tag with uid fda12b74, collecting nonces for key B of block 16 (sector 4) using known key A a0a1a2a3a4a5 for block 0 (sector 0)
Collected 4762 nonces... leftover complexity 8600042471424 (~2^42.97) - press enter to start brute-force phase
Collected 4768 nonces... leftover complexity 8600042471424 (~2^42.97) - initializing brute-force phase...
Starting 4 threads to test 190577073196 states using 128-way bitslicing
Cracking... 100.00%
No solution found :(
MFOC not possible, detected hardened Mifare Classic
Trying HardNested Attack...
libnfc_crypto1_crack a0a1a2a3a4a5 0 A 16 B mfc_fda12b74_foundKeys.txt
Found tag with uid fda12b74, collecting nonces for key B of block 16 (sector 4) using known key A a0a1a2a3a4a5 for block 0 (sector 0)
Collected 4910 nonces... leftover complexity 294072679876 (~2^38.10) - initializing brute-force phase...
Starting 4 threads to test 294072679876 states using 128-way bitslicing
Cracking... 99.96%
No solution found :(
MFOC not possible, detected hardened Mifare Classic
Trying HardNested Attack...
libnfc_crypto1_crack a0a1a2a3a4a5 0 A 16 B mfc_fda12b74_foundKeys.txt
Found tag with uid fda12b74, collecting nonces for key B of block 16 (sector 4) using known key A a0a1a2a3a4a5 for block 0 (sector 0)
Collected 5132 nonces... leftover complexity 190577073196 (~2^37.47) - initializing brute-force phase...
Starting 4 threads to test 190577073196 states using 128-way bitslicing
Cracking... 99.97%
No solution found :(
MFOC not possible, detected hardened Mifare Classic
Trying HardNested Attack...
libnfc_crypto1_crack a0a1a2a3a4a5 0 A 16 B mfc_fda12b74_foundKeys.txt
Found tag with uid fda12b74, collecting nonces for key B of block 16 (sector 4) using known key A a0a1a2a3a4a5 for block 0 (sector 0)
Collected 4091 nonces... leftover complexity 8600042471424 (~2^42.97) - press enter to start brute-force phase
Collected 4097 nonces... leftover complexity 8600042471424 (~2^42.97) - initializing brute-force phase...
Starting 4 threads to test 8600042471424 states using 128-way bitslicing
**Cracking... 0.00%/usr/local/bin/miLazyCracker: line 127: 96558 Segmentation fault "${mycmd[@]}"**
MFOC not possible, detected hardened Mifare Classic
Trying HardNested Attack...
libnfc_crypto1_crack a0a1a2a3a4a5 0 A 16 B mfc_fda12b74_foundKeys.txt
Found tag with uid fda12b74, collecting nonces for key B of block 16 (sector 4) using known key A a0a1a2a3a4a5 for block 0 (sector 0)
Collected 4956 nonces... leftover complexity 190577073196 (~2^37.47) - initializing brute-force phase...
Starting 4 threads to test 190577073196 states using 128-way bitslicing
Cracking... 99.98%
No solution found :(
Hello there. How can I get rid of the following error?
Regards