Flipper freeze when emulating Mifare DESfire on a STID card reader

[dreamshape]

Describe the bug.

I work at a place where you access doors with your pass with STID readers and Simons Voss readers we use Mifare DESfire 7b however the readers only read the UID that's not encrypted

I cloned/wrote my badge on a 7b keyfob n it work just fine however when i use the FZ to emulate the key it works on the Simons Voss readers without issues but on the STID readers it works but the screen get stuck on the emulation screen n i gotta reset it everytime after using it

issue doesn't happen when i use a magic nfc

Same issue both on latest UL and Xtrem fw

Another odd thing is maybe 1/4 times if i swipe quickly enough for the STID to read my FZ but not too long it doesn't get stuck so idk if it's something about the reader sending something /after/ recognizing the card that makes the FZ freeze

Reproduction

1. go to nfc
2. emulation
3. swipe the FZ for more than 1,5 seconds
4. it works
5. it get stucks
6. i reboot the fz
7. repeat each time i need to use the elevator reader

Target

STID NFC readers

Logs

No response

Anything else?

No response

[xMasterX]

Can you verify it on latest OFFICIAL firmware? latest dev or release

[dreamshape]

eh right nvm I checked with the official fw it does the same

[xMasterX]

eh right nvm I checked with the official fw it does the same

Can you please create same issue in official firmware and attach your reader photo or model? Also add your nfc file if possible

[dreamshape]

sure I'll do that on the forum.flipperzero thing

[UrSuLa360]

The bug happens with other readers, like a dl533n usb nfc reader with libnfc. When the reader interacts with flipper emulating desfire uid, it gets frozen. If you don't interact with any reader, bug doesn't happen.

[dreamshape]

@UrSuLa360 by that you mean that it'll get unfrozen if i wait for a while without rebooting?

[dreamshape]

there's the nfc file just wondering would removing everything under mifare desfire specific data changes anything ? since the reader only check the uid

Details

# Nfc device type can be UID, Mifare Ultralight, Mifare Classic, Bank card Device type: Mifare DESFire # UID, ATQA and SAK are common for all formats UID: 04 5F 3E 0A 29 6F 80 ATQA: 03 44 SAK: 20 # Mifare DESFire specific data PICC Version: 04 01 01 12 00 1A 05 04 01 01 02 01 1A 05 04 5F 3E 0A 29 6F 80 CF 0E 56 45 30 28 20 PICC Free Memory: 8192 PICC Change Key ID: 00 PICC Config Changeable: true PICC Free Create Delete: true PICC Free Directory List: true PICC Key Changeable: true PICC Max Keys: 01 PICC Key 0 Version: 00 Application Count: 0

[UrSuLa360]

@UrSuLa360 by that you mean that it'll get unfrozen if i wait for a while without rebooting?

no, once you interacted with the reader the flipper gets unresponsive.

I just wanted to point, flipper is responsive until any communication with the reader is performed

[dreamshape]

i had a full NFC debug file that I deleted to try again to emulate on debug mode but now there's no debug file that get created when i try to scan on the STID reader?Le 14 juin 2023 11:58, nahaki @.***> a écrit : Thanks for sharing

—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

[UrSuLa360]

today i tested it with 62e and it worked correctly. can you still reproduce this bug @dreamshape with latest version?

[dreamshape]

It didn't work with a clone I previously made but I recloned it with the latest version and indeed it work so that's cool :v wonder what did they changed I might try to compare the old and new .NFC file to see what's different