-
Notifications
You must be signed in to change notification settings - Fork 96
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 composite key computation for BytesIO #388
Conversation
Please add a test to showcase how this can corrupt a db and that it does not happen with this patch. |
Could you take this one over? I do have some higher priority stuff on my stack and this blocks Secrets. |
Sure, thanks for looking into it!! Make sure I am able to push to this branch. |
8698fdc
to
79dbb28
Compare
@Evidlo Hi, this is ready for review. For context, this is corrupting databases on Secrets https://gitlab.gnome.org/World/secrets/-/issues/537. |
79dbb28
to
839508c
Compare
In case a keyfile as BytesIO has been read before, the next read will be empty. We need to ensure that we are reading the data from the beginning. Add seek to start to fix it.
839508c
to
ac2653a
Compare
We also update the patch with commit actually merged as part of libkeepass/pykeepass#388.
We also update the patch with commit actually merged as part of libkeepass/pykeepass#388.
We also update the patch with commit actually merged as part of libkeepass/pykeepass#388.
We also update the patch with commit actually merged as part of libkeepass/pykeepass#388.
In case a keyfile as BytesIO has been read before, the next read will be empty. We need to ensure that we are reading the data from the beginning.
Add seek to start to fix it.