Confirmed users
971
edits
(Created page with " == Crypto on the Server Side == The most ideal setup for us is to be able to do a sync session from the Firefox Home servers to the Sync Servers. This means that we run a sync ...") |
|||
| Line 2: | Line 2: | ||
== Crypto on the Server Side == | == Crypto on the Server Side == | ||
The most ideal setup for us is to be able to do a sync session from the Firefox Home servers to the Sync Servers. This means that we run a sync | The most ideal setup for us is to be able to do a sync session from the Firefox Home servers directly to the Sync Servers. Just like any other sync client would. This means that we run a sync session and store the unencrypted records on our own servers. This allows us to easily put a web service on top of those and to run online and offline queries on the user's data. | ||
=== Pros === | === Pros === | ||
* We have access to unencrypted data, which means we can prepare result sets and do full text search on the server | * We have access to unencrypted data, which means we can prepare result sets offline and do full text search on the server | ||
* This is a simple setup, we just need to run a sync client and database servers to store the unencrypted data | * This is a simple setup, we just need to run a sync client and database servers to store the unencrypted data | ||
| Line 12: | Line 12: | ||
* We store unencrypted data on servers hosts by Mozilla | * We store unencrypted data on servers hosts by Mozilla | ||
* We have to store encryption keys for the collections that we sync somewhere so that we can run a sync client. (Either on Firefox Home infrastructure or in the Sync | * We have to store encryption keys for the collections that we sync somewhere so that we can run a sync client. (Either on Firefox Home infrastructure or in the Sync Infrastructure) | ||
== Crypto and Storage in the Browser == | == Crypto and Storage in the Browser == | ||