mifare

问题 I would like to authenticate with a desfire card in native mode. Here are my current steps: I select the master application (AID = 0×00 0×00 0×00) I receive the response (a "challenge", randB) from the card Then, in the second Step, I generate a response (randA); I concatenate the 8 bytes rand A with the 8 bytes decrypted and rotated rand B I encrypt it, sending it back to the card. I receive a 91 ae answer, and I don't know why. Here is the sequence of messages: to card: 90 0A 00 00 01 00 00

问题 Closed. This question is off-topic. It is not currently accepting answers. Want to improve this question? Update the question so it's on-topic for Stack Overflow. Closed 5 years ago . Any tutorial for how to write on Mifare Ultralight tags ? I have been searching for a while 回答1: MifareUltraLight tags it contains 16 page and each page contains 4 bytes. Its first 4 page contains manufacturer info , OTP and locking bytes. After getting The Tag you can get MifareUltralight class using 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,

问题 I'm trying to set a password on my empty NTAG213 tags, but when I get to writing the PACK and PWD my app just crashes, with no exception thrown. I did get my app far enough to write valid NDEF messages and read those, it seems I can also write to other configuration pages(2Ah and 29h for configurating the password protection). When I get to writing PACK though, my app crashes but doesn't throw the IOException I would expect from MifareUltralight.transceive(byte[] data). Here is the souce code

问题 I have some Mifare Ultralight C tags for testing authentication. The first time I read it with the app NXP TagInfo, I could see the following info: (...) Page 04 - Page 27: FULL OF 0s **(empty tag)** Page 28: 00 00 -- -- Page 29: 00 00 -- -- Page 2A: 30 -- -- -- Page 2B: 00 -- -- -- Page 2C: 42 52 45 41 PAGE 2D: 4B 4D 45 49 PAGE 2E: 46 59 4F 55 PAGE 2F: 43 41 4E 21 The page 2C - 2F means that it had the default key "BREAKMEIFYOUCAN!" ( 425245414b4d454946594f5543414e21 ). Then I ran my Android

问题 I am trying to create and write an NDEF message to an NFC tag in a Windows Form Application (written in C#) using an ACR122U NFC reader. I have created raw bytes of the NDEF message using Andreas Jakl's NDEF library. This is the C# code: var spRecord = new NdefTextRecord { Text = "1", LanguageCode = "en" }; var msg = new NdefMessage { spRecord }; string hex = BitConverter.ToString(msg.ToByteArray()); resultBox.Text = hex.Replace('-',' '); The output I get is D1 01 04 54 02 65 6E 31

问题 I have pc/sc reader and Contactless card(mifare card), I can connect to the card and also I execute getdate command successfully, but when I want to authenticate I see this error "6982:Security status not satisfied" I've tried these 3 different commands for authentication but I get the same error for all of them. FF 88 00 00 06 FF FF FF FF FF FF FF 88 00 00 60 12 FF 88 00 00 05 01 00 12 60 00 how can I fix this error?what is my mistake? 回答1: I've find the answer ,I used this command and it

问题 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 working on an app that scans just the UID of MIFARE Classic cards to facilitate attendance registration. I have got it working. However, every time I scan a card on my Galaxy S4, I get a toast stating "NFC tag type not supported". I want to either block or hide that message while the app is open. I noticed there was one other question asking for the same thing on a Galaxy S6 but it was down-voted once and then ignored. I found this conversation on the Samsung Developers forum, however, I