configure -prefix=/home//builds/nfc/prefix $ LIBNFC_CFLAGS=-I/home//builds/nfc/prefix/include LIBNFC_LIBS="-L/home//builds/nfc/prefix/lib -lnfc". Now, let’s compile mfcuk and make it use our newly compiled version of libnfc. Now, let’s compile this older libnfc version and install it in a local directory to avoid messing up the system libraries. So let’s start by getting these, together with pcsclite and the PC/SC drivers for the ACR122U. mfcuk r65 and libnfc 1.5.1Ī working combination of mfcuk and libnfc seems to be mfcuk r65 and libnfc 1.5.1. I use yaourt to install packages from the AUR. Also, take care to replace all instances of with your own username. Note that # command means that the command should be executed as root, and that $ command should be executed as your own user. So, let’s install duplicate copies of libnfc to get everything working. This older version is, in turn, not compatible with mfoc. However, this will also require an older version of libnfc. The fix seems to be to use an older version of mfcuk.
I assume that the bug described in is the one causing trouble. I launched an attack using mfcuk and got a key back after some time. The problemĪfter installing libnfc, together with mfcuk and mfoc using AUR in Arch Linux, everything seemed to work. When one key is found, mfoc can be used to find all other keys within minutes. A typical attack scenario is to use mfcuk to find the first key of the card (which may take quite some time).
There are two well-known applications for this: mfcuk and mfoc. To be able to decrypt the content of the card, the keys must be found. The different sectors of the MIFARE Classic card are protected by different keys. I recently bought an ACR122U reader to play around with RFID, and especially MIFARE Classic cards because of their low security and widespread adoption.
0 kommentar(er)
