-
Notifications
You must be signed in to change notification settings - Fork 14
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
Fix calculateAll #8
Conversation
The algorithm used in calculateAll is wrong, if you have multiple tokens, some with the touch requirement and some without, the map produced by calculateAll is not correct: the first n names have the touchRequired, the following TOTP tokens from other keys.
Oops, good catch. Will you be able to produce a test case for this as well? |
I'm struggling to generate the bytecode of the mocks, maybe you can help me or you have a better tool to do it. In your tests, the order of the credentials is the following:
You can generate a test by putting a touch required credential at the end of this list and running |
I'm on vacation now so I'll get back to it in ~14days. |
Any updates? |
Sorry, work/live interference. I am having a look today/this week. |
This should hopefully unblock the test in #8.
Sorry for making you wait @j0hnsmith & @asiragusa. I've committed the internal dump tool I've used for the previous tests. If your drop a Apart from that the PR looks good to me. Could be released tomorrow if you can quickly contribute the tests ... |
This should fix the issue from PR #8 while using a single datastructure instead of two.
Closed through 4e2c7c9 while also changing all commands to use the new structure. Thanks again @asiragusa & @j0hnsmith, took me a long time to find the time to fix this properly. |
The algorithm used in calculateAll is wrong, if you have multiple
tokens, some with the touch requirement and some without, the map
produced by calculateAll is not correct: the first n names have the
touchRequired, the following TOTP tokens from other keys. This PR
fixes this issue, using the appropriate data structures.