UID Changeable cards are used to duplicate Mifare Classic 1K access cards. Whilst generally it is best practice to use unique Mifare Classic 14443A cards for each user, there are some instances where you may wish to clone a card and have multiple cards with the same UID and data. For example access control with few users with no user having the ability to add new cards into the system. Or for access control that has a user limit which has been reached. These types of cards can be programmed with the Proxmark3.IMPORTANT: There are different types of cards that you can choose from:(Gen4 GDM ZUID) – New and interchangeable from Gen1a to Gen1a & Gen2. Once the SAK is changed and gen2 mode is enabled, you can use both gen1a & gen2 commands. Gen1a cannot be disabled on ZUID.The following shows the expected result when running “hf mf info” using a proxmark.The config can then be read via the “hf mf gdmcfg –gen1a” command.Type 1: Normal GEN1 UID Changeable Cards:All blocks (including Block 0) can be re-written multiple timesUses “backdoor” technique to change/rewrite UID.UID can be changed multiple times.Not suitable for MCT on Android (Mifare Classic Tool)Answers to the proxmark magic backdoor commands (GEN 1a): YESType 2: Special GEN2 CUID Cards:All blocks (including Block 0) can be re-written multiple timesNot easily detectable by a system with “anti-clone” featureIMPORTANT: Card will die if an invalid Block 0 is writtenUse normal commands. eg. hf mf wrbl 0 B FFFFFFFFFFFF a473f601200804006263646566676869Answers to proxmark magic backdoor commands: NOIMPORTANT:The UID of MIFARE Classic® Compatible 1K Direct Write UID Tags is comprised of two parts: the UID itself, and the BCC. The BCC is a checksum value calculated from the UID. If the BCC is incorrect, tag will be rejected by the reader.Most RFID tools, such as the Proxmark, LibNFC, MCT etc automatically calculate the BCC when the UID is modified. If you are modifying the UID by hand, it is vital that the BCC is correctly calculated.KSEC cannot provide support or refunds under any circumstances for cards that were ‘bricked’ due to incorrect UID/BCC configuration.
