Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • B Backlog
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 1,502
    • Issues 1,502
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • e
  • Backlog
  • Issues
  • #271

Closed
Open
Created Apr 10, 2019 by Manoj Nair@manojnairDeveloper

Infosec Handbook Review Issues : “...TLS 1.2-encrypted traffic from/to www.google.com.... via IPv4/IPv6.”

[These issues are created out of the Infosec Handbook review conducted on March 15, 2019. ]

(Issue title)

Infosec Handbook Review Issues : “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.”

Summary

Infosec Handbook Review Issues : “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.”

Steps to reproduce

read the Infosec Handbook review here

What is the current behavior?

TLS encrypted calls to and from google web addresses as mentioned above.

What is the expected correct behavior?

The calls should not take place.

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)

Assignee
Assign to
Time tracking