mifare

authentication error for mifare card “6982:Security status not satisfied”

守給你的承諾、 提交于 2019-12-04 18:15:00
I know. This question asked before under same tag and same name here . But the answers are useless for me. and i opened again for real answers. 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 4 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 FF 88 00 00 60 00 how can I authenticate to this card ? The

Get mifare card serial number with WinSCard library

旧城冷巷雨未停 提交于 2019-12-04 16:25:50
I am working on an application that required reading the mifare card serial number, the language I am working with is C#. I am new to mifare reader programming, so I am sorry for asking dumb question. At first I would like to know if there is a different between Mifare UID and Mifare Serial number. I have managed to get UID with the help of WinSCard library, but I cant figure it out how to get the card serial number which should be 10 digit numbers. I do appreciate if you could point me to the right direction. Thanks in advance for the help. Regards C# signature of SCardTransmit method

Reading the tag UID of Mifare classic card

无人久伴 提交于 2019-12-04 16:08:27
I am creating an app for NFC where my first objective is to get the tag uid from the mifare tag. When i press the tag button my activvity goes to second activity where i should be getting the tagID. I am getting error of resource lookup. I know i am doing some major mistakes but could not find it. Request you to please help. This is my Meanifest file <?xml version="1.0" encoding="utf-8"?> <manifest xmlns:android="http://schemas.android.com/apk/res/android" package="com.chetan.nfc" android:versionCode="1" android:versionName="1.0"> <uses-sdk android:minSdkVersion="10"></uses-sdk> <uses-feature

How to authenticate NTAG213 with ACR122U

久未见 提交于 2019-12-04 13:19:28
I'm using an ACR122U reader with an NTAG213 card. The card is password (reading and writing) protected with the password 52 84 00 08 . What are the APDU commands I should run to authenticate the card and also to read pages 30 and 31 of it once authenticated? I know with the MiFare 1k I could load the password and authenticate a sector, but I'm not sure how authentication works with the NTAG213 cards with the ACR122U readers. With the ACR122U you would need to send direct commands to the PN532 NFC controller chip inside the reader in order to exchange such low-level commands. For instance, you

Authenticating Ultralight EV1 with PC/SC reader

∥☆過路亽.° 提交于 2019-12-04 12:00:46
I have a problem trying to authenticate an Ultralight EV1 card using a PC/SC reader (specifically an ACR1222L) in Java. I'm able to write and read on an unprotected tag using the corresponding APDUs for ISO 14443-3 tags. However, I can't find a way to run the PWD_AUTH command since it is not part of the 14443-3 standard (or any native command for that matter). Is it possible to run this command (or any native command for that matter)? I have tried sending the following APDU {e0 00 00 24 07 1b ff ff ff ff 63 00} where 1b is the native command, ff ff ff ff is the password and 63 00 is the CRC_A

NFC tag information

时间秒杀一切 提交于 2019-12-04 07:12:05
问题 I have a question, it is possible know the code source of explain th type of tag NFC that I read? If is a Mifare 1k or Ntag203 or another else? protected void onNewIntent(Intent intent){ String[] techList = tag.getTechList(); for(String tech:techList) { //I think must insert here the code } } 回答1: Fingerprinting of NFC tags is not quite easy. Most tags don't just tell you "I am XY". Moreover, for certain tag technologies there exist many different tags from several different manufacturers. E

MIFARE Classic: How to find to good Access Byte value

隐身守侯 提交于 2019-12-04 06:17:43
问题 My aim is to have only KEY A authentification and disable Key B (used space to store data). I read these documentations: http://www.nxp.com/documents/data_sheet/MF1S503x.pdf http://dangerousthings.com/wp-content/uploads/2012/08/NFC-Access-Control-for-Mifare-S50.pdf I understand how to calculate the hexadecimal values of these three bytes. But I don't understand how to choose the good data block and access byte rules : Data Block rule Here, I want to keep only key A (R & Write data) and

Reading correct data from NFC wrist band with NXP Mifare Ultralight in C

为君一笑 提交于 2019-12-04 02:04:10
问题 I am very new to NFC devices reading but I have managed to implement in my own project using the code from nfc-mfultralight.c (libnfc). What I don't understand is that when I read the data from a MIFARE Ultralight band, I get lots of garbage. For example, I have the number 255555574558888 in the tag (I used an Android device to write this number to the tag). Now when I run: nfc-mfultralight r /home/user/dump I get this d▒r▒!▒ H▒▒U255555574558888▒-67644-67546-2346 This is from the examples of

NFC APDU READ command performance tuning

旧巷老猫 提交于 2019-12-03 20:27:54
I am reading several hundred bytes from a DESFire card using APDU commands. The data application is authenticated, and the response MAC'ed. I submit a series of READ_DATA commands (0xBD), each retrieving 54 bytes+MAC while increasing read offset for each command. Will this operation go much quicker if I use a long READ with ADDITIONAL_FRAME (AF) instead of many sequential reads? I understand that a simple AF is 1 byte vs 8 bytes for a full READ DATA command, thus reducing the number of bytes transferred by ~10%. But will use of AF give additional performance benefits, for example because of

Writing to a Mifare tag with Android NFC?

那年仲夏 提交于 2019-12-03 16:48:18
I'm trying to write a simple "Hello World" string to the first block of sector 0 on a Mifare 1K tag. The tag is brand new with default configuration. The sector trailer (block 3), when read, is: 00 00 00 00 00 00 00 00 ff 07 80 69 ff ff ff ff ff ff ff ff . Hence, the access conditions is ff 07 80 69 , meaning I can read and write on each block with key A. Still, I can't manage to write anything on the tag. Here's my code: try { mfc.connect(); boolean auth = false; auth = mfc.authenticateSectorWithKeyA(0,MifareClassic.KEY_DEFAULT); if (auth) { String text = "Hello, World!"; byte[] value = text