Closed Bug 624430 Opened 15 years ago Closed 9 years ago

Sync key mismatch (SHA256 HMAC error) on sender after setting up client with J-PAKE

Categories

(Firefox :: Sync, defect)

defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: rnewman, Unassigned)

Details

Justin reported that: * Machines A and B were happily syncing. 4.0b8/1.6.1. * Machine C added via J-PAKE. * Machine B (after restart, presumably) reports that its sync key cannot decrypt the server keybundle. Master Password was enabled on Machine B. Log: http://justin.pastebin.mozilla.org/921526 ... but doesn't do much good; it's the J-PAKE sender log, after a restart. This is relevant: 2011-01-10 09:52:02 Service.Main INFO Testing info/collections: {"clients":1294678753.65,"crypto":1292863910.86,"forms":1294679286.58,"history":1294679286.96,"keys":1285522516.97,"meta":1292867312.41,"bookmarks":1294678754.19,"prefs":1293497123.28,"tabs":1294679287.12,"passwords":1294632949.94}
qa will attempt to repro
Clarifying: * Machine A: no MP. * Machine B: MP. * Machine C: no MP. J-PAKE was between A and C, which are now working fine. Machine B stopped working. Possible old version/upgrade/?
This bug only affects Sync 1.1, and it was shut down in the fall of 2015 (https://blog.mozilla.org/services/2015/07/31/shutting-down-the-legacy-sync-service/).
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Component: Firefox Sync: Backend → Sync
Product: Cloud Services → Firefox
You need to log in before you can comment on or make changes to this bug.