security: fix potential segfault on exit - #567
Merged
Merged
Conversation
sqlcipher introduced a cleanup in atexit handler, which is unsafe when other threads may still be closing database connections, which is the case in sqlx. This commit uses a patched version of sqlcipher which disables this feature. Instead of segfaulting and potentially leaking secrets in a coredump, we rely on the OS to clean up them.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
sqlcipher introduced a cleanup in atexit handler, which is unsafe when
other threads may still be closing database connections, which is the
case in sqlx. This commit uses a patched version of sqlcipher which
disables this feature. Instead of segfaulting and potentially leaking
secrets in a coredump, we rely on the clean up by the OS.