LudovicRousseau / pyscard Public
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
empty response -> crash on empty sw1 #18
Comments
result of pcsc_scan in case it helps
|
What happens with gscriptor if you send the APDU "A0 A4 00 00 02 7F 10"? |
not much apparently… Thanks for fast answer :) edit: this made me understand (quite new to rfid, sorry) that what i want mainly, getting tag ID was simpler than i though, i was sending SELECT + FFCA000000 for that, when i only needed the latter part, and in this case, answer is immediate, so for now i'm settled, but if think there is a real bug to solve in pyscard for the DF_TELECOM (if it should work with any tag/reader), i can help debugging this further, it might be useful in the future. |
Can you generate pcscd logs as described in https://pcsclite.alioth.debian.org/ccid.html#support and send the problematic APDU A0 A4 00 00 02 7F 10 using gscriptor ? |
|
I've read a bit more about |
Please attach a complete pcscd log. |
Sorry, i though keeping only the communication part would be more useful
|
The reader firmware is bogus. The reader should report an error in bStatus so that the driver knows something failed and returned an error so that the upper layers, in this case pyscard, do not try to parse the empty result. |
Can you follow https://pcsclite.alioth.debian.org/ccid.html#CCID_compliant please? Your reader is already in the "unsupported" list but I want to know what firmware version you are using |
Sure, here it is, thanks for looking into it and explaining, i've been told this reader was quite common, so though it would have good support, but maybe it's limited by a bad firmware, support is good enough for what i want for now anyway :), i guess i should have started with the support list.
|
You are using a "recent" firmware |
looks a lot like LudovicRousseau/pyscard-contrib#2
trying any example with transmit (here http://pyscard.sourceforge.net/pyscard-framework.html#selecting-the-df-telecom-of-a-card), with any tag, i get:
when i get down to it with pudb,
response
is just[]
in there, so of course it's out of range. First tried with python-pysdcard from ubuntu repository, then i built/installed from source (this repository). I'm having a look intoscard.i
, and SCardTransmit, but i have no experience with swig, so i'm not positive i'll find the cause on my own, so any idea welcome :). If i startgscriptor
and run a script likeFFCA000000
, i do get an answer, so i guess pcscd is working correctly.The text was updated successfully, but these errors were encountered: