Confirmed users
971
edits
Home/Features/crypto/proxy: Difference between revisions
→Accessing Sync Data
(Created page with "= Crypto Proxy = Firefox Home Roadmap: http://bit.ly/homeroadmap == Introduction == This is a proposal for the 'Crypto Proxy'. It is a server-side component in the Sync Servic...") |
|||
| Line 75: | Line 75: | ||
Firefox Home has its own Sync Client. Instead of talking directly to the Sync Service, authenticated with Basic Auth, it will now talk to the Crypto Proxy with the Username and Access Token. | Firefox Home has its own Sync Client. Instead of talking directly to the Sync Service, authenticated with Basic Auth, it will now talk to the Crypto Proxy with the Username and Access Token. | ||
'''The crypto proxy will have to talk to the regular sync infrastructure. It will either skip basic auth or it will have to authenticate by some other means. (Basic Auth is not possible because the proxy does not know the users password)''' | |||
The Sync Protocol is pretty much the same except that known collections to which Firefox Home has access are automatically decrypted by the Crypto Proxy. | The Sync Protocol is pretty much the same except that known collections to which Firefox Home has access are automatically decrypted by the Crypto Proxy. | ||
This means Firefox Home does not have to access crypto/keys but instead can go straight to the collections it wants to sync. | This means Firefox Home does not have to access crypto/keys but instead can go straight to the collections it wants to sync. | ||