Maybe change user's default DoH region when the user is roaming
Categories
(Core :: Networking: DNS, task, P2)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox123 | --- | fixed |
People
(Reporter: kershaw, Assigned: valentin)
References
(Blocks 1 open bug)
Details
(Whiteboard: [necko-triaged][necko-priority-queue])
Attachments
(1 file)
We should consider switching the user's local DoH provider when we detect that the user is in a roaming state.
| Assignee | ||
Comment 1•2 years ago
|
||
For context, we have this code in DoHConfig:
async loadRegion() {
await new Promise(resolve => {
let homeRegion = lazy.Preferences.get(`${kGlobalPrefBranch}.home-region`);
if (homeRegion) {
kRegionPrefBranch = `${kGlobalPrefBranch}.${homeRegion.toLowerCase()}`;
resolve();
return;
}
So what we do is if we don't have the pref set, we compute the region store it as a pref, and use that from then forward.
Problem is if a user from Canada travels to Australia, they will still use the canadian DoH providers with additional latency.
A better approach would probably be to use the region stored as a pref, but also do one region check per session and store that in the pref, so at the next run you'll use the correct region and DoH providers.
Or maybe we can think of an even better design.
| Assignee | ||
Comment 2•2 years ago
|
||
The DoHConfig now listens for region change notification and
saves the new region in a pref. On the next initialization of
the DoH config we will use the saved pref to update the doh
region even if the pref was already set.
This should also work for testing (manually setting the value of the
pref) as long as no region changes happen.
Updated•2 years ago
|
Comment 3•2 years ago
|
||
Could we get loud and clear notification when the config is automatically modified, please?
| Assignee | ||
Comment 4•2 years ago
|
||
(In reply to Petr Špaček from comment #3)
Could we get loud and clear notification when the config is automatically modified, please?
What do you mean?
Comment 5•2 years ago
|
||
Let me rephrase. If Firefox is switching to a different DoH provider automatically, I as an user want to know that it has happened.
| Assignee | ||
Comment 6•2 years ago
|
||
This only happens for users under the Default Protection (network.trr.mode = 0) setting in about:preferences#privacy
In that mode Firefox configures the DoH server automatically based on your region.
What this fix does is that if your original region was detected as US, upon travelling to Germany or Canada, Firefox would not keep using the default DoH settings for US.
This change does not affect users who selected Increased protection or Max protection, or Off. It would also not change anything if you manually set a custom DoH URL.
Comment 7•2 years ago
|
||
Aha! Thank you for clarification. That was not clear from the title "Maybe change user's local DoH provider when the user is roaming". Maybe stuff a word "default" somewhere to the title?
Thank you for your time.
| Assignee | ||
Updated•2 years ago
|
Comment 9•2 years ago
•
|
||
Backed out for causing bc failures on browser_doorhangerUserReject.js
Comment 10•2 years ago
|
||
There is an r+ patch which didn't land and no activity in this bug for 2 weeks.
:valentin, could you have a look please?
If you still have some work to do, you can add an action "Plan Changes" in Phabricator.
For more information, please visit BugBot documentation.
| Assignee | ||
Updated•2 years ago
|
Comment 11•2 years ago
|
||
Comment 12•2 years ago
|
||
| bugherder | ||
Description
•