Feture Request: Want to get some part of data encrypted via RSA Private keys to avoid client side data manipulation #11124
Unanswered
rahul3v
asked this question in
Feature Requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Feature request
To get some part of data encrypted via RSA Private keys to avoid client side data manipulation, and user can add RSA public key to decrypt that data at client side to confirm data is not manuplated;
Is your feature request related to a problem? Please describe.
Well It would be batter to get some part of data encrypted so that any user using some tools can't able to modify data before feeding it to the front-end applications and breaking the chance of data validation;
For example: Subscription Services (Security Issue for client side data validation)
Let say a user didn't subscribed to 'pro' version as we fetch our data via database to get that information,
But at client side we can use many ways to manipulate server data we received before feeding it into the client-side application and application don't have any way to verify whether it's a valid one or not if we directly getting the data un-encrypted
Impact : User can able to access features of 'pro' versions without having one
Describe the solution you'd like
A user can able to set a column in Postgres Database to which he/she wants it go encrypted all the time. (you can limit no. of columns if you want)
A user should be provided with RSA private and public keys so that user can use that public key at client side for any data validation check
Describe alternatives you've considered
I have to use server function as an api to do that, fetching the data from supabase and encrypt that their and send it to client and decrypt it at client side for data validity check
Additional context
What supabase is all about to one can use it on client side is not justifiable if we have to use anything internally
All reactions