Issues with lookups against encrypted fields about django-fernet-encrypted-fields HOT 2 OPEN

Maybe we can learn from and implement this? https://django-fernet-fields.readthedocs.io/en/latest/#indexes-constraints-and-lookups

from django-fernet-encrypted-fields.

You're right this project doesn't support that.

SQLAlchemy is probably using encrypted fields at the database level whereas this and other projects, like it using PBKDF2 hash at the the software level then saved the value value to the back-end. This allows them to work with database back-ends that would not normally support it. That's why you can't filter on the original value, you'd need to be filtering on the output at the time.

This means that the output of the encryption is unique every time it's run. For example if you save your model and look directly at the database, then save the model again and repeat you'll notice that the value in the database has changed. This is because the project uses "PBKDF2-with-HMAC-with-SHA256" to help protect against bruteforce attacks (PBKDF2 is a slow algorithm compared to SHA265 alone). - https://crypto.stackexchange.com/questions/35275/whats-the-difference-between-pbkdf-and-sha-and-why-use-them-together

So you'd need to filter on another property

from django-fernet-encrypted-fields.