Infosec Handbook Review Issues : “ /e/ uses Google’s DNS servers (e.g. 18.104.22.168) by default.”
[These issues are created out of the Infosec Handbook review conducted on March 15, 2019. ]
Infosec Handbook Review Issues : “Other users report that /e/ uses Google’s DNS servers (e.g. 22.214.171.124) by default.”
Infosec Handbook Review mentions that users have reported by checking /e/'s Gitlab that /e/ users report the use of google's DNS servers (126.96.36.199) as default and this has not be resolved.
Steps to reproduce
Read the InfoSec Handbook review here ....Since we only deploy our test devices in a controlled VLAN, we weren’t able to reproduce this. The settings allow you to set a default DNS resolver (Settings → Wireless & networks → More → DNS → disable “Use network DNS” → Set DNS to use). We tried this but the router enforces the DNS resolver of the network.
Moreover, there is TLS 1.2-encrypted traffic from/to www.google.com, gstaticadssl.l.google.com, googleadapis.l.google.com, and www3.l.google.com via IPv4/IPv6............
What is the current behavior?
Mentioned above in Steps to reproduce
What is the expected correct behavior?
Google DNS usage should not be available by default
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output,
logs, and code as it's very hard to read otherwise.)
(You can use
adb logcat command to capture log of you device, when connected to a computer)
(If you can, link to the line of code that might be the cause for this problem)