136 ms·
Zero knowledge here means client side only not zero knowledge proof, correct?
by SeanAnderson 4y ago
Zero knowledge here means client side only not zero knowledge proof, correct?
- js8 4y agoIt means progress: Normal app: Both user and application know what they are doing. User-friendly app: User doesn't know what they're doing, luckily, the app does. Zero-knowledge app: Neither the application nor the user know what they are doing.
- baby 4y agoYeah this doesnt seem to have anything to do with zero knowledge besides reusing the keywords because it’s trendy
- tony_codes 4y agothe decryption key never leaves the browser. Maybe it's not perfect, but I'm not using the keywords because it's trendy, this project started out of an interest in more secure authentication and data security.
- baby 4y agoBut zero knowledge cryptography has nothing to do with that. Sorry I was a bit harsh, I guess I got tripped by the misuse there.
- tony_codes 4y agoit's ok, it's hacker news so I expected honesty which I appreciate. But What would you call an authentication mechanism which never passes the decryption key off the browser? It's an improvement over systems that handle the keys themselves on the server side.
- baby 4y agoI'm not sure, I would call that encrypted storage perhaps? Or client-side encryption
- tony_codes 4y agoyeah, perhaps client-side encryption or User encryption ownership or something along those lines. To me, "encrypted storage" doesn't sound like anything different that what is done with normal authentication methods.