contactless-smartcard

问题 The SDK provided along with NFC reader does not work and we are not able to write data / tag using the Tools available with SDK. The main issue is that the data written using another tool does not remain in the device for permanently. When tag is scanned using Android device, reader gets clear and we have to to write data again. I have checked and tried instructions from https://github.com/fkooman/nfcip-java/blob/master/nfcip-java/doc/ACR122_PN53x.txt but it does not work. So, we need help to

问题 I had a previous question regarding a way to access a proxy card from within a web page when using Chrome. I'm now attempting to instead use a vb.Net application with an embedded CefSharp object. I have the code I need to access the proxy card (thanks to Smart Card API), but I need an easy way to indicate that this is even an option. My thought is to: Put an otherwise empty element on the web page (such as <div id='smartcard' /> ) Inside Visual Basic, monitor the contents of the page for this

问题 How to identify different types of MIFARE Ultralight tags? In document AN10834 Ultralight and Ultralight C differ by the answer from "Auth". What is this "Auth"? There is no description of this function in the datasheets to the chips. I noticed that Ultralight C and EV1 support GET_VERSION (60h), I sent this request to EV1 card, it does not return anything to me. 回答1: In order to distinguish MIFARE Ultralight, Ultralight C, Ultralight EV1, and NTAG tags, you would first send a GET_VERSION

问题 I'm using Galaxy A5, Android 5.0.2, SDK 21 with Android Studio 1.1.0 Android as PCD, and Mifare DESFire as PICC. Native DESFire APDU Framing didn't work, but ISO 7816-4 worked. Example: MIFARE DESFire SelectApplication with AID equal to 000000h (PICC level) Command: 90 5a 00 00 03 00 00 00 00 . Expected response: 91 00 . Currently the response is 68 00 . Document reference: AN11004.pdf (page 33) void SelectApp() { _isoDep.connect(); byte[] reqSelectApp = new byte[]{(byte) 0x90, (byte) 0x5A,

问题 The AID of my app is F239856324897348 and I have constructed a SelectAID APDU for it. Now how do I actually send it to the receiving Android device which is using host card emulation. I have a created my HCE service to respond with a response APDU as in this thread: How to define an APDU for STORE DATA for Host Card Emulation? public static byte[] SelectAID = new byte[]{ (byte) 0xF2, (byte) 0x39, (byte) 0x85, (byte) 0x63, (byte) 0x24, (byte) 0x89, (byte) 0x73, (byte) 0x48}; private void

问题 I try to figure out what kind of encryption the EMV standardization recommends for transferring payment information via NFC. I browsed through the specification, but I can't find any hint about this topic. I know though that the card manufacturer provides some encryption technology on their card itself, which has partly been compromised. Does someone know, if its encrypted at all (I hope so) and if so, with which technology? 回答1: The communication between the card and the contactless reader

问题 I would like to write a Java Card applet that responds to an NFC reader as if it was a regular MIFARE Ultralight or NTAG NFC tag. I am aware the MIFARE protocol is proprietary and may be a little more difficult but surely I should be able to achieve emulation of the NTAG protocol. If I match the NTAG specification and respond to the correct APDUs then I can surely emulate an NTAG? Update to original question I think I asked my original question incorrectly. I'm not looking to emulate a

问题 I am aware of this post :- Locking mechanism of Mifare Classic 1K However, it is really not clear - how a value like FF 07 80 FF is calculated in this string: D3 F7 D3 F7 D3 F7 FF 07 80 FF 00 00 00 00 00 00 This means that the blocks can be read with key A and written with Key B but does not allow inc/dec. How should the access bits look like if I have to support increment and decrement operations. I understand that C1, C2 and C3 must be 1,1,0 how does this reflect to the byte 6, 7 and 8. Any

问题 I am developing an Android app which has function to read data from a smart card. By default, NFC Controllers support APDU command with maximum transceive length is 261 bytes in single command. Because of large data need to be read on the card, the speed of reading is very slow. Are there any Android phones which support extended APDUs allow to send more than 261 bytes in single APDU ? Or are there any ways to modify the maximum transceive length by calling Android API to allow to do that? I

问题 I'm new to this field, I got a Nexus S ( CyanogenMod11 = Android Kitkat 4.4.2) And I need to use HCE (Host-Based Card Emulation) mode in order to emulate a contactless card. Any guidance on the steps and the tips I need to follow in order to accomplish this? ( - Do I need to program the simulated Secure Element? put it on cloud? ) P.S: I have to use the new Reader Mode also, because my app is going to be read by another Android NfC-enabled phone and not by an NFC reader. Thank you. 回答1: