vk496 / mfoc Goto Github PK

View Code? Open in Web Editor NEW

This project forked from nfc-tools/mfoc

86.0 9.0 32.0 1.53 MB

Mifare Classic Offline Cracker with Hardnested support

License: GNU General Public License v2.0

Makefile 0.04% M4 0.24% C 99.70% Roff 0.02%

mfoc's People

Contributors

Stargazers

Watchers

mfoc's Issues

AC_MSG_ERROR([libnfc >= $LIBNFC_REQUIRED_VERSION is mandatory

Hi, I have this problem, can you please help me?

root@kaliEvo:~/cartellona/mfoc# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... /usr/bin/mkdir -p
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether make supports nested variables... yes
checking for gcc... gcc
checking whether the C compiler works... yes
checking for C compiler default output file name... a.out
checking for suffix of executables... 
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ISO C89... none needed
checking whether gcc understands -c and -o together... yes
checking whether make supports the include directive... yes (GNU style)
checking dependency style of gcc... gcc3
checking whether make supports nested variables... (cached) yes
./configure: line 3930: syntax error near unexpected token `libnfc,'
./configure: line 3930: `PKG_CHECK_MODULES(libnfc, libnfc >= $LIBNFC_REQUIRED_VERSION, , AC_MSG_ERROR([libnfc >= $LIBNFC_REQUIRED_VERSION is mandatory.]))'

Missing no-intel support

$ make
make  all-recursive
make[1]: Entering directory '/home/rock64/mfoc'
Making all in src
make[2]: Entering directory '/home/rock64/mfoc/src'
  CC       crapto1.o
  CC       crypto1.o
  CC       mfoc.o
  CC       mifare.o
  CC       nfc-utils.o
  CC       parity.o
  CC       hardnested/hardnested_bruteforce.o
  CC       hardnested/tables.o
  CC       cmdhfmfhard.o
  CC       util.o
  CC       util_posix.o
  CC       ui.o
gcc  -O3 -std=c99 -mno-mmx -mno-sse2 -mno-avx -mno-avx2 -mno-avx512f -c -o hardnested/hardnested_bf_core_NOSIMD.o hardnested/hardnested_bf_core.c
gcc: error: unrecognized command line option '-mno-mmx'
gcc: error: unrecognized command line option '-mno-sse2'; did you mean '-fno-dse'?
gcc: error: unrecognized command line option '-mno-avx'; did you mean '-Wno-a,'?
gcc: error: unrecognized command line option '-mno-avx2'; did you mean '-Wno-a,'?
gcc: error: unrecognized command line option '-mno-avx512f'
Makefile:719: recipe for target 'hardnested/hardnested_bf_core_NOSIMD.o' failed
make[2]: *** [hardnested/hardnested_bf_core_NOSIMD.o] Error 1
make[2]: Leaving directory '/home/rock64/mfoc/src'
Makefile:375: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/home/rock64/mfoc'
Makefile:316: recipe for target 'all' failed
make: *** [all] Error 2

I need to improve the Makefile.am to avoid using intel flags on no-Intel machines.

In proxmark3 works very well (https://github.com/Proxmark/proxmark3/blob/master/client/Makefile#L202), but I have issues when translating to automake format

Speed up cracking of hardened card by checking for key reuse

Hi,

would it be possible to check the recovered key against all (uncracked) sectors after running a hardnested attack?
This would speed up the recovery in case of key-reuse.

Best regards,

Earthnuker

Last Block Zeroing Access Conditions in Dump File

When using the hardnested branch with a 1K mifare card, it successfully finds the keys, but the saved dump has zeroed the last block's access conditions. When copying the dump to a blank card, it results in zeroing the access conditions on the new card, making the last block of the card unrecoverable.

Command used:
mfoc -O file.dmp

Last two blocks of the file.dmp:
0000:0380 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000:0390 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000:03A0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000:03B0 | 2A 2C 13 CC 24 2A FF 07 80 69 FF FF FF FF FF FF | *,.Ì$*ÿ..iÿÿÿÿÿÿ
0000:03C0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000:03D0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000:03E0 | 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 | ................
0000:03F0 | 2A 2C 13 CC 24 2A 00 00 00 00 FF FF FF FF FF FF | ,.Ì$....ÿÿÿÿÿÿ

Expected last line:
0000:03F0 | 2A 2C 13 CC 24 2A FF 07 80 69 FF FF FF FF FF FF | *,.Ì$*ÿ..iÿÿÿÿÿÿ

As you can see the access conditions (FF 07 80 69) are zero'd out.

This has happened on multiple source cards

run with "Error while requesting plain tag-nonce"

ENV:
ubuntu 18.04 64bit
Reader : Bus 001 Device 005: ID 072f:2200 Advanced Card Systems, Ltd ACR122U

errors:

lee@lee-Inspiron-7577 ~/nfc/mfoc-hardnested/src $ ./mfoc  -O t1.dump
Found Mifare Classic 1k tag
ISO/IEC 14443A (106 kbps) target:
    ATQA (SENS_RES): 00  04  
* UID size: single
* bit frame anticollision supported
       UID (NFCID1): 23  29  82  e1  
      SAK (SEL_RES): 08  
* Not compliant with ISO/IEC 14443-4
* Not compliant with ISO/IEC 18092

Fingerprinting based on MIFARE type Identification Procedure:
* MIFARE Classic 1K
* MIFARE Plus (4 Byte UID or 4 Byte RID) 2K, Security level 1
* 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] -> [xxxxxxxxx.xxxxxx]
[Key: a0a1a2a3a4a5] -> [xxxxxxxxx.xxxxxx]
[Key: d3f7d3f7d3f7] -> [xxxxxxxxx.xxxxxx]
[Key: 000000000000] -> [xxxxxxxxx.xxxxxx]
[Key: b0b1b2b3b4b5] -> [xxxxxxxxx.xxxxxx]
[Key: 4d3a99c351dd] -> [xxxxxxxxx.xxxxxx]
[Key: 1a982c7e459a] -> [xxxxxxxxx.xxxxxx]
[Key: aabbccddeeff] -> [xxxxxxxxx.xxxxxx]
[Key: 714c5c886e97] -> [xxxxxxxxx.xxxxxx]
[Key: 587ee5f9350f] -> [xxxxxxxxx.xxxxxx]
[Key: a0478cc39091] -> [xxxxxxxxx.xxxxxx]
[Key: 533cb6c723f6] -> [xxxxxxxxx.xxxxxx]
[Key: 8fd0a4f256e9] -> [xxxxxxxxx.xxxxxx]

Sector 00 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 01 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 02 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 03 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 04 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 05 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 06 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 07 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 08 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 09 - Unknown Key A               Unknown Key B
Sector 10 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 11 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 12 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 13 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 14 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 15 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff


Using sector 00 as an exploit sector
Card is not vulnerable to nested attack

Using AVX2 SIMD core.          


          
 time    | trg | #nonces | Activity                                                | expected to brute force          
         |     |         |                                                         | #states         | time           
-------------------------------------------------------------------------------------------------------------          
       0 |  0? |       0 | Start using 8 threads and AVX2 SIMD core                |                 |          
       0 |  0? |       0 | Brute force benchmark: 1091 million (2^30.0) keys/s     | 140737488355328 |   36h          
       0 |  0? |       0 | Using 235 precalculated bitflip state tables            | 140737488355328 |   36h          
      18 |  9A |     497 | Apply bit flip properties                               |    257337589760 |  4min          Error while requesting plain tag-nonce
lee@lee-Inspiron-7577 ~/nfc/mfoc-hardnested/src $

Compilation issues on ARM architecture?

Hello, I am new to GitHub, with close to no experience in coding, so please excuse me if this message is irrelevant.

Thank you for putting this fork together! It is extremely convenient (automated keys recovery and full dump), as MFOC would perform, only with the added benefit of the hardnested attack.

I could verify that the implementation of the attack is much quicker with this fork thant with say miLazyCracker. Similar speeds as with the ProxMark3 device, actually.

I am facing an issue where the Proxmark hardnested attack requires more memory than a Rapsberry Pi 3 can allocate. miLazyCracker works fine though.

I would like to speed things up a bit by using this fork of MFOC, but I am unable to get it to compile either on the latest and updated Raspbian (Debian) 32 bits or Kali Linux 64 bits for ARM architecture.

I am getting the same error when running the ./configure command.

I am using the following commands:

sudo apt-get update
sudo apt-get install git binutils make csh g++ sed gawk autoconf automake autotools-dev libglib2.0-dev libnfc-dev liblzma-dev libnfc-bin

git clone https://github.com/vk496/mfoc
cd mfoc
git checkout hardnested

autoreconf -is
./configure
make

I am getting warnings running autoreconf -is

and this is the output when running ./configure

Then the ouptut of make

So, mfoc is not even generated due to the aforementionned compilation errors.
It does compile fine in Debian or Kali for x64 (amd64),and works fine !

Any idea regarding the issue and how to sort it out? Anything I can investigate?
I am a beginner, sorry if my post is irrelevant, please let me know!
Thanks again,
Eric.

Error with -f parameter

Repo: https://github.com/vk496/mfoc/tree/hardnested

Cli:
$ ./mfoc -f ./default_keys -P 500 -O card.dmp
Cannot open keyfile: (null), exiting

In original repo (master from https://github.com/nfc-tools/mfoc) the -f param works

Key-reuse check algorithm re-adds keys for each sector

The code to check new keys adds any working keys to the list of keys to try, even if they are already in the list.
The problem is the code adds to the known keys buffer for each sector that has a valid key, so it will just keep adding more copies for the same key used in multiple sectors, leading to an explosion of candidate keys to try.
https://github.com/vk496/mfoc/blob/hardnested/src/mfoc.c#L371

Leading to output like this:

[Key: 000000000000] -> [xxxxxxxxxxxxxxxxxxxxxx/................x]
[Key: 000000000000] -> [xxxxxxxxxxxxxxxxxxxxxx/................x]
[Key: 000000000000] -> [xxxxxxxxxxxxxxxxxxxxxx/................x]
[Key: 000000000000] -> [xxxxxxxxxxxxxxxxxxxxxx/................x]
[Key: 000000000000] -> [xxxxxxxxxxxxxxxxxxxxxx/................x]
[Key: 000000000000] -> [xxxxxxxxxxxxxxxxxxxxxx/................x]
[Key: 000000000000] -> [xxxxxxxxxxxxxxxxxxxxxx/................x]
[Key: 000000000000] -> [xxxxxxxxxxxxxxxxxxxxxx/................x]

In my experience the code then actually hangs at some point, I didn't exactly narrow down why yet.

`make` fails with `ld` error

Here is the error I stumble.

kali@kali:~/rfid/mfoc$ make
make  all-recursive
make[1]: Entering directory '/home/kali/rfid/mfoc'
Making all in src
make[2]: Entering directory '/home/kali/rfid/mfoc/src'
  CC       crapto1.o
  CC       crypto1.o
  CC       mfoc.o
  CC       mifare.o
  CC       nfc-utils.o
  CC       parity.o
  CC       hardnested/hardnested_bruteforce.o
  CC       hardnested/tables.o
  CC       cmdhfmfhard.o
  CC       util.o
  CC       util_posix.o
  CC       ui.o
gcc  -O3 -std=c99 -mno-mmx -mno-sse2 -mno-avx -mno-avx2 -mno-avx512f -c -o hardnested/hardnested_bf_core_NOSIMD.o hardnested/hardnested_bf_core.c
gcc  -O3 -std=c99 -mno-mmx -mno-sse2 -mno-avx -mno-avx2 -mno-avx512f -c -o hardnested/hardnested_bitarray_core_NOSIMD.o hardnested/hardnested_bitarray_core.c
gcc  -O3 -std=c99 -mmmx -mno-sse2 -mno-avx -mno-avx2 -mno-avx512f -c -o hardnested/hardnested_bf_core_MMX.o hardnested/hardnested_bf_core.c
gcc  -O3 -std=c99 -mmmx -msse2 -mno-avx -mno-avx2 -mno-avx512f -c -o hardnested/hardnested_bf_core_SSE2.o hardnested/hardnested_bf_core.c
gcc  -O3 -std=c99 -mmmx -msse2 -mavx -mno-avx2 -mno-avx512f -c -o hardnested/hardnested_bf_core_AVX.o hardnested/hardnested_bf_core.c
gcc  -O3 -std=c99 -mmmx -msse2 -mavx -mavx2 -mno-avx512f -c -o hardnested/hardnested_bf_core_AVX2.o hardnested/hardnested_bf_core.c
gcc  -O3 -std=c99 -mmmx -msse2 -mavx -mavx2 -mavx512f -c -o hardnested/hardnested_bf_core_AVX512.o hardnested/hardnested_bf_core.c
gcc  -O3 -std=c99 -mmmx -mno-sse2 -mno-avx -mno-avx2 -mno-avx512f -c -o hardnested/hardnested_bitarray_core_MMX.o hardnested/hardnested_bitarray_core.c
gcc  -O3 -std=c99 -mmmx -msse2 -mno-avx -mno-avx2 -mno-avx512f -c -o hardnested/hardnested_bitarray_core_SSE2.o hardnested/hardnested_bitarray_core.c
gcc  -O3 -std=c99 -mmmx -msse2 -mavx -mno-avx2 -mno-avx512f -c -o hardnested/hardnested_bitarray_core_AVX.o hardnested/hardnested_bitarray_core.c
gcc  -O3 -std=c99 -mmmx -msse2 -mavx -mavx2 -mno-avx512f -c -o hardnested/hardnested_bitarray_core_AVX2.o hardnested/hardnested_bitarray_core.c
gcc  -O3 -std=c99 -mmmx -msse2 -mavx -mavx2 -mavx512f -c -o hardnested/hardnested_bitarray_core_AVX512.o hardnested/hardnested_bitarray_core.c
  CCLD     mfoc
/usr/bin/ld: hardnested/hardnested_bruteforce.o:(.bss+0x20): multiple definition of `t'; mfoc.o:(.bss+0x40): first defined here
/usr/bin/ld: hardnested/hardnested_bruteforce.o:(.bss+0x0): multiple definition of `r'; mfoc.o:(.bss+0x20): first defined here
/usr/bin/ld: hardnested/tables.o:(.bss+0x0): multiple definition of `r'; mfoc.o:(.bss+0x20): first defined here
/usr/bin/ld: hardnested/tables.o:(.bss+0x20): multiple definition of `t'; mfoc.o:(.bss+0x40): first defined here
/usr/bin/ld: cmdhfmfhard.o:(.bss+0x120): multiple definition of `t'; mfoc.o:(.bss+0x40): first defined here
/usr/bin/ld: cmdhfmfhard.o:(.bss+0x100): multiple definition of `r'; mfoc.o:(.bss+0x20): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_NOSIMD.o:(.bss+0x0): multiple definition of `r'; mfoc.o:(.bss+0x20): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_NOSIMD.o:(.bss+0x20): multiple definition of `t'; mfoc.o:(.bss+0x40): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_MMX.o:(.bss+0x0): multiple definition of `r'; mfoc.o:(.bss+0x20): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_MMX.o:(.bss+0x20): multiple definition of `t'; mfoc.o:(.bss+0x40): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_SSE2.o:(.bss+0x0): multiple definition of `r'; mfoc.o:(.bss+0x20): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_SSE2.o:(.bss+0x20): multiple definition of `t'; mfoc.o:(.bss+0x40): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_AVX.o:(.bss+0x0): multiple definition of `r'; mfoc.o:(.bss+0x20): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_AVX.o:(.bss+0x20): multiple definition of `t'; mfoc.o:(.bss+0x40): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_AVX2.o:(.bss+0x0): multiple definition of `r'; mfoc.o:(.bss+0x20): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_AVX2.o:(.bss+0x20): multiple definition of `t'; mfoc.o:(.bss+0x40): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_AVX512.o:(.bss+0x0): multiple definition of `r'; mfoc.o:(.bss+0x20): first defined here
/usr/bin/ld: hardnested/hardnested_bf_core_AVX512.o:(.bss+0x20): multiple definition of `t'; mfoc.o:(.bss+0x40): first defined here
collect2: error: ld returned 1 exit status
make[2]: *** [Makefile:436: mfoc] Error 1
make[2]: Leaving directory '/home/kali/rfid/mfoc/src'
make[1]: *** [Makefile:376: all-recursive] Error 1
make[1]: Leaving directory '/home/kali/rfid/mfoc'
make: *** [Makefile:317: all] Error 2

The output of lsb_release -a

kali@kali:~/rfid/mfoc$ lsb_release -a
No LSB modules are available.
Distributor ID: Kali
Description:    Kali GNU/Linux Rolling
Release:        2020.3
Codename:       kali-rolling

The output of autoreconf --version

kali@kali:~/rfid/mfoc$ autoreconf --version
autoreconf (GNU Autoconf) 2.69
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+/Autoconf: GNU GPL version 3 or later
<http://gnu.org/licenses/gpl.html>, <http://gnu.org/licenses/exceptions.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by David J. MacKenzie and Akim Demaille.

Hardnested attack (mfoc) not workin/exiting

Dear community,

an actual installation works not well with a mifare classic card:

Found Mifare Classic 4k tag
ISO/IEC 14443A (106 kbps) target:
    ATQA (SENS_RES): 00  02  
* UID size: single
* bit frame anticollision supported
       UID (NFCID1): **  **  **  **  
      SAK (SEL_RES): 18  
* Not compliant with ISO/IEC 14443-4
* Not compliant with ISO/IEC 18092

Fingerprinting based on MIFARE type Identification Procedure:
* MIFARE Classic 4K
* MIFARE Plus (4 Byte UID or 4 Byte RID) 4K, Security level 1
* SmartMX with MIFARE 4K 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] -> [.x..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: ffffffffffff] -> [.x..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: a0a1a2a3a4a5] -> [/x..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: d3f7d3f7d3f7] -> [/x..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: 000000000000] -> [/x..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: b0b1b2b3b4b5] -> [xx..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: 4d3a99c351dd] -> [xx..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: 1a982c7e459a] -> [xx..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: aabbccddeeff] -> [xx..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: 714c5c886e97] -> [xx..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: 587ee5f9350f] -> [xx..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: a0478cc39091] -> [xx..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: 533cb6c723f6] -> [xx..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]
[Key: 8fd0a4f256e9] -> [xx..xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.....]

Sector 00 - Found   Key A: a0a1a2a3a4a5 Found   Key B: b0b1b2b3b4b5
Sector 01 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 02 - Unknown Key A               Unknown Key B
Sector 03 - Unknown Key A               Unknown Key B
Sector 04 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 05 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 06 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 07 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 08 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 09 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 10 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 11 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 12 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 13 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 14 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 15 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 16 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 17 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 18 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 19 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 20 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 21 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 22 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 23 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 24 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 25 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 26 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 27 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 28 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 29 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 30 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 31 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 32 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 33 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 34 - Found   Key A: ffffffffffff Found   Key B: ffffffffffff
Sector 35 - Unknown Key A               Unknown Key B
Sector 36 - Unknown Key A               Unknown Key B
Sector 37 - Unknown Key A               Unknown Key B
Sector 38 - Unknown Key A               Unknown Key B
Sector 39 - Unknown Key A               Unknown Key B


Using sector 34 as an exploit sector
Card is not vulnerable to nested attack

Using AVX SIMD core.          


          
 time    | trg | #nonces | Activity                                                | expected to brute force          
         |     |         |                                                         | #states         | time           
-------------------------------------------------------------------------------------------------------------          
       0 |  0? |       0 | Start using 4 threads and AVX SIMD core                 |                 |          
       0 |  0? |       0 | Brute force benchmark: 213 million (2^27.7) keys/s      | 140737488355328 |    8d          
       0 |  0? |       0 | Using 235 precalculated bitflip state tables            | 140737488355328 |    8d          mfoc: ERROR: Reader-answer transfer error, exiting..

Is there anything I can provide to solve that issue ?
Regards,

RV.

Problem for install "configure.ac:19 error"

Hi, i have a problem during installation after git clone.
when i do the command autoreconf -is i have a fail message...
in attachment the full lines.

Hardnested Attack on RPi Zero

I have been using a PN5322 connected to a Raspberry Pi Zero to try and find the keys on a Mifare Classic 4k card. When the process reaches the hardnested attack it throws the following error.

Out of memory error in init_nonce_memory(). Aborting...

Before this it states that it is 'Using no SIMD core.' which is different to the expected response I believe.

Could you assist me in figuring out what this output means?

vk496 / mfoc Goto Github PK

mfoc's People

Contributors

Stargazers

Watchers

Forkers

mfoc's Issues

Recommend Projects

Recommend Topics

Recommend Org