TRR canary check returns "disable_doh" if the DNS request fails
Categories
(Firefox :: Security, defect, P1)
Tracking
()
Tracking | Status | |
---|---|---|
firefox79 | --- | fixed |
People
(Reporter: tdsmith, Assigned: nhnt11)
References
Details
(Whiteboard: [necko-triaged][trr])
Attachments
(1 file)
The application DNS canary check in the DoH rollout addon returns disable_doh
if the DNS request fails (for example, because the network is disconnected). These are probably inflating our disable rates.
I think the check should only return disable_doh
if the check affirmatively fails according to the criteria in https://support.mozilla.org/en-US/kb/canary-domain-use-application-dnsnet.
STR:
- Visit about:devtools-toolbox?type=extension&id=doh-rollout@mozilla.org and run
await globalCanary()
in the console; result should beenable_doh
. - Disconnect the network.
- Repeat. Expected result to be
enable_doh
; result wasdisable_doh
.
Comment 1•5 years ago
|
||
needinfo Nihanth and cc Dragana and Valentin.
Updated•5 years ago
|
Updated•5 years ago
|
Assignee | ||
Comment 2•5 years ago
|
||
Hmm, we aren't running heuristics until the network goes up. Is there any other situation in which this could result in a false-negative?
Reporter | ||
Comment 3•5 years ago
|
||
I'm not sure. My concern is that a consistent baseline of 20-30% of heuristics evaluations on all networks report that the canary is disabling DoH, which seems unlikely to me, and this looked like a potential cause. This could be spurious but I'm suspicious of it.
Assignee | ||
Updated•5 years ago
|
Assignee | ||
Comment 5•5 years ago
|
||
Updated•5 years ago
|
Assignee | ||
Updated•5 years ago
|
Comment 7•5 years ago
|
||
bugherder |
Updated•5 years ago
|
Comment 8•5 years ago
|
||
Hello,
Im trying to verify this bug. On 79.0b9 if I repeat the steps (As i understand the steps I must be disconnected from the network when running await globalCanary()
) if that's the case I can still reproduce this issue.
Assignee | ||
Comment 9•5 years ago
|
||
Daniel, if that code is called when network is disconnected, the canary heuristic will still fail.
The patch in this bug simply tries to ensure that we don't call the code when the network is down.
This situation will be further improved in bug 1654520.
Comment 10•5 years ago
|
||
Hello,
Understood, will remove the qe+ flag from the bug.
Description
•