-
Notifications
You must be signed in to change notification settings - Fork 20
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
Current sha2 branch lost the ability to RSA-sign #22
Comments
Note "user_consent" The card enforces this and policies of the card issuer want user to enter PIN again, so OpenSC Is there a missing sc_unlock? What does a trace with the previous code show about "user_consent" and does tokend prompt foe the PIN for each signature? On 12/2/2015 9:36 PM, Mouse wrote:
Douglas E. Engert DEEngert@gmail.com |
On Dec 3, 2015, at 7:19 , Doug Engert notifications@github.com wrote:
Yes I understand.
I don’t know.
I don’t know. This splitting appears to have caused much more damage than one would think possible from looking at the code. Practically no lines in the “sub-functions seem executed, after the very initial debug print at the entry of the method… I don’t understand why this seemingly innocuous change broke it so completely, and frankly don’t have too much time to dig for its roots - which also are very non-obvious. Plus, delving into this would screw up my Git structure again, and I’m not comfortable enough with it to endeavor these drastic code sweeps.
It prompted me for the PIN consistently, verified it OK according to the log, and then said that it cannot sign because my cert has problems. It’s all plausible, except that this very cert works quite well with this same code before “generateSignature()” was split into sub-functions. |
A ton of things changed since this report was submitted, and I'm tracking my fork that doesn't exhibit this problem. As this point this issue doesn't seem to serve any useful purpose. |
Happens now consistently. Prompts for a PIN, reports that cannot sign. Debugging output is insufficient (this is at
debug=3;
)The text was updated successfully, but these errors were encountered: