contactless-smartcard

问题 Using a Nexus 4 and the latest Android API level 18 to communicate with a Mifare DESFire EV1 AES tag is giving me a headache. Following the NXP native protocol in order to write and read this type of tag, these steps must be followed: Select application Authenticate Write or Read To do it so, I use Android's IsoDep class which provides access to ISO 14443-4 properties and I/O operations. The very weird thing about it is that once I send the select application native command I get an

问题 I have some issues with the GET PROCESSING OPTIONS (GPO) command for a VISA card. Following is my response to the SELECT command for the VISA application: 6F408407A0000000031010A535500A564953412044454249549F380C9F66049F02069F37049F1A025F2D02656EBF0C1242034761735F550255539F5A0511084008409000 I extracted the following PDOL from this: 9F66049F02069F37049F1A02 I'm not sure about tag 9F66 . My GPO command then looks like this: 80a800000100000001000000001000823DDE7A12400 But I get a parser error as

问题 I am making an app using NFC tags and I have to prevent the NFC tag from cloning. I have seen many other NFC tags which when tried to be cloned, shows a pop up message "Cloning is restricted, tag is secured by secret key", I want the same security for my NFC tag. 回答1: That depends on what type of tag you use and what level of protection against cloning you want. NFC tags (as defined by the NFC Forum) have no protection against cloning. Such tags are intended as containers for freely readable