-
Notifications
You must be signed in to change notification settings - Fork 5
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
Multipacket handling for credentials listing and other improvements #24
Conversation
5df4632
to
9580018
Compare
Load tests counters: 425 RW before, 421 RO / 4 RW now
Handle injected key writing error Show error on failed write
Abort if the previous state is not set. Try to clean up after Credential's write failure. Using 0x61FF, as we do not know the count of the remaining bytes.
Fill the buffer as long as it is possible, break otherwise. Instead of using a temporary buffer for the unfit data, reiterate over directories again - this saves memory at the cost of the additional computation.
1631dfd
to
314f8e5
Compare
314f8e5
to
98c8b01
Compare
@robin-nitrokey Friendly ping! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! I’m not sure if I understand the role of the SendRemaining
command though. Currently it has the same effect as calling ListCredentials
(unless there is no cached state), right? Wouldn’t it make more sense if ListCredentials
would start at zero and only SendRemaining
would use the cached state? Alternatively, an optional offset could be added to ListCredentials
directly.
Regarding the |
Changes:
Fixes #19
Fixes #14