Closed DidierA closed 1 year ago
Yea, we know. Someone else already mentioned it like two days ago. Not sure where it comes from tho unfortunately (yet)
fixed in next release
fixed in release
Thank you, tested this morning, I can confirm it is now working as expected.
Describe the bug.
Using latest Xtreme firmware, NFC Reader attack reports incorrect keys. This is due to a wrong cuid being written in nfc/.mfkey32.log I could pinpoint the issue by emulating a reader with a proxmark3, using the flipper in Reader attack mode and looking at the trace. The UID sent by the flipper is not the one it dumps in the log file.
Reproduction
nfc/.mfkey32.log
.mfkey32.log
, note that the cuid is not correct: it should be the last 4 bytes of the UID reported by the proxmark.Target
No response
Logs
No response
Anything else?
lua script to use on the proxmark: