51–54 of 54 posts
You scored an F on SSL Labs.
https://www.ssllabs.com/ssltest/analyze.html?d=beta.cryptpad...
I like the idea though! :)
Why do people insist on using the term zero knowledge for simple semantically secure encryption? Zero knowledge has a very specific meaning inside cryptography. Encrypting something does not make it "zero knowledge".
This is a fair question. I'm somewhat to blame for contributing to it over the last 10 years via SpiderOak. There are very good reasons though, and it's probably time I made a post about it.
Okay, I'd really like to hear the argument about why muddying the waters about an already-hard-to-understand subject is totally fine.
> and it's probably time I made a post about it.
Please do.
A blog post that I linked elsewhere in this thread makes the case for why it's harmful.
Earlier quoted context omitted.
The reason crypto in the browser is dangerous is because the crypto algorithms come from the server (they aren't built into the browser) so you have to verify them every time you go to the site to know they're doing everything properly. They could easily change them to no ops for you at the request of the NSA or whatever and you wouldn't know. So on the basis of that, I don't think this project avoids that problem
iOS silently installs updates too all apps from the App Store. There is no meaningful distinction between Javascript being served from the server and an App being served from the App Store.