Open
Bug 1548030
Opened 5 years ago
Updated 2 years ago
Flip the preference to enable CRLite
Categories
(Core :: Security: PSM, defect, P3)
Core
Security: PSM
Tracking
()
NEW
People
(Reporter: mgoodwin, Assigned: jschanck)
References
(Blocks 1 open bug)
Details
(Whiteboard: [psm-blocked])
Attachments
(1 file)
|
(deleted),
text/x-phabricator-request
|
Details |
Bug 1488865 will land with
security.remote_settings.crlite.enabled
and
security.remote_settings.crlite.enforced
set to false in security-prefs.js
At some point we'll want to change that...
Priority: -- → P3
Whiteboard: [psm-blocked]
Blocks: crlite
|
Assignee | |
Comment 1•2 years ago
|
||
Assuming we do an incremental rollout in 106, we'll want to land security.remote_settings.crlite.enabled=true permanently in 107. I'll attach a patch, but let's wait to land it until we confirm the incremental rollout schedule.
Assignee: nobody → jschanck
|
|
Assignee | |
Comment 2•2 years ago
|
||
This sets security.remote_settings.crlite_filters.enabled = true for
non-android users on all channels. This will cause release users to download
CRLite filters. The default value of security.pki.crlite_mode is still 3
(Confirm Revocations).
|
|
Assignee | |
Comment 3•2 years ago
|
||
We're going to do the staged rollout in 107 and flip the pref permanently in 108 instead.
|
||
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•