You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@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.
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.
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.
The text was updated successfully, but these errors were encountered: