-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
🚀 Feature: Encypted database fields #3150
Milestone
Comments
Of course, you could also include the option for deterministically encrypted and randomly encrypted attributes. Randomly encrypted attributes could of course not be used in queries at all. |
2 tasks
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
🔖 Feature description
It would be very handy especially for string fields if you could have AppWrite encrypt them natively.
🎤 Pitch
Here I think of the use-case for keys that are stored directly in the database, which should not be readable for everyone with database access. Of course, there are other examples of sensitive data that should not be stored as plain text in the database. Of course you would lose some queries and indexes for such fields, but "equal" would still work without problems. As key for these fields you could either take the already existing
_APP_OPENSSL_KEY_V1
or create an own ENV variable for it.👀 Have you spent some time to check if this issue has been raised before?
🏢 Have you read the Code of Conduct?
The text was updated successfully, but these errors were encountered: