3 ms·
The deal with mine, is the encryption is left to the client. The server just stores a binary "thing." That "thing" can be an encrypted envelope, managed by the
by ChrisMarshallNY 6y ago
The deal with mine, is the encryption is left to the client. The server just stores a binary "thing." That "thing" can be an encrypted envelope, managed by the client[s]. Since it's a closed-loop system, then a key could be shared programmatically, outside the purview of the server.
- tasn 6y agoYeah, in Etebase the server also just sees "things", though it tries to make it easy on the client to only get what's changed and etc.
- fabrice_d 6y agoJust curious, how does that differ from a system like Firefox sync which is also using client side encryption?
- tasn 6y agoI don't think Firefox sync makes it very easy for devs to build other encrypted applications. Even if they did however, there are a lot of challenges with encrypted applications that they just don't take care of. Not to mention that they are very we centric and don't have developer APIs in many languages.