-
Notifications
You must be signed in to change notification settings - Fork 44
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
Unknown error in get_status() (error code 0x6c0c) #8
Comments
Card Type: THD-89 (Proprietary JCOS) I noticed that Satochip v0.9 applet (SatoChip-3.0.4.cap) seems to be working properly. Here's the Trace Log:
The commonality in the working applet is that it returns SW 0x9C04 when INS_GET_STATUS is enquired on a blank card. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Electrum Satochip Version: electrum-satochip-v4.1.5
SatopchipApplet Version: SatoChip-0.12-05.cap
Card Type: THD-89 (Proprietary JCOS)
Issue:
Getting 'Failed to create a client for this device. Make sure it is in the correct state.' error message when trying to create a new hardware wallet with Satochip applet and Electrum client.
Trace Log:
Comments:
It seems that the GET_STATUS instruction is returning SW 0x6C0C. I am wondering if some card types are sensitive to Le being used and the current CardConnector does not issue a Le in the APDU.
A suggestion is to issue Le with 255 for all APDU commands which may help to accommodate more types of cards to run Electrum-Satochip by default.
Here's a GP.EXE execution with APDU with Le enabled:
Here's a GP.EXE execution with APDU with Le not enabled:
It seems the pysatochip.CardConnector getting SW 0x6C0C is abit odd since without Le, GP.EXE returns SW 0x9C11 and pysatochip.CardConnector on the other hand returns 0x6C0C.
There seems to be some differences in how GP.EXE and pysatochip.CardConnector calls the smartcards ?
The text was updated successfully, but these errors were encountered: