AESEncrypt and AESDecrypt functions shoud be public by default#59
Open
nicolasriousset wants to merge 1 commit intovertica:masterfrom
Open
Conversation
AESEncrypt and AESDecrypt functions are now public by default
|
|
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
2 participants
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.
When installing the encryption_package, the AESEncrypt and AESDecrypt functions usage is restricted to the user installing it.
Since these functions are immutable, and do not affect the database structure, and that the account used to install is probably not the one which will use them, it seems to make sense to make them public.