martinpaljak / nfc4pc Goto Github PK

Goal: when a tag is detected and reader is capable of reading the UID of the chip, but no NDEF payload (again, type 4 only currently) is detected, open a pre-defined URI with the UID of the chip appended as query parameter in small case hex.

That is:

• If the daemon is started with parameter --uid-url https://example.com/foo#bar and the UID of the chip presented to a reader is 046B477AB92980, the following URL will be triggered: https://example.com/foo?uid=046b477ab92980#bar
• This will work independently of the tag technology with most readers, meaning that even if currently NTAG NDEF values are not read, the UID is still available and would trigger the URL opening

Possible enhancements:

• Do a silent triggering with --silent-uid - only show the notification, but don't open the browser, only send a "webhook" (PROBABLY)
• Add basic/api key authentication to the request (PROBABLY)
• Add GUI to change the UID URL and silent option (MAYBE)

When using Meta-URL the URL Parameter 'url' gets encoded into URL String twice. This results in an wrong encoding

Example:
URL to encode: https://google.com
correctly encoded URL: https%3A%2F%2Fgoogle.com
Encoding from this tool: https%253A%252F%252Fgoogle.com

Maybe it is resulting from this issue: https://bz.apache.org/bugzilla/show_bug.cgi?id=39746

Workaround for me is to decode the URL twice on the receiving end.

Without checking the code out. Maybe the issue is in the class "NFC4PC" where you encode the URL on Line 153 and then add it to the URL with the method "appendUri" in that method you write that the append String will be URL encoded. That would mean that the URL gets encoded twice and would explain the behaviour.

https://github.com/cyberphone/qr-replacement

Just F.Y.I.

Seems to not happen :(

https://files.identiv.com/products/smart-card-readers/contactless/3700/uTrust_370xF_User_Manual.pdf

Seems regardless of the tag type I use (tried with Classic 1K, NTAG213 and NTAG424), I get the following error as soon as I tap it:

22:40:44:508 [ACS ACR122 0] [ERROR] NFCReader - Could not connect to or read: newPosition < 0: (-2 < 0)
java.lang.IllegalArgumentException: newPosition < 0: (-2 < 0)
at java.base/java.nio.Buffer.createPositionException(Buffer.java:341)
at java.base/java.nio.Buffer.position(Buffer.java:316)
at java.base/java.nio.ByteBuffer.position(ByteBuffer.java:1516)
at jnasmartcardio.Smartcardio$JnaCardChannel.transmitImpl(Smartcardio.java:809)
at jnasmartcardio.Smartcardio$JnaCardChannel.transmit(Smartcardio.java:690)
at apdu4j.pcsc.CardBIBO.transceive(CardBIBO.java:130)
at apdu4j.core.APDUBIBO.transmit(APDUBIBO.java:35)
at pro.javacard.nfc4pc.NDEF.getType2(NDEF.java:42)
at pro.javacard.nfc4pc.NFCReader.tryToRead(NFCReader.java:120)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
at java.base/java.lang.Thread.run(Thread.java:833)
WARNING: Could not read: newPosition < 0: (-2 < 0)

I am using a ACR-122U reader. What could be causing this?