Building Zero-Knowledge Backends
summary
Backend stores only encrypted blobs and public keys and never holds private keys so servers cannot decrypt user data; server logic limits itself to signature and timestamp verification, authorization checks and returning encrypted payloads. Implementation uses Node with a REST framework (Resta), certificate handling via notForge, document storage in MongoDB, and auth with JSON Web Token/Passport over TLS. Key flow uses client-side symmetric keys wrapped with asymmetric certificates (x.509); the system works as a simple REST ping‑pong.
AI-written summary · about
chapters (9)
- 0:00Start
- 1:36We Need Encryption
- 2:42Design Pattern That Enforces User Privacy
- 3:10E2E Encryption
- 3:59Symmetric Key Wrapping (IDEA, Blowfish, etc.)
- 8:59Certificate Generation • Key Storage
- 13:09Full TLS native implementation • X.509 compatible
- 17:47Actions are identified and protected with JWT
- 25:09The complex part is on the Client and requires a lot of Crypto
related talks
45mZero Knowledge; Meeting the Growing Demand for Security and Privacy
38mZero Knowledge: you can't leak what you don't know
47mIs a Secured (Web) App Possible?
44mZero Knowledge Architecture
28mDeveloping zero-knowledge solutions with JavaScript
50mBuilding Production-Grade End to End Encrypted App...
42mZero-Knowledge Architecture, or Leak-Free Secrets, with HC Vault
43mSecure Storage and Sharing of Large Files