pcsc-tools | Some tools to be used with smart cards and PC/SC | Video Game library

by LudovicRousseau Perl Version: 1.6.0 License: GPL-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | pcsc-tools Summary

pcsc-tools is a Perl library typically used in Gaming, Video Game, Nodejs applications. pcsc-tools has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. You can download it from GitHub.

Some tools to be used with smart cards and PC/SC

Support

Quality

Security

License

Reuse

Support

pcsc-tools has a low active ecosystem.

It has 134 star(s) with 54 fork(s). There are 16 watchers for this library.

It had no major release in the last 12 months.

There are 2 open issues and 37 have been closed. On average issues are closed in 16 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of pcsc-tools is 1.6.0

Quality

pcsc-tools has 0 bugs and 0 code smells.

Security

pcsc-tools has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

pcsc-tools code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

pcsc-tools is licensed under the GPL-2.0 License. This license is Strong Copyleft.

Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.

Reuse

pcsc-tools releases are available to install and integrate.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of pcsc-tools

Get all kandi verified functions for this library.

pcsc-tools Key Features

No Key Features are available at this moment for pcsc-tools.

pcsc-tools Examples and Code Snippets

No Code Snippets are available at this moment for pcsc-tools.

Community Discussions

Trending Discussions on pcsc-tools

"Time Out, the target has not answered" from ACR122U reader with Jewel/Topaz512 NFC tags

QUESTION

"Time Out, the target has not answered" from ACR122U reader with Jewel/Topaz512 NFC tags

Asked 2020-Apr-22 at 15:33

I am building a Windows/Java program (using javax.smartcardio) to communicate with Jewel/Topaz512 tags (from Innovision/Broadcom) using an ACR122U device (with a PN532 NFC Controller chip inside).

I implemented the Topaz512 protocol (from this data sheet) but only half of my commands are working.

Some commands that work: RID, RALL, READ, WRITE-NE, RSEG
Some commands that don't work: WRITE-E, READ8, WRITE-E8, WRITE-NE8

Example with the WRITE-NO-ERASE command

For instance, here is what I get when I send a WRITE-NO-ERASE command:

Command: FF:00:00:00:0C:D4:40:01:1A:7F:42:38:01:9A:00:17:E8

Where:

D4:40:01 is the InDataExchange command,
1A:7F:42 is the WRITE-NO-ERASE command (value: 0x42, block 0x0F, byte 7),
38:01:9A:00 is the 4-bytes tag UID,
17:E8 is the CRC.

Response: D5:41:00:42:90:00

Here the response is correct: 0x42. The status byte (0x00) informs that everything went well.

Example with the WRITE-WITH-ERASE command

And here is what I get when I send a WRITE-WITH-ERASE command:

Command: FF:00:00:00:0C:D4:40:01:53:7F:42:38:01:9A:00:28:6E

Where:

D4:40:01 is the InDataExchange command,
53:7F:42 is the WRITE-WITH-ERASE command (value: 0x42, block 0x0F, byte 7),
38:01:9A:00 is the 4-bytes tag UID,
28:6E is the CRC.

Response: D5:41:01:90:00

Here, the status byte (0x01) informs of a timeout detected by the PN532. (From the PN532 documentation (p67): "Time Out, the target has not answered - 0x01")

Also when I remove the PN532 timeouts (with FF:00:00:00:06:D4:32:02:00:00:00) non-working commands do not respond D5:41:01:90:00, but wait longer, then I get no response.

Edit 2020-04-20

I just tried to execute the commands using gscriptor (from the pcsc-tools suite) and I got the same behavior. Here are my results:

The script:

...

ANSWER

Answered 2020-Apr-22 at 15:33

Some time ago I looked into this in detail and concluded that the PN532 NFC controller chip from NXP has an issue with its firmware that prevents it from successfully transceiving some commands with NFC Forum Type 1 tags (Topaz/Jewel brands). The ACR122U is based on this chip as noted.

When I tried to write 8 byte blocks at a time using the WRITE-E8 (0x54) command, the response received is 0x01, a timeout waiting for the tag to respond.

Things I tried that don't work:

Including the UID echo in the InDataExchange, I even played with the endianness of the UID echo and still the same result.

Using the inCommunicateThru command rather than InDataExchange and calculating the CRC1 and CRC2 values at the application level (same results)

The final conclusion I reached is:

The PN532 cannot write to pages 0x10 and greater on a Type 1 tag which makes it impossible to write to the full range of memory on popular models such as the Topaz 512.

Recommendation:

This issue was relevant in 2012 when the Topaz 512 was a great low cost yet high memory NFC tag. Now that there's the NAG215 and NTAG216 models, I recommend using those models that have high memory and universal compatibility with NFC readers.

Source https://stackoverflow.com/questions/61275660

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install pcsc-tools

You can download it from GitHub.

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: