Open Bug 1311753 Opened 8 years ago Updated 2 years ago

audit PSM initialization for silent failures that may result in an unusable session

Categories

(Core :: Security: PSM, defect, P3)

Product:
Core
Component:
Security: PSM
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox52 --- wontfix

People

(Reporter: keeler, Unassigned)

Details

(Whiteboard: [psm-backlog]) 

See e.g. bug 1311077 comment 3 and 4. During PSM initialization, some operations may fail. In some cases, the failure isn't propagated. This can result in situations where Firefox runs but is more or less unusable (e.g. if the builtin root modules aren't loaded, navigation to https sites, updates, etc. will all fail (probably - given they aren't all duplicated to the user's cert db or something)).

We should audit PSM initialization for cases like this and address them in one of two ways:

1. Fall back to a sensible default (see the solution in bug 1311077)
2. Propagate the failure so that at least whatever's trying to initialize PSM will know it failed
Mass wontfix for bugs affecting firefox 52.
status-firefox52: affected → wontfix
Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information
Priority: P2 → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.