Hosts file no longer blocks some sites since native HTTPS resolver was enabled on Ubuntu
Categories
(Core :: Networking: DNS, defect, P2)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox125 | --- | disabled |
firefox126 | --- | disabled |
firefox127 | --- | affected |
People
(Reporter: ke5trel, Assigned: kershaw)
References
(Blocks 1 open bug, Regression, )
Details
(Keywords: regression, Whiteboard: [necko-triaged])
Attachments
(1 file)
15.06 KB,
image/png
|
Details |
STR:
- Block
www.youtube.com
using/etc/hosts
on Ubuntu 23.10. - Set DoH to Off.
- Visit
www.youtube.com
.
Site loads instead of being blocked.
Other sites like www.facebook.com
can still be blocked.
Using about:networking#dnslookuptool
returns:
IPs
127.0.0.1
HTTP RRs
1 youtube-ui.l.google.com ()
Adding youtube-ui.l.google.com
to the hosts file allows the block to work.
Changing network.dns.native_https_query = false
stops returning HTTP RRs and avoids the issue.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=4c5285764100fef7429262fb418cb665ea747427&tochange=8a936faee760859d530e2fbc7d8ac3d0294385b5
Regressed by Bug 1874464.
Comment 1•1 year ago
|
||
:valentin, since you are the author of the regressor, bug 1874464, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
Comment 2•1 year ago
|
||
It seems this is caused by this line.
We're using the CNAME returned in the HTTPS record for the new connection info, that means we end up using youtube-ui.l.google.com
instead of www.youtube.com
in the connection info.
HTTPSSVC: use new routed host (youtube-ui.l.google.com) and new npnToken (None)
Potential solutions:
- wait for IP lookups to complete before using HTTPS record (but even if they do, and point to 127.0.0.1, we might have to make a decision whether to use it).
- Not do HTTPS lookups for domains that have an entry in /etc/hosts
- something else?
Kershaw, what do you think?
Assignee | ||
Comment 3•1 year ago
|
||
- Not do HTTPS lookups for domains that have an entry in /etc/hosts
I think this is the easiest approach to be implemented and is less likely to cause any regression.
I'll take this bug.
Comment 4•1 year ago
|
||
Do you have the necessary read permissions on a sandboxed system like Android?
Updated•1 year ago
|
Updated•1 year ago
|
Comment 5•1 year ago
|
||
Setting 126 to disabled by Bug 1893970
Assignee | ||
Comment 6•1 year ago
|
||
FYI, this one should be fixed by bug 1893944.
Assignee | ||
Updated•1 year ago
|
Description
•