search

timmerk / nfc-tools

Automatically exported from code.google.com/p/nfc-tools
0 stars 0 forks source link

lsnfc and ISO14443A tags with randomized UID #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
Each time nfc_initiator_select_tag gets called, it return a new instance of 
the same card. This causes lsnfc to enter a loop.

What steps will reproduce the problem?
1. place the card on the reader
2. run lsnfc

Output:

$ nfcutils/src/lsnfc 
device = ACS ACR122U PICC Interface 00 00 / ACR122U206 - PN532 v1.4 (0x07)      

  ISO14443A: Unknown tag type: ATQA (SENS_RES): 0004, UID (NFCID3): 
0870e8e0, SAK (SEL_RES): 20, ATS (ATR): 0857800201100009                   
  ISO14443A: Unknown tag type: ATQA (SENS_RES): 0004, UID (NFCID3): 
08ba4071, SAK (SEL_RES): 20, ATS (ATR): 0857800201100009                   
  ISO14443A: Unknown tag type: ATQA (SENS_RES): 0004, UID (NFCID3): 
08ddfaaa, SAK (SEL_RES): 20, ATS (ATR): 0857800201100009                   
  ISO14443A: Unknown tag type: ATQA (SENS_RES): 0004, UID (NFCID3): 
08edb506, SAK (SEL_RES): 20, ATS (ATR): 0857800201100009                   
  ISO14443A: Unknown tag type: ATQA (SENS_RES): 0004, UID (NFCID3): 
081c969f, SAK (SEL_RES): 20, ATS (ATR): 0857800201100009
^C           

AFAIK, libfreefare uses the same mechanism in the get_tags function which 
means the function will not return with such cards.

Original issue reported on code.google.com by newhano...@gmail.com on 28 Feb 2010 at 5:19

GoogleCodeExporter commented 9 years ago 
Hello,
Thanks for report.
I don't have this kind of card and don't think Romain has one neither, so it 
will be
difficult to test your case but do you know how to handle your issue, any hint 
or
idea ?

Original comment by romu...@libnfc.org on 4 Mar 2010 at 3:59

GoogleCodeExporter commented 9 years ago

Original comment by romu...@libnfc.org on 4 Mar 2010 at 3:59

GoogleCodeExporter commented 9 years ago 
Hi Conty, I have a few cards issue by T-Money, all of them have uid randomized, 
the 
card i used in the example was one of them. Also Mifare DESFire EV1 can be 
configured 
to operate in the uid-randomized mode. This weekend i will try to dig futher 
and try 
to find a solution for the issue.

Original comment by newhano...@gmail.com on 5 Mar 2010 at 7:01

GoogleCodeExporter commented 9 years ago

Original comment by romu...@libnfc.org on 9 Mar 2010 at 4:09

GoogleCodeExporter commented 9 years ago 
newhanoian, did you made some improvement regarding this issue ?

Original comment by romu...@libnfc.org on 27 Apr 2010 at 2:48

GoogleCodeExporter commented 9 years ago 
I can't reproduce the problem with my passport:

romain@marvin ~/Projects/nfc-tools/nfcutils % ./src/lsnfc         
device = ACS ACR 38U-CCID 01 00 / ACR122U102 - PN532 v1.4 (0x07)
NXP MIFARE Plus 1k (UID=08203d95)
1 tag(s) on device.
romain@marvin ~/Projects/nfc-tools/nfcutils % ./src/lsnfc         
device = ACS ACR 38U-CCID 01 00 / ACR122U102 - PN532 v1.4 (0x07)
NXP MIFARE Plus 1k (UID=0818268b)
1 tag(s) on device.
romain@marvin ~/Projects/nfc-tools/nfcutils % ./src/lsnfc         
device = ACS ACR 38U-CCID 01 00 / ACR122U102 - PN532 v1.4 (0x07)
NXP MIFARE Plus 1k (UID=088afce7)
1 tag(s) on device.

While the target type is wrong, you can see that the UID changed each time and 
that there is no looping.  Please reopen if your problem is still presant and 
you have more instructions on how to reproduce it.

Original comment by romain.t...@gmail.com on 4 Sep 2010 at 11:33