Issue 271 in libnfc: SAK value problem

30 views
Skip to first unread message

lib...@googlecode.com

unread,
Mar 4, 2014, 4:04:58 AM3/4/14
to libnfc...@googlegroups.com
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium

New issue 271 by chihfeng...@gmail.com: SAK value problem
http://code.google.com/p/libnfc/issues/detail?id=271

Hi, everybody.I have a access control card.
After I duplicate data to new card at Windows 7(x64) system,it's SAK = 88.
Why original card SAK =08 ??


Original card information as follows:

nfc-list uses libnfc 1.5.1
Connected to NFC device: ACS ACR122 0 / ACR122U214 - PN532 v1.6 (0x07)
1 ISO14443A passive target(s) found:
ATQA (SENS_RES): 00 04
UID (NFCID1): 31 72 3a e3
SAK (SEL_RES): 08

Command:
nfc-mfclassic r a filename
Result:
Open filename,I find SAK =88
00000000h: 31 72 3A E3 9A 88 04 00 C0 8E 1D D3 41 90 33 12
00000010h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000020h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000030h: FF FF FF FF FF FF FF 07 80 69 00 00 00 00 00 00

Command:
nfc-mfclassic R a filename
Result:
Connected to NFC reader: ACS ACR122 0 / ACR122U214 - PN532 v1.6 (0x07)
Found MIFARE Classic card:
ATQA (SENS_RES): 00 04
UID (NFCID1): 31 72 3a e3
SAK (SEL_RES): 08
Guessing size: seems to be a 1024-byte card
Unlocking card
Sent bits: 50 00 57 cd
Sent bits: 40 (7 bits)
unlock failure!

But dump by "mfoc" program. I got
00000000h: 31 72 3A E3 9A 88 04 00 C0 8E 1D D3 41 90 33 12
00000010h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000020h: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00000030h: FF FF FF FF FF FF FF 07 80 69 FF FF FF FF FF FF

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

lib...@googlecode.com

unread,
Mar 4, 2014, 4:32:34 AM3/4/14
to libnfc...@googlegroups.com
Updates:
Status: Invalid

Comment #1 on issue 271 by yob...@gmail.com: SAK value problem
http://code.google.com/p/libnfc/issues/detail?id=271

Memory content and anticollision SAK are not as linked as you think.
libnfc is correct AFAIK.
Reply all
Reply to author
Forward
0 new messages