OK, I decided to build this and try to make a living off it: An end-2-end encrypted serverless platform for web/mobile apps, offering user auth, db, & file store services. The end user gets privacy. The app developer gets spared from the liability & burden of handling user data.https://twitter.com/dvassallo/status/1122968287355129856 …
It tends to expose the encrypted to arbitrary (i.e. large sizes) and malicious (i.e. padding oracles) inputs. Signing is specifically designed for proof of key possession and has a lot of thought through defenses.
-
-
Usual pattern is to establish a channel with DH, and to sign the DH shares. Gives you forward secrecy and proof of key. Asymmetric key encryption isn't used in modern network encryption. Ok-ish for durable data envelope encryption.
-
For the sharing encrypted data, DBs or channels, that's an open hard problem. If you share the underlying encryption key, it has to be bulk-reencrypted on revoke. If you do pair-wise, you have to denormalize and can end up with N^2 key establishment problems.
- 1 more reply
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.


Account Management
Database
File Store
All these will be available through a JavaScript API for the browser. Initial iOS and Android support will be through