You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 27, 2022. It is now read-only.
For some future features that require entries that are not supposed do be read by others (eg settings, private messages,... ) an encrypted storage would be useful.
I've read about the privacy problem in multiple threads, so i write a new one.
The encryption key itself could be encrypted with the public key of the page/account, so the key can be shared with others if needed (eg for private messages) .
The text was updated successfully, but these errors were encountered:
Yeah this has been on my mind. If you wanted to experiment, you could use https://github.com/sodium-friends/sodium-universal or something like it within an app. You'd write the public keys to the profile somewhere, and then save the private keys to localStorage. It's not a great longterm solution -- eventually the browser is going to need to manage private keys securely, and ideally keep the private keys out of the app's memory space entirely. We also need to give apps better tools to lock down their execution space (ie CSP controls). But it'd be a good PoC.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
For some future features that require entries that are not supposed do be read by others (eg settings, private messages,... ) an encrypted storage would be useful.
I've read about the privacy problem in multiple threads, so i write a new one.
The encryption key itself could be encrypted with the public key of the page/account, so the key can be shared with others if needed (eg for private messages) .
The text was updated successfully, but these errors were encountered: