Firefox/Sync and Backup: Difference between revisions
< Firefox
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| (8 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
This page aggregates resources and information about the work that has already been done to define how to simplify browser | This page aggregates resources and information about the work that has already been done to define how to simplify browser synchronization and profile back-up. Some of this information can be obsolete. | ||
* [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/DLJpBYVFqdY Sync in 2012: Persona integration] | * [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/DLJpBYVFqdY Sync in 2012: Persona integration] | ||
* [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/5NhnEGuwuN8 Sync in 2012: New storage service and storage format] | * [https://groups.google.com/forum/?fromgroups#!topic/mozilla.dev.planning/5NhnEGuwuN8 Sync in 2012: New storage service and storage format] | ||
* [[BrowserID_Key_Wrapping|Browser ID Key Wrapping Proposal]] | |||
* [http://benlog.com/articles/2012/04/30/encryption-is-not-gravy/ VIDEO - Firefox Sync without the Sync key] | |||
* [[Identity/Architecture/SignIntoBrowser|Sign in to the browser proposal]] | * [[Identity/Architecture/SignIntoBrowser|Sign in to the browser proposal]] | ||
* [[Identity/CryptoIdeas/01-PBKDF-scrypt|Key Wrapping Security Review]] | * [[Identity/CryptoIdeas/01-PBKDF-scrypt|Key Wrapping Security Review]] | ||
* [https://groups.google.com/forum/?fromgroups#!searchin/mozilla.dev.identity/key$20wrapping$20protocol/mozilla.dev.identity/Aj7f9DPf-2I/9ACFd9TRkCYJ Key Wrapping: Protecting the initial set-up] | * [https://groups.google.com/forum/?fromgroups#!searchin/mozilla.dev.identity/key$20wrapping$20protocol/mozilla.dev.identity/Aj7f9DPf-2I/9ACFd9TRkCYJ Key Wrapping: Protecting the initial set-up] | ||
* [https://groups.google.com/d/topic/mozilla.dev.identity/JhhT11pysKs/discussion Key Wrappings: More Details discussion] | * [https://groups.google.com/d/topic/mozilla.dev.identity/JhhT11pysKs/discussion Key Wrappings: More Details discussion] | ||
* [[Services/Sync/Protocol_2.0 Sync 2.0 | * [[Services/Sync/Protocol_2.0|Sync 2.0 Wishlist]] | ||
* [[Services/Sync/Protocol_2.0_changes|Sync 2.0 Changes]] | * [[Services/Sync/Protocol_2.0_changes|Sync 2.0 Changes]] | ||
* [https://groups.google.com/forum/?fromgroups#!topic/mozilla-services-dev/5Sf0xqHf8P0 Flag day mitigation tactics: For migration of Sync to a new back-end] | * [https://groups.google.com/forum/?fromgroups#!topic/mozilla-services-dev/5Sf0xqHf8P0 Flag day mitigation tactics: For migration of Sync to a new back-end] | ||
* [http://people.mozilla.com/~zfang/SignIn/Home.html OBSOLETE - Sign in to the Browser Mock ups] | * [http://people.mozilla.com/~zfang/SignIn/Home.html OBSOLETE - Sign in to the Browser Mock ups] | ||
* [http://people.mozilla.com/~zfang/SignInMobile/Mobile.html OBSOLETE - Sign in to the Mobile Mock ups] | * [http://people.mozilla.com/~zfang/SignInMobile/Mobile.html OBSOLETE - Sign in to the Mobile Mock ups] | ||
* [http://docs.services.mozilla.com/sync/index.html Sync Client Documentation] | |||
Open questions: | |||
* Is the user experience to "pair devices" or to "log in to the account"? | |||
* What's the required security level? | |||
* Key stored locally or wrapped and stored remotely? Do we want to offer both options? | |||
* Does all the information need to be encrypted? Does all the information need the same level of security? | |||
* Is Persona the only login method? Can a user benefit from this service without a Persona account? | |||
* Back-up == Permanent storage? Do we want to remove data after certain level of inactivity? | |||
* Discoverability of Sync+Back Up: Hidden in settings? A more findable UI with feedback about status (i.e. shows avatar if logged in). | |||
* Profile Sync vs Experience Sync: Can we offer an API that add-on and web-app developers can use to store information about the user? Can we run a freemium model? | |||
* Transition from the actual Sync to the new service. How does it look like? | |||
* How does this look with a locally run machine? Is it possible to run this service locally? | |||
Latest revision as of 23:34, 9 July 2012
This page aggregates resources and information about the work that has already been done to define how to simplify browser synchronization and profile back-up. Some of this information can be obsolete.
- Sync in 2012: Persona integration
- Sync in 2012: New storage service and storage format
- Browser ID Key Wrapping Proposal
- VIDEO - Firefox Sync without the Sync key
- Sign in to the browser proposal
- Key Wrapping Security Review
- Key Wrapping: Protecting the initial set-up
- Key Wrappings: More Details discussion
- Sync 2.0 Wishlist
- Sync 2.0 Changes
- Flag day mitigation tactics: For migration of Sync to a new back-end
- OBSOLETE - Sign in to the Browser Mock ups
- OBSOLETE - Sign in to the Mobile Mock ups
- Sync Client Documentation
Open questions:
- Is the user experience to "pair devices" or to "log in to the account"?
- What's the required security level?
- Key stored locally or wrapped and stored remotely? Do we want to offer both options?
- Does all the information need to be encrypted? Does all the information need the same level of security?
- Is Persona the only login method? Can a user benefit from this service without a Persona account?
- Back-up == Permanent storage? Do we want to remove data after certain level of inactivity?
- Discoverability of Sync+Back Up: Hidden in settings? A more findable UI with feedback about status (i.e. shows avatar if logged in).
- Profile Sync vs Experience Sync: Can we offer an API that add-on and web-app developers can use to store information about the user? Can we run a freemium model?
- Transition from the actual Sync to the new service. How does it look like?
- How does this look with a locally run machine? Is it possible to run this service locally?