-
Notifications
You must be signed in to change notification settings - Fork 2.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mifare DESFire UID emulation not possible due to "Can not parse file" #2040
Labels
Comments
mh-
added a commit
to mh-/flipperzero-firmware
that referenced
this issue
Nov 22, 2022
I also have this problem with my bus pass, wrote here: #1904 (comment) |
This was referenced Nov 22, 2022
I have one Mifrare Desfire which was read by FZ previously as an |
mh-
added a commit
to mh-/flipperzero-firmware
that referenced
this issue
Nov 24, 2022
Fixes flipperdevices#2040 Minor editorial changes
skotopes
added a commit
that referenced
this issue
Nov 28, 2022
* NFC: Accept non-parsed apps in Mifare DESFire. Fixes #2040 Co-authored-by: gornekich <n.gorbadey@gmail.com> Co-authored-by: あく <alleteam@gmail.com>
Dig03
pushed a commit
to Dig03/flipperzero-firmware
that referenced
this issue
Dec 31, 2022
* NFC: Accept non-parsed apps in Mifare DESFire. Fixes flipperdevices#2040 Co-authored-by: gornekich <n.gorbadey@gmail.com> Co-authored-by: あく <alleteam@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug.
This is related to #1730, but I want to clarify that I do not expect the encrypted (and thus unreadable) data to be saved.
What I do want is that the UID is saved and can be emulated later, by opening a "saved" card.
I only have one particular DESFire card, and it is possible to use a cloned version of that card in its system, by just emulating the UID. I know this works, because the Android app "NFC Card Emulator Pro (Root)" can do that.
Of course, only the UID can be cloned, no encrypted data, but the reader accepts it anyway.
Now, after reading this card, the data which is saved by the firmware is 'a bit short', because of these problems
so the file ends after the
Application IDs:
This causes the "Can not parse file" screen, and nothing can be done with this file.
So I suggest to accept such file (as it was written by the firmware previously) and only emulate the UID, no apps.
I will provide a simple PR for that.
Reproduction
.nfc
fileTarget
No response
Logs
No response
Anything else?
There is a follow-up bug - when trying to emulate the UID of that specific card immediately after the "Read", the external reader will not accept the emulation; and this apparently continues until the Flipper is rebooted, also when using the data from the saved file (which I did after applying the mentioned PR).
The text was updated successfully, but these errors were encountered: