FIPS can no longer be enabled, saved passwords inaccessible



6 months ago
2 months ago


(Reporter: adam, Unassigned)



53 Branch

Firefox Tracking Flags

(Not tracked)


(Whiteboard: [regression:TB53])



6 months ago
User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.133 Safari/537.36

Steps to reproduce:

Updated from Thunderbird 52 to 53 then started it as usual.

Actual results:

None of my mailboxes could be accessed over IMAP because saved passwords were inaccessible. I am no longer asked for my FIPS-140 software software device.

I am also unable to re-enable this via the security devices in the advanced settings because it claims there is no master password set. This is worrying because I've had a master password declared for years, and the form to change the master password also claims nothing is set. (Attempting to set it as it was fails.)

Expected results:

I should have been asked for my FIPS-140 software security device password in order for saved passwords to be used in IMAP connections.

Comment 1

6 months ago
Downgrading to version 52.0b4 has definitely resolved this issue for me.

Comment 2

6 months ago
No doubt same issue as bug 1337950. But let's keep this open in Thunderbird
Depends on: 1337950
Ever confirmed: true
Keywords: regression
Whiteboard: [regression:TB53]

Comment 3

6 months ago
I did notice that issue too before reporting this, but thought it wouldn't be savory to report a Thunderbird issue in Firefox.

This could likely be an update in an underlying component shared between both products.
FIPS and Chat (at least Twitter) don't work together well either…
Neither do FIPS and Filelink.
One way or the other (make it work or remove), something should happen.

Comment 5

6 months ago
Just tried on my home PC too, can confirm it happens there as well.

Tip: When you downgrade remember to turn off automatic updates, or you'll find that you have to install Thunderbird 52.0b4 again.

Comment 6

5 months ago
This appears to be resolved in version 54.0b1, along with the sister issue in Firefox 1337950.

Comment 7

2 months ago
Thanks Adam.
Last Resolved: 2 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.