Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03) #28

Open
GoogleCodeExporter opened this issue Apr 19, 2015 · 44 comments
Open

Comments

@GoogleCodeExporter
Copy link

mfcuk -C -R 0:A -v 1 -o lalal.dmp

mfcuk - 0.3.8
Mifare Classic DarkSide Key Recovery Tool - 0.3
by Andrei Costin, [email protected], http:https://andreicostin.com

WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_skgt.mfd'
WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_ratb.mfd'
WARN: cannot open template file 
'./data/tmpls_fingerprints/mfcuk_tmpl_oyster.mfd'

INFO: Connected to NFC reader: ACS / ACR122U PICC Interface



INITIAL ACTIONS MATRIX - UID fb d5 dc 7f - TYPE 0x08 (MC1K)
---------------------------------------------------------------------
Sector  |    Key A  |ACTS | RESL    |    Key B  |ACTS | RESL
---------------------------------------------------------------------
0   |  000000000000 | . R | . . |  000000000000 | . . | . .
1   |  000000000000 | . . | . . |  000000000000 | . . | . .
2   |  000000000000 | . . | . . |  000000000000 | . . | . .
3   |  000000000000 | . . | . . |  000000000000 | . . | . .
4   |  000000000000 | . . | . . |  000000000000 | . . | . .
5   |  000000000000 | . . | . . |  000000000000 | . . | . .
6   |  000000000000 | . . | . . |  000000000000 | . . | . .
7   |  000000000000 | . . | . . |  000000000000 | . . | . .
8   |  000000000000 | . . | . . |  000000000000 | . . | . .
9   |  000000000000 | . . | . . |  000000000000 | . . | . .
10  |  000000000000 | . . | . . |  000000000000 | . . | . .
11  |  000000000000 | . . | . . |  000000000000 | . . | . .
12  |  000000000000 | . . | . . |  000000000000 | . . | . .
13  |  000000000000 | . . | . . |  000000000000 | . . | . .
14  |  000000000000 | . . | . . |  000000000000 | . . | . .
15  |  000000000000 | . . | . . |  000000000000 | . . | . .


VERIFY: 
    Key A sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f
    Key B sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f


ACTION RESULTS MATRIX AFTER VERIFY - UID fb d5 dc 7f - TYPE 0x08 (MC1K)
---------------------------------------------------------------------
Sector  |    Key A  |ACTS | RESL    |    Key B  |ACTS | RESL
---------------------------------------------------------------------
0   |  000000000000 | . R | . . |  000000000000 | . . | . .
1   |  000000000000 | . . | . . |  000000000000 | . . | . .
2   |  000000000000 | . . | . . |  000000000000 | . . | . .
3   |  000000000000 | . . | . . |  000000000000 | . . | . .
4   |  000000000000 | . . | . . |  000000000000 | . . | . .
5   |  000000000000 | . . | . . |  000000000000 | . . | . .
6   |  000000000000 | . . | . . |  000000000000 | . . | . .
7   |  000000000000 | . . | . . |  000000000000 | . . | . .
8   |  000000000000 | . . | . . |  000000000000 | . . | . .
9   |  000000000000 | . . | . . |  000000000000 | . . | . .
10  |  000000000000 | . . | . . |  000000000000 | . . | . .
11  |  000000000000 | . . | . . |  000000000000 | . . | . .
12  |  000000000000 | . . | . . |  000000000000 | . . | . .
13  |  000000000000 | . . | . . |  000000000000 | . . | . .
14  |  000000000000 | . . | . . |  000000000000 | . . | . .
15  |  000000000000 | . . | . . |  000000000000 | . . | . .


RECOVER:  0mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)


and he cant recover any key



Original issue reported on code.google.com by [email protected] on 1 Mar 2014 at 7:41

@GoogleCodeExporter
Copy link
Author

same error here. 

Original comment by [email protected] on 31 Mar 2014 at 4:59

@GoogleCodeExporter
Copy link
Author

some sectors had the same error.
is it related with the "WARN: cannot open *.mfd"?

Original comment by [email protected] on 3 Apr 2014 at 5:46

@GoogleCodeExporter
Copy link
Author

same error here... 

Original comment by [email protected] on 3 Sep 2014 at 11:13

@GoogleCodeExporter
Copy link
Author

I got this error only with some tags. I can read and write it using the key 
(the card works fine) but when running mfcuk this error is shown. Maybe is a 
kind of card protection against this attack?

Original comment by [email protected] on 13 Sep 2014 at 5:12

@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

I think that is a defect in the card. I have a set of equal cards (all of them 
with are more than 5 years old) and with some of them mfcuk works and some 
doesnt work. I'm also having troubles when writing the key blocks so I guess 
that one day these cards will stop working

Original comment by [email protected] on 7 Dec 2014 at 2:57

@GoogleCodeExporter
Copy link
Author

Got the same problem here, Ubuntu 14.10 with a ACR-122u. Key is always 
000000000000 which i think is a bit fishy. Any ideas on a fix?

Original comment by [email protected] on 23 Jan 2015 at 12:07

@GoogleCodeExporter
Copy link
Author

Getting the same error, would like to know if someone found a solution.

Original comment by [email protected] on 26 Jan 2015 at 1:07

@ilfuriano
Copy link

Same error

@facunava92
Copy link

i got the same mistake, i've installed libnfc 1.7.0 and mfcuk 0.3.8 and still having 0x03 , anyone has any clue?

@rezatoune
Copy link

Error 0x03 is "Crapto1 error". I don't know (couldn't find) why it does it, but tried another card and it worked like a charm, software /hardware setup hadn't changed apart from the card.

@rclsilver
Copy link

@rezatoune Could you provides list of versions for libnfc et mfcuk please?

@unixpapers
Copy link

Hi! I have the same problem

mfcuk - 0.3.8, libnfc - 1.7.1 (last from git)

mfcuk -C -R 0:A -s 250 -S 250 -v 3

mfcuk - 0.3.8
Mifare Classic DarkSide Key Recovery Tool - 0.3
by Andrei Costin, [email protected],

INFO: Connected to NFC reader: Adafruit PN532 board via UART



INITIAL ACTIONS MATRIX - UID f7 b2 d9 b9 - TYPE 0x08 (MC1K)
---------------------------------------------------------------------
Sector    |    Key A    |ACTS | RESL    |    Key B    |ACTS | RESL
---------------------------------------------------------------------
0    |  000000000000    | . R | . .    |  000000000000    | . . | . .
1    |  000000000000    | . . | . .    |  000000000000    | . . | . .
2    |  000000000000    | . . | . .    |  000000000000    | . . | . .
3    |  000000000000    | . . | . .    |  000000000000    | . . | . .
4    |  000000000000    | . . | . .    |  000000000000    | . . | . .
5    |  000000000000    | . . | . .    |  000000000000    | . . | . .
6    |  000000000000    | . . | . .    |  000000000000    | . . | . .
7    |  000000000000    | . . | . .    |  000000000000    | . . | . .
8    |  000000000000    | . . | . .    |  000000000000    | . . | . .
9    |  000000000000    | . . | . .    |  000000000000    | . . | . .
10    |  000000000000    | . . | . .    |  000000000000    | . . | . .
11    |  000000000000    | . . | . .    |  000000000000    | . . | . .
12    |  000000000000    | . . | . .    |  000000000000    | . . | . .
13    |  000000000000    | . . | . .    |  000000000000    | . . | . .
14    |  000000000000    | . . | . .    |  000000000000    | . . | . .
15    |  000000000000    | . . | . .    |  000000000000    | . . | . .


VERIFY: 
    Key A sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f
    Key B sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f


ACTION RESULTS MATRIX AFTER VERIFY - UID f7 b2 d9 b9 - TYPE 0x08 (MC1K)
---------------------------------------------------------------------
Sector    |    Key A    |ACTS | RESL    |    Key B    |ACTS | RESL
---------------------------------------------------------------------
0    |  000000000000    | . R | . .    |  000000000000    | . . | . .
1    |  000000000000    | . . | . .    |  000000000000    | . . | . .
2    |  000000000000    | . . | . .    |  000000000000    | . . | . .
3    |  000000000000    | . . | . .    |  000000000000    | . . | . .
4    |  000000000000    | . . | . .    |  000000000000    | . . | . .
5    |  000000000000    | . . | . .    |  000000000000    | . . | . .
6    |  000000000000    | . . | . .    |  000000000000    | . . | . .
7    |  000000000000    | . . | . .    |  000000000000    | . . | . .
8    |  000000000000    | . . | . .    |  000000000000    | . . | . .
9    |  000000000000    | . . | . .    |  000000000000    | . . | . .
10    |  000000000000    | . . | . .    |  000000000000    | . . | . .
11    |  000000000000    | . . | . .    |  000000000000    | . . | . .
12    |  000000000000    | . . | . .    |  000000000000    | . . | . .
13    |  000000000000    | . . | . .    |  000000000000    | . . | . .
14    |  000000000000    | . . | . .    |  000000000000    | . . | . .
15    |  000000000000    | . . | . .    |  000000000000    | . . | . .


RECOVER:  0
-----------------------------------------------------
Let me entertain you!
    uid: b9d9b2f7
   type: 08
    key: 000000000000
  block: 03
diff Nt: 0
  auths: 0
-----------------------------------------------------

mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)

-----------------------------------------------------
Let me entertain you!
    uid: b9d9b2f7
   type: 08
    key: 000000000000
  block: 03
diff Nt: 26
  auths: 59
-----------------------------------------------------
......
-----------------------------------------------------
Let me entertain you!
    uid: f7b2d9b9
   type: 08
    key: 000000000000
  block: 03
diff Nt: 90
  auths: 1332

And etc display error mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03) auths inc but key not recovery. RFID work.

Please help me, try to use r65 version of mfcuk and libnfc 1.5.1. NFC reader is pn532 Breakout Board. Help me please

@whirlwind110
Copy link

~$ sudo mfcuk -C -R 0:A -v 2

mfcuk - 0.3.8
Mifare Classic DarkSide Key Recovery Tool - 0.3
by Andrei Costin, [email protected], http:https://andreicostin.com

WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_skgt.mfd'
WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_ratb.mfd'
WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_oyster.mfd'

INFO: Connected to NFC reader: ACS / ACR122U PICC Interface



INITIAL ACTIONS MATRIX - UID fb 83 a2 1a - TYPE 0x08 (MC1K)
---------------------------------------------------------------------
Sector  |    Key A  |ACTS | RESL    |    Key B  |ACTS | RESL
---------------------------------------------------------------------
0   |  000000000000 | . R | . . |  000000000000 | . . | . .
1   |  000000000000 | . . | . . |  000000000000 | . . | . .
2   |  000000000000 | . . | . . |  000000000000 | . . | . .
3   |  000000000000 | . . | . . |  000000000000 | . . | . .
4   |  000000000000 | . . | . . |  000000000000 | . . | . .
5   |  000000000000 | . . | . . |  000000000000 | . . | . .
6   |  000000000000 | . . | . . |  000000000000 | . . | . .
7   |  000000000000 | . . | . . |  000000000000 | . . | . .
8   |  000000000000 | . . | . . |  000000000000 | . . | . .
9   |  000000000000 | . . | . . |  000000000000 | . . | . .
10  |  000000000000 | . . | . . |  000000000000 | . . | . .
11  |  000000000000 | . . | . . |  000000000000 | . . | . .
12  |  000000000000 | . . | . . |  000000000000 | . . | . .
13  |  000000000000 | . . | . . |  000000000000 | . . | . .
14  |  000000000000 | . . | . . |  000000000000 | . . | . .
15  |  000000000000 | . . | . . |  000000000000 | . . | . .


VERIFY: 
    Key A sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f
    Key B sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f


ACTION RESULTS MATRIX AFTER VERIFY - UID fb 83 a2 1a - TYPE 0x08 (MC1K)
---------------------------------------------------------------------
Sector  |    Key A  |ACTS | RESL    |    Key B  |ACTS | RESL
---------------------------------------------------------------------
0   |  000000000000 | . R | . . |  000000000000 | . . | . .
1   |  000000000000 | . . | . . |  000000000000 | . . | . .
2   |  000000000000 | . . | . . |  000000000000 | . . | . .
3   |  000000000000 | . . | . . |  000000000000 | . . | . .
4   |  000000000000 | . . | . . |  000000000000 | . . | . .
5   |  000000000000 | . . | . . |  000000000000 | . . | . .
6   |  000000000000 | . . | . . |  000000000000 | . . | . .
7   |  000000000000 | . . | . . |  000000000000 | . . | . .
8   |  000000000000 | . . | . . |  000000000000 | . . | . .
9   |  000000000000 | . . | . . |  000000000000 | . . | . .
10  |  000000000000 | . . | . . |  000000000000 | . . | . .
11  |  000000000000 | . . | . . |  000000000000 | . . | . .
12  |  000000000000 | . . | . . |  000000000000 | . . | . .
13  |  000000000000 | . . | . . |  000000000000 | . . | . .
14  |  000000000000 | . . | . . |  000000000000 | . . | . .
15  |  000000000000 | . . | . . |  000000000000 | . . | . .


RECOVER:  0mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
^C

@TheSnowfield
Copy link

same error :( use pn532 - CP2102 UART on KaliLinux
by accident I found use the usb hub with external power can reduce such errors??
usb power supply shortage?

`
root@rabbittu:~# mfcuk -C -R 0:A -v 1 -o card.dmp
mfcuk - 0.3.8
Mifare Classic DarkSide Key Recovery Tool - 0.3
by Andrei Costin, [email protected], http:https://andreicostin.com

WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_skgt.mfd'
WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_ratb.mfd'
WARN: cannot open template file './data/tmpls_fingerprints/mfcuk_tmpl_oyster.mfd'

INFO: Connected to NFC reader: pn532_uart:/dev/ttyUSB0

INITIAL ACTIONS MATRIX - UID 10 40 bb 2e - TYPE 0x08 (MC1K)

Sector | Key A |ACTS | RESL | Key B |ACTS | RESL

0 | 000000000000 | . R | . . | 000000000000 | . . | . .
1 | 000000000000 | . . | . . | 000000000000 | . . | . .
2 | 000000000000 | . . | . . | 000000000000 | . . | . .
3 | 000000000000 | . . | . . | 000000000000 | . . | . .
4 | 000000000000 | . . | . . | 000000000000 | . . | . .
5 | 000000000000 | . . | . . | 000000000000 | . . | . .
6 | 000000000000 | . . | . . | 000000000000 | . . | . .
7 | 000000000000 | . . | . . | 000000000000 | . . | . .
8 | 000000000000 | . . | . . | 000000000000 | . . | . .
9 | 000000000000 | . . | . . | 000000000000 | . . | . .
10 | 000000000000 | . . | . . | 000000000000 | . . | . .
11 | 000000000000 | . . | . . | 000000000000 | . . | . .
12 | 000000000000 | . . | . . | 000000000000 | . . | . .
13 | 000000000000 | . . | . . | 000000000000 | . . | . .
14 | 000000000000 | . . | . . | 000000000000 | . . | . .
15 | 000000000000 | . . | . . | 000000000000 | . . | . .

VERIFY:
Key A sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f
Key B sectors: 0 1 2 3 4 5 6 7 8 9 a b c d e f

ACTION RESULTS MATRIX AFTER VERIFY - UID 10 40 bb 2e - TYPE 0x08 (MC1K)

Sector | Key A |ACTS | RESL | Key B |ACTS | RESL

0 | 000000000000 | . R | . . | 000000000000 | . . | . .
1 | 000000000000 | . . | . . | 000000000000 | . . | . .
2 | 000000000000 | . . | . . | 000000000000 | . . | . .
3 | 000000000000 | . . | . . | 000000000000 | . . | . .
4 | 000000000000 | . . | . . | 000000000000 | . . | . .
5 | 000000000000 | . . | . . | 000000000000 | . . | . .
6 | 000000000000 | . . | . . | 000000000000 | . . | . .
7 | 000000000000 | . . | . . | 000000000000 | . . | . .
8 | 000000000000 | . . | . . | 000000000000 | . . | . .
9 | 000000000000 | . . | . . | 000000000000 | . . | . .
10 | 000000000000 | . . | . . | 000000000000 | . . | . .
11 | 000000000000 | . . | . . | 000000000000 | . . | . .
12 | 000000000000 | . . | . . | 000000000000 | . . | . .
13 | 000000000000 | . . | . . | 000000000000 | . . | . .
14 | 000000000000 | . . | . . | 000000000000 | . . | . .
15 | 000000000000 | . . | . . | 000000000000 | . . | . .

RECOVER: 0mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x03)
`

@hunter86bg
Copy link

hunter86bg commented Dec 10, 2016

Hey guys,

I'm trying the attack against a blank chinese card with default keys.
I'm using the latest Kali_Rolling (W49) with mfcuk-0.3.8 and libnfs-1.7.1

I have tried both with and without delay.Here is partial ouput generated by strace (-s 10000 -S 10000):
http:https://pastebin.com/0ZG7Qazh

@TheSnowfield
Copy link

@hunter86bg So...how to solve such like "(error code=0x03)" problem? I want to give up crack it... :(

@hunter86bg
Copy link

I got no clue.The info I have provided is for easier debugging.

@TheSnowfield
Copy link

All right....Thx :p @hunter86bg

@daiaji
Copy link

daiaji commented May 28, 2017

https://www.dropbox.com/s/9a3tawn0mcd13h0/PN532-mfoc-mfcuk-windows.zip?dl=0
The bin on the binary file can work on my PN532 of pl2303
But unfortunately
There is no modified source code :(

@hunter86bg
Copy link

It's windows stuff ... I don't do windows :) and I doubt I would open anything from dropbox...

@TheSnowfield
Copy link

@daiaji wow,It seems work fine on windows 10 64-bit
扇区 00 - 发现 秘钥 A: 702004070762 发现 秘钥 B: 702004070762
扇区 01 - 发现 秘钥 A: 702004070762 发现 秘钥 B: 702004070762
扇区 02 - 发现 秘钥 A: 702004070762 发现 秘钥 B: 702004070762
扇区 03 - 发现 秘钥 A: 702004070762 发现 秘钥 B: 702004070762
扇区 04 - 发现 秘钥 A: 702004070762 发现 秘钥 B: 702004070762
扇区 05 - 发现 秘钥 A: 702004070762 发现 秘钥 B: 702004070762
扇区 06 - 发现 秘钥 A: 702004070762 发现 秘钥 B: 702004070762
扇区 07 - 发现 秘钥 A: 702004070762 发现 秘钥 B: 702004070762
扇区 08 - 未知 秘钥 A 未知 秘钥 B
扇区 09 - 未知 秘钥 A 未知 秘钥 B
扇区 10 - 未知 秘钥 A 未知 秘钥 B
扇区 11 - 未知 秘钥 A 未知 秘钥 B

No source code..... :( But I saw there's a Email in the console.

@daiaji
Copy link

daiaji commented Jun 18, 2017

@Xiaoyu2016 我是在用PN532的板子焊上针脚然后接pl2303TTL转USB
kali-linux-2017.1-i386.iso上用mfcuk跑了一发全扇区加密的M1卡 然后就ERROR: mfcuk_key_recovery_block() (error code=0x03) 了
win10上用那个编译后的mfcuk跑是没问题的……
程序呢是在吾爱捡来的
说起来xiaoyu2016你是在跑mfoc吧
为什么用中文 因为我没法保证翻译机能够完整的翻译这段话
Issues我看了一下还是不知道怎么帮助debug(智商过低)
我只能寄希望于你们了(他力本愿)

@TheSnowfield
Copy link

@daiaji (原来你会中文)我跟你的装备都是差不多的, 但是我在尝试的时候, 发现很多卡已经不能够被这样破解了, 能破解的只有3年前的高中水卡....除非发现新漏洞, 我感觉这意义不是很大.另外, 我的学校已经采用了全新的银行卡进行刷卡..学校内所有的刷卡消费都是通过银行卡里边的IC...不能再变态了... 所以没什么办法...

@whirlwind110
Copy link

whirlwind110 commented Jun 21, 2017

@daiaji @Xiaoyu2016

老哥们,给个QQ微信吧,,哈哈哈,,假装跟老外扯英语好难过。。。貌似作者都不怎么维护了。

@JoaoSobral
Copy link

This issue is solved by Stewark8 in a branch version of mfuck in https://github.com/DrSchottky/mfcuk it is advised to use the flag -w 6 for sensitive cards to this issue. So compile this version of mfcuk

I tried and it works perfectly no more 0x03 errors. I am also using libnfc1.5.3.

Cheers

@TheSnowfield
Copy link

@JoaoSobral Thx! God bless you :3

@whirlwind110
Copy link

@JoaoSobral
Wow! good job!

@daiaji
Copy link

daiaji commented Aug 4, 2017

@JoaoSobral coooooool!

@tobiasakesson
Copy link

@JoaoSobral So you are using the mfcuk version that Stewark8 has made and the libnfc1.5.3?

Is anyone else using libnfc1.7.1? I still have the issue and am wondering if I need to fix libnfc1.5.3 to solve it.

@JoaoSobral
Copy link

JoaoSobral commented Oct 9, 2017

@tobiasakesson

Tjena Tobias,

That is true. There is a bug in the mfcuk that does not allow to properly work with the new libnfc1.7.1 at least with the ACR122U.

Please downgrade it to <= libnfc1.5.3 and it will work like a charm. I just used a vmware image of Kali Linux and modified it. But a clean solution would be using a clean distribution as CentOS or similar and do it from the scratch.

Note: quote: "You cannot use mfcuk, because libnfc 1.7.1 needs to be installed to blacklist the kernel’s built-in drivers for the ACR122U, which will otherwise interfere with pcsclite."

@Meth84
Copy link

Meth84 commented Oct 15, 2017

@JoaoSobral I guess you were are using Kali linux same here, and @tobiasakesson how do you downgraded to libnfc 1.5.3 and how do you use the MFCUK of Stewark8 to be the default in Kali
Thanks

@eSenKaa
Copy link

eSenKaa commented Oct 10, 2018

up @JoaoSobral @Meth84 @tobiasakesson , I have the same problem . Where can I find the libnfc 1.5.3 and how do you use the MFCUK to be the default in kali linux, thanks a lot

@daiaji
Copy link

daiaji commented May 25, 2019

@Meth84 @eSenKaa
https://github.com/daiaji/libnfc-1.5.1
Cong. sub and config. guess have been updated to handle compilation on the arm64 architecture.

Building

It should be as simple as running these two commands:

./configure
make

@pr414
Copy link

pr414 commented Sep 29, 2019

There's a way to fix all these errors even with 1.7.1. I'm just showing it to fix the problems.
This solution allows you to use libnfc-1.7.1 with DrSchottky's Mfcuk.
The problem appears if you compile and install it the normal way.
First, get this version of mfcuk:

sudo git clone https://github.com/DrSchottky/mfcuk.git

then, compile with these commands:

cd mfcuk
sudo libtoolize
sudo aclocal
sudo autoconf
sudo autoheader
sudo automake --add-missing
sudo automake
sudo autoreconf -vis
sudo ./configure
sudo make
sudo make install

To make it work,

sudo mfcuk -C -R 0:A -w 6 -v 3

Cheers Guys, have fun.
(Oh, and don't use this for illegal purpose)

@sferia82
Copy link

sferia82 commented Feb 5, 2020

the repository not exist. any idea? thanks

@OscarGomezGonzalez
Copy link

@sferia82
hi, I think @TheGlitchyCoder wanted to say this
https://github.com/DrSchottky/mfcuk

@xavave
Copy link

xavave commented Feb 11, 2020

for people on windows 64 bits, I've already cross compiled all tools --> here

http:https://legacy.averbouch.biz/libnfc-and-nfc-utils-binaries-on-windows-10/

ZIP CONTENT :
cropto1_bs.exe
libgcc_s_seh-1.dll
liblzma-5.dll
libnfc.dll
libnfc_crypto_crack.exe
libusb0.dll
libwinpthread-1.dll
mfcuk_keyrecovery_darkside.exe
mfoc.exe
mfoc_hardnested.exe
nfc-anticol.exe
nfc-barcode.exe
nfc-dep-initiator.exe
nfc-dep-target.exe
nfc-detect-chinese-magic-card.exe
nfc-emulate-forum-tag2.exe
nfc-emulate-forum-tag4.exe
nfc-emulate-tag.exe
nfc-emulate-uid.exe
nfc-jewel.exe
nfc-list.exe
nfc-mfclassic.exe
nfc-mfsetuid.exe
nfc-mfultralight.exe
nfc-poll.exe
nfc-read-forum-tag3.exe
nfc-relay-picc.exe
nfc-relay.exe
nfc-scan-device.exe
pn53x-diagnose.exe
pn53x-sam.exe
pn53x-tamashell.exe
solve_bs.exe

@pr414
Copy link

pr414 commented Sep 9, 2020

@sferia82 @OscarGomezGonzalez Yeah I fixed it now

@pr414
Copy link

pr414 commented Sep 9, 2020 via email

@and33sand
Copy link

and33sand commented Nov 14, 2020

Hi guys, when start "libtoolize" coming this ---->
root@kali:/mfcuk# libtoolize
libtoolize: putting macros in AC_CONFIG_MACRO_DIRS, 'm4'.
libtoolize: You should add the contents of 'm4/libtool.m4' to 'aclocal.m4'.
libtoolize: You should add the contents of 'm4/ltoptions.m4' to 'aclocal.m4'.
libtoolize: You should add the contents of 'm4/ltsugar.m4' to 'aclocal.m4'.
libtoolize: You should add the contents of 'm4/ltversion.m4' to 'aclocal.m4'.
libtoolize: You should add the contents of 'm4/lt
obsolete.m4' to 'aclocal.m4'.
libtoolize: Remember to add 'LT_INIT' to configure.ac.
libtoolize: Consider adding '-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
root@kali:~/mfcuk#
Don't know what to do.......

@tutan7
Copy link

tutan7 commented Oct 2, 2022

Hi guys,
Tried the standard libnfc 1.7.1 + mfcuk but received the error ERROR: mfcuk_key_recovery_block() (error code=0x03).

Installed ibnfc 1.5.1 and the error continued.
Now im trying to install https://github.com/DrSchottky/mfcuk

Tried to instructions listed in the repo but error occurred.
Also tried the instructions above:
cd mfcuk
sudo libtoolize
sudo aclocal
sudo autoconf
sudo autoheader
sudo automake --add-missing
sudo automake
sudo autoreconf -vis
sudo ./configure
sudo make
sudo make install

After the last command "sudo make install" received the error:
Making install in src
make[1]: Entering directory '/home/kali/keys1/mfcuk/mfcuk/src'
CC mifare.o
In file included from mifare.c:35:
mifare.h:79:34: error: unknown type name ‘nfc_device’; did you mean ‘nfc_device_t’?
79 | bool nfc_initiator_mifare_cmd(nfc_device *pnd, const mifare_cmd mc, const uint8_t ui8Block, mifare_param *pmp);
| ^~~~~~~~~~
| nfc_device_t
mifare.c:55:26: error: unknown type name ‘nfc_device’; did you mean ‘nfc_device_t’?
55 | nfc_initiator_mifare_cmd(nfc_device *pnd, const mifare_cmd mc, const uint8_t ui8Block, mifare_param *pmp)
| ^~~~~~~~~~
| nfc_device_t
make[1]: *** [Makefile:381: mifare.o] Error 1
make[1]: Leaving directory '/home/kali/keys1/mfcuk/mfcuk/src'
make: *** [Makefile:367: install-recursive] Error 1

Troubleshoot a lot but without success.
Im I doing something wrong?
Thank you in advance!
PS. Im using PN532 on UART on KaliLinux.
PS2. mfoc is working fine on blank tags

@andariel1985
Copy link

andariel1985 commented Jan 2, 2023

Hi @JoaoSobral, I've installed libnfc 1.5.1 using these commands:

mkdir -p ~/builds/nfc
cd ~/builds/nfc
wget https://github.com/nfc-tools/libnfc/releases/download/libnfc-1.5.1/libnfc-1.5.1.tar.gz
tar zxf libnfc-1.5.1.tar.gz
cd libnfc-1.5.1
./configure --prefix=/home/myusername/builds/nfc/prefix --with-drivers=all --sysconfdir=/etc/nfc --enable-serial-autoprobe
make
make install

but I still get this message: nfc-list uses libnfc 1.7.1

Is it incorret to install libnfc-bin and libnfc-dev?

Could you gently post the commands to completely remove libnfc 1.7.1?

@pr414 could you please post the commands to completely remove the old version of mfcuk before installing 'DrSchottky' version?

Many thanks and a happy new year to everyone! :)

@liwenjie119
Copy link

for people on windows 64 bits, I've already cross compiled all tools --> here

http:https://legacy.averbouch.biz/libnfc-and-nfc-utils-binaries-on-windows-10/

ZIP CONTENT : cropto1_bs.exe libgcc_s_seh-1.dll liblzma-5.dll libnfc.dll libnfc_crypto_crack.exe libusb0.dll libwinpthread-1.dll mfcuk_keyrecovery_darkside.exe mfoc.exe mfoc_hardnested.exe nfc-anticol.exe nfc-barcode.exe nfc-dep-initiator.exe nfc-dep-target.exe nfc-detect-chinese-magic-card.exe nfc-emulate-forum-tag2.exe nfc-emulate-forum-tag4.exe nfc-emulate-tag.exe nfc-emulate-uid.exe nfc-jewel.exe nfc-list.exe nfc-mfclassic.exe nfc-mfsetuid.exe nfc-mfultralight.exe nfc-poll.exe nfc-read-forum-tag3.exe nfc-relay-picc.exe nfc-relay.exe nfc-scan-device.exe pn53x-diagnose.exe pn53x-sam.exe pn53x-tamashell.exe solve_bs.exe

the libnfc.dll cannot use in win11 x64. The program ends directly without any output

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests