contactless-smartcard

Why doesn't Android HCE support Mifare Classic type?

走远了吗. 提交于 2019-12-29 07:13:00
问题 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

Error “Malformed content.” in Signature Verification

爷,独闯天下 提交于 2019-12-25 18:26:21
问题 I want to verify my signature . my signature is a byte array. I use spongy castle I get error "org.spongycastle.cms.CMSException: Malformed content." this is my code: String base64 = Base64.toBase64String(signedchallenge); CMSSignedData cms = new CMSSignedData(Base64.decode(base64)); Store store = cms.getCertificates(); SignerInformationStore signers = cms.getSignerInfos(); Collection c = signers.getSigners(); I get error in line " CMSSignedData cms = new CMSSignedData(Base64.decode(base64));

Reading phantom NFC tags via javax.smartcardio

十年热恋 提交于 2019-12-24 08:39:20
问题 I have an an old NFC reader for the tikitag web service (which was later renamed touchatag, and finally abandoned around 2012). Since the website is no longer available, I could no longer find the original tikitag/touchatag drivers. After some searching, I found this NFC reader is a generic ACS ACR122U USB reader, and installed a suitable driver from here. My system is Windows 7 (64-bits). First, I tried the NFC Tools library for high-level read and write access to NFC tags. I got an error

How to read Smart Card data

二次信任 提交于 2019-12-24 07:38:22
问题 I am trying to retrieve the data from the smart card using smart card reader. I've used the software (PascProbe.exe) to obtain all the data I've could. This what I got: Card Reader: OMNIKEY CardMan 5x21-CL 0 ATR=3B8F8001804F0CA0000003060A0018000000007A (hex) Card type: PicoPass 2KS Card serial number (CSN, UID): 504B4901FBFF12E0 (hex); PACS bits (raw Wiegand) data: 000000202FA473F8 applying HID H10304 card format: Facility Code: =762 Card Number: =145916 I understand how to get CSN(UID) and

Mifare Application Directory Management?

半城伤御伤魂 提交于 2019-12-22 00:16:05
问题 [ Please only consider 1k classic cards in your answers. ] I am hoping to gain a bit of industry knowledge in the realm of RFID. Specifically, with the MIFARE MAD (Mifare application directory). I understand its architecture from reviewing the MIFARE MAD documentation published by NXP located here: http://www.nxp.com/documents/application_note/AN10787.pdf However, from this document a few questions arise. Who manages the initial MAD directory on a given card? I know that manufactures may

MIFARE card for payment with EMVco compliance

寵の児 提交于 2019-12-21 22:19:14
问题 I am working on an NFC-based payment device. I am using MIFARE DESFire EV1 chip. My question is: How to enable a full EMV compliant payment transaction with this chip hardware? I found this Visa Ring which does payment transactions. It uses NFC Ring® design of McLear & Co with NTAG IC. 回答1: How to enable a EMV payment transaction with MIFARE DESFire EV1? Simple answer: You can't. MIFARE DESFire is a proprieatry contactless smartcard system that implements a filesystem for data storage and an

Send APDU command to card through HID OMNIKEY 5427 CK

感情迁移 提交于 2019-12-21 12:57:14
问题 I'm trying to pass though APDUs command via HID OMNIKEY 5427 CK to operate MIFARE Card ie. Ultralight C card, on the Windows 10 x64 OS environment using WinSCard.dll. (I'm under NXP NDA and have full access t their documents) I tried to find information online for days now. Seem like no published document for this model except the 2pages brochure. The simple command like GetUID (FFCA000000) is OK, I can get back the actual card UID. But for 'Authentication with Card', reference document from

Parsing PDOL for GET PROCESSING OPTIONS command in EMV transaction

社会主义新天地 提交于 2019-12-19 06:57:34
问题 I am trying to build a correctly formatted GET PROCESSING OPTIONS command to be sent to a contactless EMV card. This post has been very helpful but I just need to know a little more detail. When parsing the PDOL, is it safe to assume that each tag is 2 bytes in length, followed by the size of the data expected in return? For example, the PDOL 9F66049F02069F37049F1A02 is broken into 9F66 04 , 9F02 06 , etc. each with 2 byte tags and 1 byte for the expected length of the data value. Is it safe

issue with get processing options

丶灬走出姿态 提交于 2019-12-17 20:28:46
问题 I have selected application ( A0000000032010 ) on Visa contactless card and when I issue GPO command: "80A8000002830000" I get error: 67 00 Does anyone have idea what can be causing this? 回答1: You receive that error code because you are sending an invalid GET PROCESSING OPTIONS command. In response to the application selection, you received the following PDOL: 9F38 0E (Processing Options Data Object List (PDOL)) 9F6604 (Terminal Transaction Qualifiers (TTQ)) 9F0206 (Amount, Authorized

Locking mechanism of Mifare Classic 1K

天涯浪子 提交于 2019-12-17 09:55:29
问题 The procedure of Mifare Classic 1K is Polling for tags Authenticate those tags If authentication succeded then read/write. I already completed those procedures and also read and write data from specific sectors. Command for Polling for tags is new byte[] { (byte) 0xFF, (byte) 0x00, (byte) 0x00, (byte) 0x00, (byte) 0x04, (byte) 0xD4, (byte) 0x4A, (byte) 0x01, (byte) 0x00 } Authentication command is new byte[] { (byte) 0xFF, (byte) 0x86, (byte) 0x00, (byte) 0x00, (byte) 0x05, (byte) 0x01,(byte)