Created attachment 430407 [details] Update screen with multiple FIPS password prompts When you have enabled FIPS (menu Tools | Options, Advanced pane, Certificates tab, Security Devices button), and upgrade or downgrade Thunderbird, you get multiple password prompts. One for each add-on that is installed and gets its updates over https, with a maximum of three. See also bug 450721 comment #6 and bug 217646
9 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 450721
Didn't realize you were filing this for add-ons... if you want to file this for add-ons you should file the bug in add-ons manager and not app update.
Ah, ok... Do I file a new bug, or dedupe this one and change component?
9 years ago
Status: RESOLVED → UNCONFIRMED
Component: Application Update → Add-ons Manager
QA Contact: application.update → add-ons.manager
Resolution: DUPLICATE → ---
I have the same problem. Can someone please fix this? It makes Thunderbird look like the people working on it aren't real programmers!
Is this issue still present on Latest Nightly 25?
For normal day to day usage I used to get two master password prompts in TB 17 and that bug seems to be resolved in current Daily and Earlybird dated 2013-07-24. However this bug still persists. When I start Daily after having run Earlybird or after upgrading, I get about 10 master password prompts in the update screen which checks for extension compatibility...
Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.
Status: NEW → RESOLVED
Last Resolved: 9 years ago → 5 months ago
Resolution: --- → INACTIVE
Onno. Does this still reproduce?
I don't know when exactly it started, but with TB60 it isn't possible anymore to enable FIPS, so I can't reproduce at the moment. Maybe when in the future FIPS will be possible again I can verify this. The current state of FIPS is unclear to me. According to bug 1360692 it would be removed, but the state of that bug is now resolved won't fix...
You need to log in before you can comment on or make changes to this bug.