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

🚀 Feature: Encypted database fields #3150

Closed
2 tasks done
maeddin opened this issue Apr 25, 2022 · 1 comment · Fixed by #5604
Closed
2 tasks done

🚀 Feature: Encypted database fields #3150

maeddin opened this issue Apr 25, 2022 · 1 comment · Fixed by #5604
Milestone

Comments

@maeddin
Copy link

maeddin commented Apr 25, 2022

🔖 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?

  • I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

@maeddin
Copy link
Author

maeddin commented Apr 27, 2022

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.

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

Successfully merging a pull request may close this issue.

2 participants