Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • Trac Trac
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Service Desk
    • Milestones
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
  • Wiki
    • Wiki
  • Activity
  • Create a new issue
  • Issue Boards
Collapse sidebar
  • Legacy
  • TracTrac
  • Issues
  • #28125

Closed (moved)
(moved)
Open
Created Oct 19, 2018 by Matthew Finkel@sysrqb

Don't let Android leak DNS queries

In #27431 (moved) and #27375 (moved), it was reported Android is leaking DNS requests. From [ticket:27431#comment:1 27431], in summary:

This is exactly what we feared. It looks like this is the result
of a bug within the Android core HTTP library. This leak is already
fixed in the more recent releases of Android. In particular, any
version after Android O (API 26+) should not leak DNS queries.

We should patch TBA so it relies on the Android core library as little as possible. We don't need the fancy optimizations Android provide with request pools and such, so I think we can simply create and manage a proxy connection ourselves.

#27822 (moved) maybe related (but there isn't enough info available).

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking