docs: add a short guide on security. #2201
Conversation
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
|
||
| <<< @../../examples/encryption/src/Example.tsx{tsx} | ||
|
|
||
| ### Key management |
There was a problem hiding this comment.
I don't have a lot of experience with key distribution but isn't storing the key (unencrypted) alongside the encrypted data more-or-less make it basically the same as if it wasn't encrypted? Since anyone with access to the db can now decrypt whatever data they want?
There was a problem hiding this comment.
You could store keys in a different database and just sync the right ones. I do think that the point of Electric being good to sync keys is valid: it's just like the distributed config case. You need to share the right keys with the right users. What better mechanism?
There was a problem hiding this comment.
🤷 like I said I dunno — maybe if the key is encrypted before sharing so it's just a backup/cloud syncing mechanism.
There was a problem hiding this comment.
Have jigged the description a bit.
There was a problem hiding this comment.
Ultimately for e2e encryption you need to get keys into the client.
There was a problem hiding this comment.
you can have client-generated keys right?
There was a problem hiding this comment.
Yup, but if you're sharing the data, you have to share keys.
Co-authored-by: Kyle Mathews <[email protected]>
Co-authored-by: Kyle Mathews <[email protected]>
Covering data access and encryption:
https://deploy-preview-2201--electric-next.netlify.app/docs/guides/security