Live data from Hacker News

Cryptpad: Zero Knowledge, Collaborative Real Time Editing

beta.cryptpad.fr

1–10 of 54 posts

Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing

#2
This is a cool implementation of this idea.

Proof 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

#4
Sharing the URL is essentially giving out the key, so there is no digitally safe way to do this unless you encrypt the initial message, at which stage you are using encrypted communication anyway and the URL just leaves open an attack vector. Please correct me if I am wrong.

Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing

#5
I have often seen claims that doing any kind of crypto in (browser) javascript is dangerous. Does this fall into that trap?

How 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

#7

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

Re: Cryptpad: Zero Knowledge, Collaborative Real Time Editing

#9

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

Bower is a package manager for Javascript libraries.

So the only attack vector would be a MIT attack, intercepting the requests to the Bower registry.

Post reply on HN