Infosec Handbook Review Issues : “.... /e/ .. using Google for connectivity check:”
[These issues are created out of the Infosec Handbook review conducted on March 15, 2019. ]
(Issue title)
Infosec Handbook Review Issues : “We monitored all data connections of /e/ after restarting the phone. First of all, /e/ knocks on Google’s door by using its connectivity check:”
Summary
The infosec Handbook monitored all data connections the /e/ OS made after restarting and found calls to Google servers
Steps to reproduce
Read the Infosec handbook article here + We monitored all data connections of /e/ after restarting the phone. First of all, /e/ knocks on Google’s door by using its connectivity check:
- GET /generate_204 HTTP/1.1
- User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/52.0.2743.82 Safari/537.36
- Host: connectivitycheck.gstatic.com
- Connection: Keep-Alive
- Accept-Encoding: gzip
What is the current behavior?
Calls are being made to Google
What is the expected correct behavior?
There should not be any Google calls.
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)
Possible fixes
(If you can, link to the line of code that might be the cause for this problem)