-
Notifications
You must be signed in to change notification settings - Fork 2.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Manually revert the Windows only DNS over HTTP work-around (for Brave VPN) #25488
Labels
Milestone
Comments
25 tasks
7 tasks
The above requires |
Verification
Reproduced using STR from the description #25488 (comment) using
Steps:
|
stephendonner
added
the
QA/In-Progress
Indicates that QA is currently in progress for that particular issue
label
Oct 3, 2022
Verification
|
Brave | 1.45.84 Chromium: 106.0.5249.91 (Official Build) beta (x86_64) |
---|---|
Revision | fa96d5f07b1177d1bf5009f647a5b8c629762157-refs/branch-heads/5249@{#707} |
OS | macOS Version 11.7 (Build 20G817) |
Steps:
- installed
1.45.84
- launched Brave
- purchased and set up Brave VPN
- connected to the
USA (Central)
region - opened
brave://settings/security
- confirmed
Use secure DNS
defaults toON
- confirmed
With your current service provider
radio button is selected - loaded
browserleaks.com/dns
steps 1-4 | steps 5-7 | step 8 |
---|---|---|
Confirmed no "local" (ISP, i.e. non-VPN-region) DNS-server addresses shown as all DNS queries are resolved by the VPN as expected
Verification
|
Brave | 1.45.84 Chromium: 106.0.5249.91 (Official Build) beta (64-bit) |
---|---|
Revision | fa96d5f07b1177d1bf5009f647a5b8c629762157-refs/branch-heads/5249@{#707} |
OS | Linux |
NOTE: VPN is disabled and unavailable on Linux.
This is a regression test to ensure we don't regress DNS-over-HTTP/leaks.
1.44.103
Case 1: Use secure DNS
ON
, no DoH server - PASSED
Steps:
- installed 1.44.103
- launched Brave
- opened
brave://settings/security
- confirmed
Use secure DNS
was set toEnabled
- confirmed
With your current service provider
radio button was selected - loaded
browserleaks.com/dns
Confirmed I saw my local ISP's DNS resolvers listed
brave://settings/security |
browserleaks.com/dns |
---|---|
Case 2: Use secure DNS
ON
, CleanBrowsing
DoH set - PASSED
Steps:
- installed 1.44.103
- launched Brave
- opened
brave://settings/security
- confirmed
Use secure DNS
was set toEnabled
- set the radio button to
With CleanBrowsing (Family Filter)
- loaded
browserleaks.com/dns
Confirmed I did NOT see my local ISP's DNS resolvers listed
brave://settings/security |
browserleaks.com/dns |
---|---|
1.45.84
Case 1: Use secure DNS
ON
, no DoH server - PASSED
Steps:
- installed
1.45.84
- launched Brave
- opened
brave://settings/security
- confirmed
Use secure DNS
was set toEnabled
- set the radio button to
With CleanBrowsing (Family Filter)
- loaded
browserleaks.com/dns
Confirmed I saw my local ISP's DNS resolvers listed
brave://settings/security |
browserleaks.com/dns |
---|---|
Case 2: Use secure DNS
ON
, CleanBrowsing DoH set - PASSED
Steps:
- installed
1.45.84
- launched Brave
- opened
brave://settings/security
- confirmed
Use secure DNS
was set toEnabled
- set the radio button to
With CleanBrowsing (Family Filter)
- loaded
browserleaks.com/dns
Confirmed I did NOT see my local ISP's DNS resolvers listed
brave://settings/security |
browserleaks.com/dns |
---|---|
stephendonner
added
QA Pass-Linux
and removed
QA/In-Progress
Indicates that QA is currently in progress for that particular issue
labels
Oct 3, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Description
We should manually revert the logic introduced in brave/brave-core#13434
Basically, Windows can leak your ISP due to
Smart Multi-Homed Name Resolution
(even when you're on VPN). This is a feature of Windows and is expected behavior. See #22163 for full details. During security review, we came up with a plan that attempted to solve this. If users aren't already using DNS over HTTP, it would enable this (on Windows only). When disconnecting from VPN, it would revert that config change.This approach has a few problems
Steps to Reproduce
Actual result:
DNS over HTTP defaults to
1.1.1.1
and becomes enabledExpected result:
DNS over HTTP should not be affected
Reproduces how often:
100%
The text was updated successfully, but these errors were encountered: