Zero Knowledge; Meeting the Growing Demand for Security and Privacy
summary
Prototype SaaS splits storage and processing: a Laravel backend hosts separate profile and transaction servers, keys are generated in the browser with OpenPGP.js, passwords are bcrypt-hashed in-browser before sending, public keys live on the transaction server and private keys sit encrypted in the profile blob. The demo registers users, issues capability tokens, stores encrypted account data and lets the browser decrypt and re-encrypt transactions for client-side processing. Works as a proof of concept; biggest gaps are offline processing and correlation leakage from graph analysis; code is open source.
AI-written summary · about
chapters (10)
- 0:00Start
- 1:48Securing Communications
- 7:07Software as a Service
- 9:02Zero Knowledge
- 12:39Profile Encryption
- 16:56Processing Encrypted Data
- 30:40Sharing Data Anonymously Between Users
- 31:00The Issues
- 33:25What Next?
- 36:01Competition!
related talks
27mBuilding Zero-Knowledge Backends
38mZero Knowledge: you can't leak what you don't know
47mIs a Secured (Web) App Possible?
28mDeveloping zero-knowledge solutions with JavaScript
27mA privacy first period tracker? Is it even possible?
57mBuild your own Secure Messenger
44mZero Knowledge Architecture
50mBuilding Production-Grade End to End Encrypted App...