-
Notifications
You must be signed in to change notification settings - Fork 466
Description
Hi,
I have this NFC reader:
https://www.akasa.co.uk/update.php?tpl=product/product.detail.tpl&model=AK-CR-15BK
It identifies itself as Alcor Link AK9567 [Contactless Card Reader] 01 00.
However, when I try to scan a NTAG216, the ATQA shows 00 00.
$ LIBNFC_LOG_LEVEL=3 LIBNFC_DEVICE='pcsc:Alcor Link AK9567 [Contactless Card Reader] 01 00' nfc-list -v
[...]
NFC device: user defined device opened
debug libnfc.general set_property_bool NP_INFINITE_SELECT False
debug libnfc.driver.pcsc TX: ff ca 00 00 00
debug libnfc.driver.pcsc RX: 04 74 48 22 a6 14 90 90 00
debug libnfc.driver.pcsc TX: ff ca 00 00 00
debug libnfc.driver.pcsc RX: 04 74 48 22 a6 14 90 90 00
1 ISO14443A passive target(s) found:
ISO/IEC 14443A (106 kbps) target:
ATQA (SENS_RES): 00 00
* UID size: single
* bit frame anticollision not supported
UID (NFCID1): 04 74 48 22 a6 14 90
SAK (SEL_RES): 20
* Compliant with ISO/IEC 14443-4
* Not compliant with ISO/IEC 18092
ATS: 75 77 81 02 80 4f 0c a0 00 00 03 06 03 00 03 00 00 00 00
* Max Frame Size accepted by PICC: 64 bytes
* Bit Rate Capability:
* PICC to PCD, DS=2, bitrate 212 kbits/s supported
* PICC to PCD, DS=4, bitrate 424 kbits/s supported
* PICC to PCD, DS=8, bitrate 847 kbits/s supported
* PCD to PICC, DR=2, bitrate 212 kbits/s supported
* PCD to PICC, DR=4, bitrate 424 kbits/s supported
* PCD to PICC, DR=8, bitrate 847 kbits/s supported
* Frame Waiting Time: 77.33 ms
* Start-up Frame Guard Time: 0.6041 ms
* Node Address not supported
* Card IDentifier supported
* Historical bytes Tk: 80 4f 0c a0 00 00 03 06 03 00 03 00 00 00 00
* Tk after 0x80 consist of optional consecutive COMPACT-TLV data objects;
the last data object may carry a status indicator of one, two or three bytes.
See ISO/IEC 7816-4 8.1.1.3 for more info
Fingerprinting based on MIFARE type Identification Procedure:
Other possible matches based on ATQA & SAK values:
* Unknown card, sorry
[...]I have read the ATQA is not transmitted via PC/SC so it is reader-dependent if those values can be retrieved.
Which is unfortunate because now when I try to read the memory, the command fails:
$ LIBNFC_DEVICE='pcsc:Alcor Link AK9567 [Contactless Card Reader] 01 00' nfc-mfultralight r dump
NFC device: user defined device opened
1 ISO14443A passive target(s) found:
04744822a61490
nfc-mfultralight: ERROR: tag is not a MIFARE Ultralight cardI have found the error message ERROR: tag is not a MIFARE Ultralight card in the source here:
https://github.com/nfc-tools/libnfc/blob/libnfc-1.8.0/utils/nfc-mfultralight.c#L634
And it checks the second byte of ATQA is 0x44.
So my question is:
Can I read the ATQA somehow with this reader?
And if not, can I still read my tag or fake the ATQA? I would like to tell the CLI command I am using a NTAG216.