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

Closed (moved)
Open
Opened Oct 05, 2012 by Peter Eckersley@pde

[SSL Observatory] localhost Tor detection breaks once the user has picked "submit certs without Tor"

The way that submitting certs directly is implemented in the observatory is by setting use_custom_proxy to True and configuring the proxy to be a passthrough.

But that state confuses the code that tries to tell whether Tor is available for routing Observatory requests:

https://gitweb.torproject.org/https-everywhere.git/blob/HEAD:/src/components/ssl-observatory.js#l734

What that means is if the user picks "submit certs even if Tor is not available", then next time they restart Firefox, "submit through Tor" will no longer be an option though Tor is running on localhost:9050.

I think this blocks 3.0 stable.

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