-
-
Notifications
You must be signed in to change notification settings - Fork 892
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
Support "Gen3" magic tags #336
Comments
|
Step 1: I need to buy Gen3 tags! |
I got some tags. I did some implementation. It did change the UID but it also bricked my tag (partially). All very strange. The function is part of master (bd5d481) but it is not used/triggered for now. Maybe someone is willing to contribute to testing at the risk of breaking gen3 tags? :) |
hey, just tried your modifications - yes, it modified the uid and bricked the card :) The card is detected with the new uid (on android and linux (nfc-list)). This was the card i used: I had to modify one line to get it compiled
into
|
what i found while looking at the output of the app: block 0 of original card: block 0 the app tries to write: |
Hi @Aendrew87! Thank you very much for testing and I'm sorry for you loss of a card. The behavior you're describing sound exactly the same as I experienced it. Interesting catch with the difference in writing. How did you observe it? Where you able to read block 0 after it was written? Did you emulate a card and looked you for what MCT was trying to write? The three bytes in question should be the ATQA and the SAK. The |
It seems I have one of these gen3 cards and I confirm this is one of the strangest cards I had in my hands. |
Interesting observations. Scrolling through https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/magic_cards_notes.md looks like there are special tags which allow changing between 4/7 bytes UID. Never had one of those. Since there are so many magic MIFARE Classic tags now, it's hard to keep track. |
The new MIFARE Classic special/magic cards "Gen3" should be configurable using Android. The configuration commands are just issued using the APDU structure: https://github.com/RfidResearchGroup/proxmark3/blob/master/doc/magic_cards_notes.md#mifare-classic-gen3-aka-apdu
The main goal is to implement an extra Gen3 configuration tool. A great addition would be to have writing to block 0 of Gen3 seamlessly integrated into the rest of the application flow.
A way to detect Gen3 cards is to read block 0 without authentication. If this works it should be Gen3.
The text was updated successfully, but these errors were encountered: