700081 - J-PAKE / Easy Setup fails with FIPS mode enabled

Status: RESOLVED DUPLICATE of bug 443386

(Firefox :: Sync, defect)

Description

[podge]

Attachment: Latest sync log showing failure.

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:7.0.1) Gecko/20100101 Firefox/7.0.1
Build ID: 20110928134238

Steps to reproduce:

Kept getting error bar indicating sync issues. Removed sync account, then attempted to perform setup again.


Actual results:

Attempting to use the "Add a Device" dialog, when I enter the three sets of characters on the other device, the other device just report "Please try again" and the characters change on the device I am attempting to setup.
Attempting to enter the account information manually (email address, password, sync key), when I click next the little progress icon appears briefly then goes away, but the dialog will not continue.


Expected results:

Browser should have been added to the existing sync account, or an error message displayed.

Comment 1

[Richard Newman [:rnewman]]

podge: are you running in FIPS mode?

http://support.mozilla.com/en-US/kb/Configuring%20Firefox%20for%20FIPS%20140-2

Comment 2

[podge]

Yes I am in FIPS mode (step 2 in the linked document). Although I haven't followed all those steps to disable the older SSL versions/ciphers (steps 1&3 in the linked document).

Comment 3

[Richard Newman [:rnewman]]

(In reply to podge from comment #2)
> Yes I am in FIPS mode (step 2 in the linked document). Although I haven't
> followed all those steps to disable the older SSL versions/ciphers (steps
> 1&3 in the linked document).

Sync doesn't work in FIPS mode; see Bug 443386. Apparently neither does the J-PAKE setup flow. This is not a big surprise.

Please try again with FIPS mode disabled. If that gets you moving, I'll dupe this.

Comment 4

[podge]

That seems to fix it. Disabling FIPS, then setting up sync works. Re-enabling FIPS afterwards, and I get the same errors again and can't sync anymore.

Comment 6

[podge]

Well that's annoying, it's a more than 3 year old bug but sync still doesn't have an error message to tell you it won't work. Sorry to have taken up your time with it.

Comment 7

[Richard Newman [:rnewman]]

(In reply to podge from comment #6)
> Well that's annoying, it's a more than 3 year old bug but sync still doesn't
> have an error message to tell you it won't work.

Yup, afraid so. It affects only a tiny minority of users, so it hasn't really been a product priority.

Patches welcome :)

> Sorry to have taken up your time with it.

Not a problem!