SAK value problem

[GoogleCodeExporter]

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

Original issue reported on code.google.com by chihfeng...@gmail.com on 4 Mar 2014 at 9:04

[GoogleCodeExporter]

Memory content and anticollision SAK are not as linked as you think.
libnfc is correct AFAIK.

Original comment by yob...@gmail.com on 4 Mar 2014 at 9:32

• Changed state: Invalid