contactless-smartcard

问题 I would like to know if there is a way of changing the historical bytes automatically as you power your smartcard, in order to have different response if on contact or contactless. In Javacard you can use setATRHistBytes , and also call it depending on the access interface. But the changes would be reflected on next power up of the card. I want to set them intermediately. TA 回答1: Actually the contact-less interface has no attribute named ATR. Because ATR is for contact interface only. The

问题 I'm trying to communicate between a Samsung Galaxy S3 and a smartcard that supports NfcA and IsoDep (Mifare DESFire EV1). To do this, I enabled forgeground dispatch and started a task when a tag is discovered. The code in the task looks like this: IsoDep isoDep = IsoDep.get(tag); byte[] selectCommand = { (byte)0x00, // CLA (byte)0xA4, // INS (byte)0x04, // P1 (byte)0x00, // P2 (byte)0x0A, // LC (byte)0x01,(byte)0x02,(byte)0x03,(byte)0x04,(byte)0x05,(byte)0x06,(byte)0x07,(byte)0x08,(byte)0x09,

问题 I'm trying a PoC where in I'm trying to authenticate a user based on their HID card value. I don't have any specific API for the reader. The reader outputs plain number of the card by keyboard emulation. The PoC permits a user to authenticate through username/password or through HID proxy card. To simplify things I wanted to use a hidden TextBox to which the value from HID is read and a corresponding webservice is triggered from TextChanged event. I was unable to do so. Can anyone advice how

问题 Now that Android supports Card Emulation on the Nexus 5 with Android 4.4, is it likely that some apps may become available that allow me to effectively duplicate a smartcard (e.g. Smart Card that opens doors in my office) and use my phone in their place? Would be pretty handy. Cheers! 回答1: No, this is not likely. Typically, copying/cloning arbitary cards using Android HCE is not possible. Many access control systems use the card ID (UID) to identify the card (or even to make an access control

问题 I want to send an APDU with a length of 1699 bytes via NFC (class IsoDep ) to a Java Card smartcard. I get the error java.io.IOException: Transceive length exceeds supported maximum My phone is a Samsung Galaxy S7. I use extended-length in my applet on the card. I have verified that the card supports extended length. I tested this via pyapdutool by sending an APDU with 4000 bytes to the card. I found that when I write this code, the result is false : final Tag t = (Tag) tag; myTag = IsoDep

问题 This question is specifically about MIFARE Ultralight C/EV1, or MIFARE DESFire EV1, or even NTAG cards. I want to implement a system of tokens, so that each time a normal user reads one of those cards they'll get one available token; that token will "pop out" from the NFC card they're reading. In other words, every time that NFC chip is read, it will issue a different usable token from the card's storage. Is this possible to implement? 回答1: Common non-programmable smart cards usually provide

问题 Which of MIFARE cards support a single block that can be programmed to require a password for writing, but is available to everyone for reading its data? And is such standard eligible on all platforms, specifically iOS. Can it use its NFC chip for doing both mentioned operations on such card? 回答1: There are quite a few products in the MIFARE product family 1 that would allow write-protecting information with an authentication key/password (while at the same time having that information freely

问题 Is it possible using ATR to determine whether I have ISO14443A or ISO14443B type card? If yes, how? 回答1: As mictter correctly explained, a real AT R only exists for ISO 7816 contact cards. I can follow the argumentation that the ISO 14443 equivalent could be the ATQA/ATQB as this is the first answer you get from tags after activation, though I would rather say that the equvalent of the ATR is a combination of ATQA + SAK + ATS (for Type A) and a combination of ATQB + Answer to ATTRIB (for Type

问题 When reading a MIFARE card with Android and converting the data to UTF-8 I get strange characters like �. I'm trying to build an application that can read some kind of ID card we're using. The problem now is that I get weird characters between words and some words are split between blocks so how can I safely get a word I'm looking for? For instance my readings is something like this: 43224���19032019�� at block 2 sektor 2 bindex :8 and with splitting where rest of the number starting with 19

问题 Mifare Classic is the most used cards and I can't understand why HCE (Host-based Card Emulation) only supports ISO 14443-4, but not Mifare Classic type. Because NXP stops them from using their proprietary protocols and algorithms? Or because they didn’t implement Mifare Classic in Android OS level? Any comments will be very appreciated. 回答1: Short answer: Because Google decided to support only ISO/IEC 7816-4 over ISO-DEP (ISO/IEC 14443-4). Speculations on why they decided that way: First of