Skip to content

Fix multiple DNS leaks#16

Open
liamsmith827 wants to merge 4 commits intoGrapheneOS:16-qpr2from
liamsmith827:16-qpr2_03-03_app-dns-leak
Open

Fix multiple DNS leaks#16
liamsmith827 wants to merge 4 commits intoGrapheneOS:16-qpr2from
liamsmith827:16-qpr2_03-03_app-dns-leak

Conversation

@liamsmith827
Copy link
Contributor

@liamsmith827 liamsmith827 commented Mar 7, 2026

This CL stops default (fallback) DNS servers being used for uids that have a lockdown VPN. This eliminates a serious DNS leak that can occur at tunnel creation time regardless of how the VPN is configured, and additional serious leaks that can occur when a VPN does not have DNS servers configured.

It also includes miscellaneous improvements to the VPN, such as stopping network identifiers from wrapping and crashing system_server if there are errors when setting up the lockdown VPN firewall.

This will not introduce any compatibility issues. Using fallback DNS is unreliable when there's a lockdown VPN, so VPN apps that depend on it already don't work in many cases.

GrapheneOS/platform_packages_modules_Connectivity#39
GrapheneOS/platform_packages_modules_DnsResolver#14

GrapheneOS/os-issue-tracker#5273

When a VPN app is doing DNS with its own tunnel servers, protecting that traffic
can result in the tunnel and tunnel DNS server IP addresses leaking. Any VPN app
that is setting tunnel DNS servers that aren't reachable through the tunnel is
already broken, as apps would be unable to do DNS when leak blocking is enabled.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant