-
Notifications
You must be signed in to change notification settings - Fork 1
Encryption sanity checks #341
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
Conversation
a6f7c84 to
6a27d0c
Compare
auxesis
left a comment
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.
The encryption tests are good, but I don't think we should be introducing complexity into which builds run in what context.
Let's strip this PR down to just the encryption tests, and we can address the build changes in a separate PR.
c629f8f to
6a27d0c
Compare
…sure The identity closure |t| t in map_or_else is unnecessary. Using unwrap_or_else is more idiomatic when the Some value doesn't need transformation.
6a27d0c to
47592d1
Compare
Add support for unquoted PostgreSQL identifiers when setting keyset name via SET CIPHERSTASH.KEYSET_NAME. Previously only quoted strings and numbers were accepted; now valid PG identifiers work without quotes. Update tests to validate the new behavior and adjust invalid test cases.
auxesis
left a comment
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.
Thanks for this @tobyhede.
Great to have this extra layer of tests to verify the encryption works as expected.
Goal: Add encryption verification tests to ensure data is actually encrypted, preventing silent mapping failures from going undetected.
Architecture: Create a reusable
assert_encryptedhelper incommon.rsthat queries the database directly (bypassing proxy) and asserts stored value differs from plaintext. Add one sanity check test per data type.