-
-
Notifications
You must be signed in to change notification settings - Fork 106
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
pcsc do not work with Watchdata W5181 #121
Comments
The reader "Watchdata W5181" is listed in the "Should work but untested by me" list Some readers are not compliant with CCID on the contactless interface. It looks like your Windows trace if for the SAM interface. I see the ATR 3b7d940000574429464186938abf7515143d that corresponds to what you get on Linux for the reader "Watchdata W5181 [SAM Reader ] 02 00" |
Since the problem is with the CCID driver you should have reported the problem to https://github.com/LudovicRousseau/CCID |
Ouch, thanks. I'm not really aware this. I saw in the Windows VM all 3 interfaces shows up as ccid driver so I was thinking this should work. OTOH, I think the contact interface does not work on the Windows 7 VM either. Not sure what's the cause yet. Maybe it's because the Windows system is inside VM
Yes. Actually the reader itself contains 3 slots - contact, contactless, SAM. I don't care about the SAM slot so I did not pay much attention to the info there. I confirm there is a SAM card inside the slot (the SAM card inside don't belong to me so I do know know anything about it).
|
Oh by the way, if your conclusion from the capture is that this is really an incompatible device and no way to fix it in CCID, I don't have objections - except that we probably should remove Watchdata W5181 from the supported_readers list in such case. |
If Windows can use the contactless interface then I guess the reader is not completely useless. I added a note for https://ccid.apdu.fr/ccid/shouldwork.html#0x163C0x0A03 |
Thanks
No worries. I still have other working readers on hand.
Thanks. But that might be insufficient - in my Fedora 35, none of the interfaces work for me. I only provide the log and capture with contactless interface only because that's the only thing I get it working in Windows 7 VM without anything special. So, I would suggest to mention it as not supported right now. |
From your pcsc_scan trace I see the 3 interfaces. And you get the ATR of the SAM interface. So at least the SAM interface works. |
Actually I've tried contact interface first. But it don't work with pcsc_scan (by this I mean, pcsc_scan cannot detect any card with the contact interface). Then I tried the contact interface inside Windows VM, |
OK. So the Watchdata W5181 does not work (for you). |
Versions
smart card reader driver name and version
pcsc-lite-libs-1.9.5-1.fc35.x86_64
pcsc-lite-ccid-1.4.36-2.fc35.x86_64
pcsc-lite-1.9.5-1.fc35.x86_64
pcsc-perl-1.4.14-18.fc35.x86_64
pcsc-tools-1.5.8-1.fc35.x86_64
pcsc-lite-devel-1.9.5-1.fc35.x86_64
pcsc-lite version See above
the output of the command
/usr/sbin/pcscd --version
Platform
Fedora 35 x86_64
ccid, as shows above
Watchdata W5181, which is listed in supported_readers of CCID.
J3R200, but this has nothing to do with smart card yet.
Issue
On Fedora, pcsc_scan cannot detect the card I put on Watchdata w5181 contactless interface. And gp.jar from GlobalPlatformPro cannot detect the card either
I should be able to use the contactless interface just like how it work in Windows (without any 3rd part driver).
pcsc_scan simply cannot detect the card. And gp returns like the following.
Log
watchdata-pcscdlog.txt
I captured the USB pcap on a Windows virtual machine. The capture starts before I redirect the reader to the VM, and then the whole process of runing the following commands. Hope this can be helpful.
watchdata-pcap-windows.tar.gz
Note: I don't know if this is the right place to submit the bug or not. If not, feel free to let me know where this could be submitted.
And, the card itself works fine with other readers in my Fedora.
The text was updated successfully, but these errors were encountered: