hf mf nested always responded by turning on all the lights from the proxmark and did not respond anymore. disconnect usb. connect usb. I was totally traumatized by this nested cmd (see post #18 and #29)!!
And so this story began in 2019-04-07 and it ends today!!
Many thanks to iceman, piwi, mwalker, gator96100, gencat and Ollibolli.
Thanks for the support.
Thanks for putting up with me.
"
This is the end
Hold your breath and count to ten
[...]
For this is the end
I've drowned and dreamt this moment
[...]
Let the sky fall
"
iceman wrote:You don't seem to notice what ppl write. Now go back to my previous post and read again.
really!! WTF it's so not me...
Really its you.
]]>]]>HF MF NESTED
You don't seem to notice what ppl write. Now go back to my previous post and read again.
really!! WTF it's so not me...
]]>sudo apt install git build-essential libreadline5 libreadline-dev gcc-arm-none-eabi libusb-0.1-4 libusb-dev libqt4-dev ncurses-dev perl pkg-config libpcsclite-dev pcscd
git clone https://github.com/Proxmark/proxmark3.git
cd proxmark3
make clean && make all
cd client
make
killall ModemManager
./flasher /dev/ttyACM0 -b ../bootrom/obj/bootrom.elf
./flasher /dev/ttyACM0 ../armsrc/obj/fullimage.elf
hw ver
Prox/RFID mark3 RFID instrument
bootrom: master/v3.1.0-173-ga749b1e-suspect 2020-01-09 14:36:52
os: master/v3.1.0-173-ga749b1e-suspect 2020-01-09 14:36:53
fpga_lf.bit built for 2s30vq100 on 2019/11/21 at 09:02:37
fpga_hf.bit built for 2s30vq100 on 2019/11/13 at 14:52:19
hf mf hardnested 0 A a0a1a2a3a4a5 4 B
1 nonces looping forever
ERROR
]]>The infamouse static nonce tag (01 20 01 45)
TAG(228):01 20 01 45 [0000] c[0000]
Normally no fix but just a week ago there was a solution to find keys on that specific bastard to card.
Download latest source code from official repo and run
HF MF NESTED
It will find keys eventually.
]]>root@kali:~/proxmark3/tools/mfkey# make clean && make all
rm -f crypto1.o crapto1.o parity.o util_posix.o mfkey.o mfkey32 mfkey64 mfkey32.exe mfkey64.exe
gcc -std=c99 -D_ISOC99_SOURCE -I../../include -I../../common -I../../client -Wall -O3 -c -o crypto1.o ../../common/crapto1/crypto1.c
gcc -std=c99 -D_ISOC99_SOURCE -I../../include -I../../common -I../../client -Wall -O3 -c -o crapto1.o ../../common/crapto1/crapto1.c
gcc -std=c99 -D_ISOC99_SOURCE -I../../include -I../../common -I../../client -Wall -O3 -c -o parity.o ../../common/parity.c
gcc -std=c99 -D_ISOC99_SOURCE -I../../include -I../../common -I../../client -Wall -O3 -c -o util_posix.o ../../client/util_posix.c
gcc -std=c99 -D_ISOC99_SOURCE -I../../include -I../../common -I../../client -Wall -O3 -c -o mfkey.o ../../client/mifare/mfkey.c
gcc -std=c99 -D_ISOC99_SOURCE -I../../include -I../../common -I../../client -Wall -O3 -o mfkey32 crypto1.o crapto1.o parity.o util_posix.o mfkey.o mfkey32.c
gcc -std=c99 -D_ISOC99_SOURCE -I../../include -I../../common -I../../client -Wall -O3 -o mfkey64 crypto1.o crapto1.o parity.o util_posix.o mfkey.o mfkey64.c
root@kali:~/proxmark3/tools/mfkey#
now running with data collectect from post #32.... (two pairs of AR/NR which can be used to extract keyB from reader for sector 5)
root@kali:~/proxmark3/tools/mfkey# ./mfkey32 12345678 12345678 12345678 12345678 12345678 12345678
recovered key was a0a1a2a3a4a5 (key already known) <---- "two pairs of AR/NR which can be used to extract keyB from reader for sector 5"
Another sad day for Mankind
]]>