Invalid sync key is accepted as correct one, then existing data is wiped

RESOLVED INVALID

Status

()

RESOLVED INVALID
8 years ago
3 months ago

People

(Reporter: st3fan, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

8 years ago
I have created an account with 3.6.12/1.5.1.

I then quit Firefox and run Minefield trunk (2010-12-10) and create a new empty
profile. I setup sync and enter the correct username and password but the INCORRECT sync key.

I see the "verifying" thing happening, without errors. Sync is then setup.

Sync proceeds to setup the account with the wrong sync key and wipes existing data, replacing it with empty data from the current (empty) profile.
(Reporter)

Comment 1

8 years ago
Created attachment 496826 [details]
Weave log file
Yes, the new-crypto Sync does not verify the Sync Key because when it doesn not look at the old priv/pub keypair.
(Reporter)

Comment 3

8 years ago
This means you can not install 1.6 on a clean profile with an existing 1.5.1 account that has data in the cloud. I kind of assumed that it would do the initial sync by grabbing the v4 data and then push the upgraded v5 data back. I know we are not a backup service, but I don't think people expect to lose data when upgrading this way.
(In reply to comment #3)
> This means you can not install 1.6 on a clean profile with an existing 1.5.1
> account that has data in the cloud. I kind of assumed that it would do the
> initial sync by grabbing the v4 data and then push the upgraded v5 data back.

Nope. The client only ever supports one storage version at a time.

> I know we are not a backup service, but I don't think people expect to lose data
> when upgrading this way.

They're not losing data. The canonical data is not on the server, it's spread across all clients.
Pretty sure this is stale.
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → INVALID
(Assignee)

Updated

3 months ago
Component: Firefox Sync: UI → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.