SanitizeOnShutdown should allow unset values and unlocked
Categories
(Firefox :: Enterprise Policies, enhancement, P3)
Tracking
()
People
(Reporter: mkaply, Assigned: mkaply)
Details
Attachments
(1 file, 1 obsolete file)
|
47 bytes,
text/x-phabricator-request
|
pascalc|PTO
:
approval-mozilla-beta+
RyanVM
:
approval-mozilla-esr68+
|
Details | Review |
Currently the SanitizeOnShutdown policy always sets undefined values to false.
It should not. It should ignore unset values.
In addition, it should allow the values to be locked or unlocked.
| Assignee | ||
Comment 1•6 years ago
|
||
I remember why I did it this way. Many of the sanitize values default to true. So if you just flip privacy.sanitize.sanitizeOnShutdown, lots of things will get cleared by default.
I think just adding the ability to not lock the prefs is enough (and fix the GPO so you can choose to not define things)
| Assignee | ||
Updated•6 years ago
|
| Assignee | ||
Comment 2•6 years ago
|
||
| Assignee | ||
Comment 3•6 years ago
|
||
This is what I should have done initially. Allow locking and only lock explicit values. And flip the true values to false so that setting sanitizeonshutdown doesn't delete everything when you set one thing.
| Assignee | ||
Comment 4•6 years ago
|
||
Updated•6 years ago
|
Comment 6•6 years ago
|
||
| bugherder | ||
| Assignee | ||
Comment 7•6 years ago
|
||
Comment on attachment 9126240 [details]
Bug 1613722 - Allow sanitize policy to be unlocked. r?mconley
Beta/Release Uplift Approval Request
- User impact if declined: SanitizeOnShutdown policy can't be unlocked, a little clunky
- Is this code covered by automated tests?: Yes
- Has the fix been verified in Nightly?: No
- Needs manual test from QE?: No
- If yes, steps to reproduce:
- List of other uplifts needed: None
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Policy only. Automated test, existing behavior unchanged.
- String changes made/needed:
ESR Uplift Approval Request
- If this is not a sec:{high,crit} bug, please state case for ESR consideration: Policy, customer requested feature.
- User impact if declined: SanitizeOnShutdown policy can't be unlocked, a little clunky
- Fix Landed on Version: 75
- Risk to taking this patch: Low
- Why is the change risky/not risky? (and alternatives if risky): Policy only. Automated test, existing behavior unchanged.
- String or UUID changes made by this patch:
Comment on attachment 9126240 [details]
Bug 1613722 - Allow sanitize policy to be unlocked. r?mconley
Looks safe for beta, uplift approved for 74.0b6, thanks.
Comment 9•6 years ago
|
||
| bugherder uplift | ||
Comment 10•6 years ago
|
||
Comment on attachment 9126240 [details]
Bug 1613722 - Allow sanitize policy to be unlocked. r?mconley
Policy engine update, approved for 68.6esr.
Comment 11•6 years ago
|
||
| bugherder uplift | ||
Description
•