Using mfcuk r65 with libnfc 1.5.1 in 2018

mfcuk_r65.md

You first need to download both libnfc 1.5.1 and mfcuk r65. The former is available among github releases wile the latter can be obtained via git rebase.

If you're on Arch you'll need pcsclite, if on Debian derivates libpcsclite-dev

Let's compile libnfc (<user> is your username)

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/<user>/builds/nfc/prefix --with-drivers=all --sysconfdir=/etc/nfc --enable-serial-autoprobe
make
make install
cd ..

./configure options are needed to enable editing options via the usual /etc/nfc/libnfc.conf file and to allow using a PN532 shield with a USB-UART interface.

Then, for mfcuk

git clone https://github.com/nfc-tools/mfcuk mfcuk-r65
cd mfcuk-r65
git reset --hard 1b6d022
autoreconf -is
LIBNFC_CFLAGS=-I/home/<user>/builds/nfc/prefix/include LIBNFC_LIBS="-L/home/<user>/builds/nfc/prefix/lib -lnfc" ./configure --prefix=/home/<user>/builds/nfc/prefix
make

If needed, uncomment last line in /etc/nfc/libnfc.conf to enable PN532 discovery. You'll now need to run these last 2 commands

cd /home/<user>/builds/nfc/mfcuk-r65/src
LD_LIBRARY_PATH=/home/<user>/builds/nfc/prefix/lib ./mfcuk -C -R 0:A -v 3

Sorry for the poorly written doc, it's mostly a personal reminder for future reference

Thanks guys. Compiled and finally working mfcuk r65 with libnfc1.5.1, but getting endless mfcuk_key_recovery_block() error (code 0x09). I think this has been posted elsewhere nfc-tools/mfcuk#56, but just wondering if anyone else has ideas? Thanks

Thank you so much. It works for me to on Arch Linux (5.2.6-arch1-1-ARCH [20190807]) but it stop the scan after a while, with this error:
mfcuk: ERROR: mfcuk_key_recovery_block() (error code=0x08) mfcuk: ERROR: configuring NDO_ACTIVATE_FIELD
Does anyone know how to handle it? I cannot figuring out how to fix

@gozzolino95 You better read issues in mfuck original repo for that
@alexhng1 No idea, sorry. mfcuk isn't that reliable, I guess
@kopolindo I have never stumbled upon this particular error, partially because I don't really need to use mfcuk owning two proxmarks.
Similar errors were present in MFOC and were due to timing issues, you could have a look at the code to see if there are similar issues.