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.

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

Add salt option to cloak for increased security #26

Closed
cayblood opened this issue Mar 23, 2017 · 2 comments
Closed

Add salt option to cloak for increased security #26

cayblood opened this issue Mar 23, 2017 · 2 comments

Comments

@cayblood
Copy link

It would be nice if you could specify a salt column that could be used to encrypt each row's cloak-enabled columns differently, for added security.

@tomciopp
Copy link
Contributor

@cayblood Typically a salt is only used for hashing a one way function. AES encryption uses a random initialization vector which it stores along with the data when it encrypts it. Therefore it should not be necessary, nor would it add any additional security if there was an additional salt field.

@danielberkompas Unless you have any other views on this topic I suggest this issue should be closed.

@danielberkompas
Copy link
Owner

I agree with @tomciopp. This idea would also be difficult to implement because it requires two fields. Cloak (and Ecto custom types in general) work best on a single field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants