Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #7179

Closed (moved)
Open
Opened Oct 21, 2012 by Georg Koppen@gk

Ths SSL Observatory feature leaks DNS requests without the TBB

HTTPS-Everywhere is leaking DNS requests no matter whether I use Tor or not (but note that the TBB is not affected. See below for the reason). All tests were made in a clean new profile with FF 16.0.1 and HTTPS-E 3.0.2 installed.

The reason is that

Ci.nsIProxyInfo.TRANSPARENT_PROXY_RESOLVES_HOST

is not enough to be sure to not leak DNS requests if you build your proxy settings manually and using applyFilter(). This is actually a Mozilla (Necko) bug documented here:

https://bugzilla.mozilla.org/show_bug.cgi?id=536093

The only workaround I am currently aware of is setting "network.dns.disablePrefetch" to |true|, a thing which is done in the TBB. Then there are no requests leaking.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#7179