Cryptpad: Zero Knowledge, Collaborative Real Time Editing
beta.cryptpad.fr
Cryptpad: Zero Knowledge, Collaborative Real Time Editing
1–10 of 54 posts
Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing
#2Proof of work is probably an acceptable solution for proof of concept but anonymous consensus isn't needed for for collaborative document editing.
I'm still thinking if this use cases needs timestamping or atomic broadcast.If timestamping is sufficient, Google's new roughtime protocol would do the job well. Otherwise you need a proper atomic broadcast algorithim like RAFT, Tendermint, Honeybadger etc.
Great work.
Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing
#3Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing
#4Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing
#5How can I safely share the URL to someone without already using an established encrypted communication method?
Is the encryption key stored in my browser history?
Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing
#6Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing
#7This is pretty cool, but I believe that you still have to trust cryptpad.fr to send you javascript that won't leak.
Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing
#8Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing
#9This is pretty cool, but I believe that you still have to trust cryptpad.fr to send you javascript that won't leak.
From a glance at the GitHub page, it looks like you can self-host the project. Is "bower install" a possible attack vector as well? I'm unfamiliar with it.
So the only attack vector would be a MIT attack, intercepting the requests to the Bower registry.