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
  • #7151

Closed (moved)
Open
Opened Oct 19, 2012 by cypherpunks@cypherpunks

SSL Observatory not using Tor when FoxyProxy is enabled

When FoxyProxy is enabled, and the SSL Observatory is enabled and set to use Tor, access to the Observatory seems to use FoxyProxy's rules instead of going through Tor, without HTTPS Everywhere noticing.

A workaround is to add the Tor proxy to FoxyProxy and a rule to use that for access to observatory.eff.org, but that will only work while in FoxyProxy's default mode.

If there's no way for HTTPS Everywhere to override FoxyProxy, then maybe it should at least test that access through Tor actually works as intended before submitting certificates.

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#7151