Add a pref to toggle whether to clear doh-rollout.mode at shutdown
Categories
(Firefox :: Security, task, P1)
Tracking
()
People
(Reporter: valentin, Assigned: nhnt11)
References
(Blocks 1 open bug)
Details
Attachments
(2 files)
|
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
|
47 bytes,
text/x-phabricator-request
|
jcristau
:
approval-mozilla-beta+
|
Details | Review |
Currently in DoHController.jsm we clear the TRR mode at shutdown.
We should reconsider doing this, as this means starting up the browser would always happen in mode0, followed by the heuristics and confirmation. This means we're skipping TRR for a lot of name resolutions that would otherwise use it during start-up.
I assume the reason we have it structured this way is that we can't be sure that when starting up we will be on the same network - but in my opinion that is by far the most common scenario. There's nothing preventing us from running heuristics after startup and clearing the mode if necessary. We should of course make this a pref to revert behaviour if any fallout occurs.
There is one scenario where this new behaviour might be problematic and that is with TRR steering. Since the steering URI is autodetected during heuristics, and not permanent, at startup we'd start in mode2 - use the default provider, then run the heuristics and switch to ISP's TRR server. Not great, but I think we can improve this.
| Reporter | ||
Updated•5 years ago
|
| Assignee | ||
Comment 1•5 years ago
|
||
Comment 3•5 years ago
|
||
Backed out for perma failures.
Log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=316388726&repo=autoland&lineNumber=4439
Backout: https://hg.mozilla.org/integration/autoland/rev/22d6270a11aaf468c3fbc7576632598b38b3bf00
Comment 5•5 years ago
•
|
||
Backed out changeset fccbbed6fc57 (bug 1662430) for Browser-chrome failures in preferences/tests/browser_connection_dnsoverhttps.js. CLOSED TREE
Log:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=316570502&repo=autoland&lineNumber=5330
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=316567499&repo=autoland&lineNumber=5323
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=316570497&repo=autoland&lineNumber=11521
Push with failures:
https://treeherder.mozilla.org/#/jobs?repo=autoland&group_state=expanded&revision=fccbbed6fc57cf1ff0c436d4d7c578fa4fcabd9c
Backout:
https://hg.mozilla.org/integration/autoland/rev/c872d7d3ebd8b6ec002ebe43b64ec0e845157185
| Assignee | ||
Comment 6•5 years ago
|
||
Tests are passing for me locally... hmm. Gotta dig into this.
| Assignee | ||
Comment 7•5 years ago
|
||
Happily, at least the browser_rollback.js failure is reproducible locally after I rebased the patch on the latest central tip! The preferences test could be breaking as a result of broken state left behind by that test perhaps... digging.
| Assignee | ||
Comment 8•5 years ago
|
||
The DoHConfig.jsm patch landed before this which necessitated a couple of test updates. I'm expecting the preferences test to "just work" with these, but if it fails I'll know there's something strange going on (still can't repro that one locally on its own).
https://treeherder.mozilla.org/#/jobs?repo=try&revision=5e6cda146117d0b884b9795affc8b0926511c463
| Assignee | ||
Comment 9•5 years ago
•
|
||
Preferences test still failing. New theory is that the change I made can result in a promise being created that's waiting on a pref observer that never trips - so the promise never resolves and the observer is never cleaned up.
https://treeherder.mozilla.org/#/jobs?repo=try&revision=96f533c7e7c3464c4ba292a7b62cd049f0f59fac
| Assignee | ||
Comment 10•5 years ago
|
||
That did the trick.
Comment 11•5 years ago
|
||
Comment 12•5 years ago
•
|
||
Backed out for perma failures.
Logs:
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=316611284&repo=autoland&lineNumber=5047
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=316609318&repo=autoland&lineNumber=5317
https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=316611358&repo=autoland&lineNumber=11825
Backout: https://hg.mozilla.org/integration/autoland/rev/5ef88e585fe8862d9109cf4c18b43c7e9564309f
| Assignee | ||
Comment 13•5 years ago
|
||
Ugh, I'm not having a good time with this patch. I didn't push the updated patch to phabricator, so the old version of the patch that was failing got re-landed. My apologies to the trees for the wasted CPU cycles on this one...
Comment 14•5 years ago
|
||
Comment 15•5 years ago
|
||
| bugherder | ||
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Comment 16•5 years ago
|
||
Comment on attachment 9176876 [details]
Bug 1662430 - Allow a pref to toggle whether to clear doh-rollout.mode at shutdown. r=valentin!
Beta/Release Uplift Approval Request
- User impact if declined: Currently we are seeing evidence that a significant number of DNS lookups that happen around startup are not using DoH because the heuristics haven't had time to run yet. By not clearing state at shutdown, we'll attempt to use DoH at startup if it was turned on in the previous session. The patch allows us to control this with a pref, and we want to use this to experiment on Release. In bug 1668104, we'll turn this on by default in Nightly and Beta.
- 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: Medium
- Why is the change risky/not risky? (and alternatives if risky): This is not a simple cosmetic change, but it's also not very complex. Automated tests are in place. The change can be controlled via a pref.
- String changes made/needed:
Updated•5 years ago
|
Comment 17•5 years ago
|
||
Comment on attachment 9176876 [details]
Bug 1662430 - Allow a pref to toggle whether to clear doh-rollout.mode at shutdown. r=valentin!
approved for 82.0b6
Comment 18•5 years ago
•
|
||
Backed out changeset 8223f59a9c62 (Bug 1662430) for causing failures in browser_policyOverride.js a=backout
Failure log: https://treeherder.mozilla.org/logviewer.html#/jobs?job_id=317155831&repo=mozilla-beta&lineNumber=11626
Backout: https://hg.mozilla.org/releases/mozilla-beta/rev/49a013c7f6cacc1b28ba3878dc5fe958fc3badbb
Comment 19•5 years ago
|
||
This previously landed in:
https://hg.mozilla.org/releases/mozilla-beta/rev/8223f59a9c62
Comment 20•5 years ago
|
||
Comment on attachment 9176876 [details]
Bug 1662430 - Allow a pref to toggle whether to clear doh-rollout.mode at shutdown. r=valentin!
Clearing the approval flag so this doesn't show up as pending uplift.
| Assignee | ||
Comment 21•5 years ago
|
||
Depends on D90856
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Comment 22•5 years ago
|
||
Comment on attachment 9179545 [details]
Bug 1662430 - [Beta only] Expect the correct events in DoH tests in beta. r=valentin!
Beta/Release Uplift Approval Request
- User impact if declined: See comment 16
- 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: See comment 16
- List of other uplifts needed: None
- Risk to taking this patch: Medium
- Why is the change risky/not risky? (and alternatives if risky): See comment 16
- String changes made/needed:
| Assignee | ||
Updated•5 years ago
|
| Assignee | ||
Comment 23•5 years ago
|
||
Please note: D92398 is not landing in central. It's a patch that makes D90856 compatible with current beta.
Comment 24•5 years ago
|
||
Comment on attachment 9176876 [details]
Bug 1662430 - Allow a pref to toggle whether to clear doh-rollout.mode at shutdown. r=valentin!
let's try this again for 82.0b8.
Updated•5 years ago
|
Comment 25•5 years ago
|
||
| bugherder uplift | ||
https://hg.mozilla.org/releases/mozilla-beta/rev/266dd87d4ecd
https://hg.mozilla.org/releases/mozilla-beta/rev/8c4884dfe844
Description
•