Skip to content
This repository has been archived by the owner on Dec 27, 2022. It is now read-only.

Encrypted data storage #22

Open
fsteff opened this issue Jan 15, 2018 · 2 comments
Open

Encrypted data storage #22

fsteff opened this issue Jan 15, 2018 · 2 comments

Comments

@fsteff
Copy link

fsteff commented Jan 15, 2018

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) .

@fsteff fsteff closed this as completed Jan 15, 2018
@fsteff fsteff reopened this Jan 15, 2018
@fsteff
Copy link
Author

fsteff commented Jan 15, 2018

Should not do this on the phone, damn ui😅

Also, probably this is not fritter specific, but WebDB...

@pfrazee
Copy link
Member

pfrazee commented Jan 15, 2018

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants