Firefox/Sync and Backup

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?