25 ms·
Like others, I also like the novel service workers solution (mitigation might be more accurate) to client side code integrity. I’m more interested in how you h
by chatmasta 9y ago
Like others, I also like the novel service workers solution (mitigation might be more accurate) to client side code integrity.
I’m more interested in how you handle the encryption keys. Specifically, how does a user share a document with another? You mentioned that the “share group” has its own private key; where is this stored?
- twiss 9y agoThe encryption key is in the share link, and also stored encrypted in all collaborating users' accounts (if they have one - an account is not required to collaborate).
- chatmasta 9y agoSo the user is responsible for securely transmitting the share URL? i.e. Secrets are shared out-of-band? It’s pretty clever, I like it. Definitely not the holy grail of client side browser-based multiparty encryption, but you’ve found some innovative techniques. Bravo, good luck with it.
- twiss 9y agoYep. Or, you can also set a password on the document and share that out-of-band, if you don't trust whatever it is you use to send the URL.