Open Bug 1657568 Opened 6 months ago Updated 5 months ago

Sync more preferences in Privacy & Security

Categories

(Firefox :: Sync, enhancement, P3)

enhancement

Tracking

()

REOPENED
81 Branch
Tracking Status
firefox81 --- affected

People

(Reporter: a.polivanchuk, Assigned: a.polivanchuk, Mentored)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Some preferences in the Privacy & Security section of Firefox settings are not synchronized by default.
1. Enable HTTPS-Only Mode in all windows
data-l10n-id="httpsonly-radio-enabled"
2. Enable HTTPS-Only Mode in private windows only
data-l10n-id="httpsonly-radio-enabled-pbm"
3. Don’t enable HTTPS-Only Mode
data-l10n-id="httpsonly-radio-disabled"

preference="dom.security.https_only_mode"

Add new strings to the section // Preferences to be synced by default:
mozilla-central/browser/app/profile/firefox.js
pref("services.sync.prefs.sync.dom.security.https_only_mode", true);
pref("services.sync.prefs.sync.dom.security.https_only_mode_ever_enabled", true);
pref("services.sync.prefs.sync.dom.security.https_only_mode_ever_enabled_pbm", true);
pref("services.sync.prefs.sync.dom.security.https_only_mode_pbm", true);

 4. Query OCSP responder servers to confirm the current validity of certificates
     data-l10n-id="certs-enable-ocsp"
     preference="security.OCSP.enabled"

Add new strings to the section // Preferences to be synced by default:
mozilla-central/browser/app/profile/firefox.js
pref("services.sync.prefs.sync.security.OCSP.enabled", true);

 5. Prevent accessibility services from accessing your browser (requires browser restart)
     data-l10n-id="permissions-a11y-privacy-checkbox"
     checkbox id="a11yPrivacyCheckbox"
     preference="accessibility.force_disabled"

Add new strings to the section // Preferences to be synced by default:
mozilla-central/browser/app/profile/firefox.js
pref("services.sync.prefs.sync.accessibility.force_disabled", true);

 6. Warn you about unwanted and uncommon software
     data-l10n-id="security-block-uncommon-software"
     checkbox id="blockUncommonUnwanted"
     preference="browser.safebrowsing.downloads.remote.block_potentially_unwanted"

Add new strings to the section // Preferences to be synced by default:
mozilla-central/browser/app/profile/firefox.js
pref("services.sync.prefs.sync.browser.safebrowsing.downloads.remote.block_potentially_unwanted", true);

 7. Block dangerous downloads
     data-l10n-id="security-block-downloads"
     checkbox id="blockDownloads"
     preference="browser.safebrowsing.downloads.enabled"

Add new strings to the section // Preferences to be synced by default:
mozilla-central/browser/app/profile/firefox.js
pref("services.sync.prefs.sync.browser.safebrowsing.downloads.enabled", true);

 8. Block dangerous and deceptive content
     data-l10n-id="security-enable-safe-browsing"
     checkbox id="enableSafeBrowsing"
     preference="browser.safebrowsing.phishing.enabled"
     preference="browser.safebrowsing.malware.enabled"

Add new strings to the section // Preferences to be synced by default:
mozilla-central/browser/app/profile/firefox.js
pref("services.sync.prefs.sync.browser.safebrowsing.phishing.enabled", true);
pref("services.sync.prefs.sync.browser.safebrowsing.malware.enabled", true);

Please review my proposed changes for further file modification in the repo.

Sure, we could definitely do 1-3 and 6-8!

I'm less sure about 4 and 5, though. Syncing the OCSP checkbox should be safe in theory, but I'm worried that a misconfigured proxy or other settings might interact badly with it. At one time, we used to sync the TLS version, and stopped because accidentally setting the wrong thing on one device would spread to the others, making it so Firefox couldn't connect to most sites at all. With 5, a11y software is different between systems, and I'd be cautious of the same thing happening—we don't want to make someone's Firefox unusable everywhere.

Priority: -- → P3

I've submitted a patch with new lines for all proposed preferences excluding steps 4 and 5.
Should we take a closer look at the possible issues 4 and 5 might cause? Or just not include them to the default sync?

(In reply to Artem Polivanchuk from comment #3)

Should we take a closer look at the possible issues 4 and 5 might cause? Or just not include them to the default sync?

Yeah, would you mind filing another bug for those, so we can discuss more? Meanwhile, we can land the patch you just uploaded. Thanks! 😊

Pushed by kcambridge@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/6c39cafd999e
Sync more preferences in Privacy & Security r=lina DONTBUILD
Status: NEW → RESOLVED
Closed: 6 months ago
Resolution: --- → FIXED
Target Milestone: --- → 81 Branch

During my test on the latest nightly, synchronization of preferences 6, 7 and 8 was failed.
Could you please take a closer look at the prefs? Maybe there's something more complicated than just adding new lines...

Flags: needinfo?(lina)

(In reply to Artem Polivanchuk from comment #7)

During my test on the latest nightly, synchronization of preferences 6, 7 and 8 was failed.
Could you please take a closer look at the prefs? Maybe there's something more complicated than just adding new lines...

I think you can probably do some diagnosis of that. If you manually change those preferences, does the feature toggle as expected? If not, then it's not as simple as just syncing prefs and we'll need to rethink. If it does work manually, then you can check whether the preference syncing worked by checking if the preference changes values after a sync. You can use the about:sync addon to see what the value for the pref is on the server.

Flags: needinfo?(lina) → needinfo?(a.polivanchuk)

I've tested in the latest Nightly as you suggested.
When I change the preference in the Privacy & Security section of the Settings menu it reflects in about:config
When I change the preference in about:config it doesn't reflect the change in the Settings menu.

Switching the preferences in about:config successfully synced and reflected on the other Nightly instance but nothing changed in the Settings menu as well.

Status: RESOLVED → REOPENED
Flags: needinfo?(a.polivanchuk)
Resolution: FIXED → ---
You need to log in before you can comment on or make changes to this bug.