Skip to content
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.

Sign up for GitHub

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

Jump to bottom

kbs2 unlock creates shared memory object even on decryption failure #31

Closed
woodruffw opened this issue May 27, 2020 · 0 comments · Fixed by #33
Closed

kbs2 unlock creates shared memory object even on decryption failure #31

woodruffw opened this issue May 27, 2020 · 0 comments · Fixed by #33
Assignees
@woodruffw
Labels
bug Something isn't working C:core

Comments

@woodruffw
Copy link
Owner

This should be unlinked with shm_unlink on decryption failure.
@woodruffw woodruffw added bug Something isn't working C:core labels May 27, 2020
@woodruffw woodruffw self-assigned this May 27, 2020
woodruffw added a commit that referenced this issue May 28, 2020
@woodruffw
kbs2/config: Always remove shared memory object on error
87cb1cc 
This is pretty ugly, but ensures that we never have a lingering
invalid shared memory object.

Fixes #31.
@woodruffw woodruffw mentioned this issue May 28, 2020
Merged
woodruffw added a commit that referenced this issue May 28, 2020
@woodruffw
kbs2/config: Always remove shared memory object on error (#33)
98afc4d 
This is pretty ugly, but ensures that we never have a lingering
invalid shared memory object.

Fixes #31.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@woodruffw woodruffw

Labels
bug Something isn't working C:core
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

kbs2/config: Always remove shared memory object on error woodruffw/kbs2
1 participant
@woodruffw