Skip to content
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

Broken reader, C3PO LTC31 #201

Closed
ghost opened this issue Dec 31, 2013 · 6 comments
Closed

Broken reader, C3PO LTC31 #201

ghost opened this issue Dec 31, 2013 · 6 comments

Comments

@ghost
Copy link

ghost commented Dec 31, 2013

This reader doesn't have a pinpad. Could it be added to the broken list?

--- reader-pcsc.c.orig  2013-12-31 19:26:55.000000000 +0100
+++ reader-pcsc.c   2013-12-31 19:30:37.000000000 +0100
@@ -819,7 +819,10 @@
    PCSC_TLV_STRUCTURE *pcsc_tlv;
    LONG rv;
    const char *log_disabled = "but it's disabled in configuration file";
-   const char *broken_readers[] = {"HP USB Smart Card Keyboard"};
+   const char *broken_readers[] = {
+       "C3PO LTC31 v2",
+       "HP USB Smart Card Keyboard"
+   };

    SC_FUNC_CALLED(ctx, SC_LOG_DEBUG_NORMAL);

@ghost
Copy link
Author

ghost commented Dec 31, 2013

File is src/libopensc/reader-pcsc.c

@martinpaljak
Copy link
Member

But does it report a pinpad ? If so, then it is broken indeed. But the BigMatrix(tm) does not show that the reader should have a pinpad in the first place. Thus it does not belong to this list.

@ghost
Copy link
Author

ghost commented Jan 2, 2014

When the user runs
lsusb -v | grep bPINSupport

it reports
bPINSupport 3 verification modification

He has also pointed me to a Spanish guide
http:https://fpkanarias.blogspot.com.es/2013/03/kubuntu-instalar-dni-electronico.html
Step 18 shows an enable_pinpad issue.

@martinpaljak
Copy link
Member

I would first go through with http:https://pcsclite.alioth.debian.org/ccid.html#CCID_compliant

In general, I think that working/debugging a reader for what a reader.txt file is not present in the BigMatrix is not a good idea.

@LudovicRousseau
Copy link
Member

As Javier wrote me in a private email the reader firmware can be upgraded using https://www.c3po.es/wp-content/uploads/2013/03/actualizador_firmware.zip
That is the best thing to do.

@ghost
Copy link
Author

ghost commented Jan 3, 2014

Then this issue should be closed.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants