Closed GoogleCodeExporter closed 5 years ago
Yes. I'm having the same problem. I thought it was a problem of the delay, so I
started again a recovery of the sector 0 a new setting (mfcuk -C -R 0 -s 250 -S
250 -O dump.bin -v 3) . The results after almost 4 days were the following:
Let me entertain you!
uid: <removed>
type: 08
key: 000000000000
block: 03
diff Nt: 360
auths: 545253
Exactly the same issue.
Original comment by aereal@gmail.com
on 16 Jun 2014 at 9:25
Hi guys!
Does anyone found the solution for this case?
:/
Original comment by Borb...@gmail.com
on 7 Oct 2014 at 3:49
Same here and I do not understand why. I think that my card KEY should be
recovered with mfoc because situation with MIFARE 4K card KYE's are like this:
[Key: ffffffffffff] -> [................xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: a0a1a2a3a4a5] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: d3f7d3f7d3f7] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: 000000000000] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: b0b1b2b3b4b5] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: 4d3a99c351dd] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: 1a982c7e459a] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: aabbccddeeff] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: 714c5c886e97] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: 587ee5f9350f] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: a0478cc39091] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: 533cb6c723f6] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
[Key: 8fd0a4f256e9] -> [/...............xxxxxxxxxxxxxxxxxxxxxxxx]
As you can see in card are default keys, But how ever can't recover key because
mfcuk and mfoc running forever.
Original comment by jons...@gmail.com
on 7 Jan 2015 at 9:37
Encounter same issue, mfcuk keeps running without get any key. Hope someone
could help us fix it.
Original comment by tony.3.4...@gmail.com
on 17 Jan 2015 at 8:58
what does your message log say?
Original comment by rafa...@gmail.com
on 19 Jan 2015 at 2:02
[deleted comment]
Same here, there is no error, it keeps working but it doesnt recover the key.
I've tried only with last versions of mfcuk (0.3.8 and 0.3.7) because
older versions need old libnfc library version, and i cannot make my
reader work with libnfc 1.5.1 or 1.6 it doesn't detect the reader.
I'm using pn532->uart.
I'm using two different cards with default ffffffffffffffff key.
Original comment by b01n4v...@gmail.com
on 18 Feb 2015 at 9:43
Same issue here.
I am now trying to use libnfc 1.5.1 and mfcuk r65 as advised here:
http://www.barisguvercin.com/blog/2015/01/22/mifare-classic-1k-cracking/
I will report if I have any luck.
Original comment by alexandr...@gmail.com
on 18 Apr 2015 at 4:03
If you were looking for more information once Google Code is shut down, "mfcuk revision 65" in many of these blog posts is commit 1b6d022668080aa761a4e2bea8c24c1f7aa537db. The commit date is Sun Sep 23 10:29:36 2012 +0000, the message is:
Convert all remaining dos files to unix format.
I have still not had luck in getting libnfc 1.5.1 and mfcuk r65 working with a unknown card working. However, the issue with the pn532->uart not being detected was resolved by these libnfc configure options:
./configure --prefix=$HOME/nfc/prefix --with-drivers=pn532_uart,pn53x_usb --enable-serial-autoprobe
If you have at least one known key on the card, use mfoc instead of mfcuk. This is reliable even with recent libnfc (1.7.0).
I've now made this operational with a pn532 chip. I used nfc-tools/libnfc@6752951, and nfc-tools/mfcuk@1b6d022, and installed these into a different prefix (like the instructions in the comment above mine) with a different LD_LIBRARY_PATH
so as not to use my (newer) system libnfc.
It takes 45 - 90 minutes to dump a "behaving" card with the software. You should use -v 3
and have a look at the values it returns, the "Let me entertain you" string. When the debugging information is printed, you want the "diff Nt" value to stay below about 300, and the "auths" value to keep incrementing higher. If they stay the same for a long time, you might have a card which mfcuk does not behave on, and you should try a different card.
There may be a way to modify mfcuk to fix misbehaving cards but I have not explored this.
My strategy has been to tell mfcuk to break only a single sector (this is quicker), then using the keys it acquired to seed mfoc, which is much faster but only works if at least one key is known. You can specify this with the -k
option to mfoc, for as many keys as you like, eg:
./mfoc -O mycard.mfc -k 112233445566 -k 665544332211
If you have at least one of each of the A and B keys, you can recover all keys on the card.
mfoc also works fine with current libnfc, so you only need to do funky LD_LIBRARY_PATH and multiple prefix tricks with mfcuk. I have not attempted to fix the software with current libnfc, as unfortunately each attempt at breaking a card takes about an hour.
"Misbehaving cards" where "diff Nt" continues to increment with "auths" above 300 can indicate a couple of different issues:
-s 250 -S 250
) in order to increase the stability of the crack. You should see diff Nt stay below 300, and auths continue to increment above that. This is particularly an issue with the acr122u and pn532 chipsets.ldd
and LD_LIBRARY_PATH
to check and fix).mfcuk
and mfoc
. ~Unfortunately, there's not much you can do about this, apart from wallowing in sadness.~ Edit: Mifare Plus cards are vulnerable to the Hardnested attack, which can replace mfoc
(which implements Nested attack), but you still need to extract one key from a "genuine" reader.If your cards are part of a system, it's probable that the key is generated by a function of the card's UID and sector number. If you have enough older cards (not MF Plus) which are vulnerable, you should be able to figure out the key derivation function once you have a mathematically significant number of samples.
Interesting read. Thank you :)
@micolous I have followed your instructions in using nfc-tools/libnfc@6752951, and nfc-tools/mfcuk@1b6d022. However, while doing make on mfcuk, I encountered the following error.
/home/benjamin/mfcuk/src/mfcuk.c:908: undefined reference to
nfc_configure'
/home/benjamin/mfcuk/src/mfcuk.c:914: undefined reference to nfc_configure' /home/benjamin/mfcuk/src/mfcuk.c:921: undefined reference to
nfc_configure'
/home/benjamin/mfcuk/src/mfcuk.c:931: undefined reference to nfc_initiator_sele ct_passive_target'
According to [https://github.com/nfc-tools/libnfc/issues/182](issue 182), it is a linkage problem. I followed the prefix used here, http://barisguvercin.com/mifare-1k-cracking/. Any ideas on how to solve it? Possible to upload your binaries?
Edit: For anyone who is facing similar problems in future, I recommend you download Kali 2.0. All the libraries and binaries are compatible and working nicely. Plug and play. Live USB. MFCUK, MFOC and libnfc all working.
Thanks Benjamin.
2016-06-10 14:55 GMT+02:00 Benjamin Lim notifications@github.com:
For anyone who is facing similar problems in future, I recommend you download Kali 2.0. All the libraries and binaries are compatible and working nicely. Plug and play. Live USB. MFCUK, MFOC and libnfc all working.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nfc-tools/mfcuk/issues/30#issuecomment-225174550, or mute the thread https://github.com/notifications/unsubscribe/ASwS5v7RkLg0rRMzDqABgkjIn8vAkJ6uks5qKV7OgaJpZM4Fm0Tq .
Anyone found a solution? I'm having the same problem. 56k auths and only 200 Nts.
I'm using Kali Linux and a PN532.
Try ./mfcuk -C -R 3 -S 250 - s 250 -v 3
Has anyone got the solution?
Too old issue.
Hi, This issue is still here ...After adding more printf to debug code I saw that ACR122U fails transceive bits with always the same error NFC_ERFTRANS -20 (RF Transmission Error)
nfc_initiator_transceive_bits(pnd, abtArEnc, 64, abtArEncPar, abtRx, sizeof(abtRx), abtRxPar);
https://github.com/nfc-tools/mfcuk/blob/master/src/mfcuk.c line 600
maybe this is related to Known Issues:
I can also confirm that I am having this issue. What makes this strange is that I am experiencing it even with cards that I have successfully cracked before.
Original issue reported on code.google.com by
sgunder...@bigfoot.com
on 5 Jun 2014 at 8:31