Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
  • #6541

Closed (moved)
(moved)
Open
Created Aug 03, 2012 by Peter Eckersley@pde

Make Decentralized SSL Observatory / Tor interoperability sane again

The Decentralized SSL Observatory has an option to use Tor (via Torbutton) for strongly anonymised submissions of X.509 certs. Unfortunately, when Torbutton switched to being "always on", users lost the ability to use the Observatory all the time with Tor acting as the background submission method.

So what we should do is pull the components out of Torbutton that detect a local Tor instance, see if the regular and Tor Browser Bundle Tor proxy ports are open, ping check.torproject.org over those, and determine whether Tor is locally available that way.

I will also replace "Torbutton" with "Tor" in the UI when that patch is ready.

(This is blocking 3.0 stable, because all of the advice in the UI about Tor and the Observatory is currently weird/wrong, and lots more people will see that advice when 3.0 stable ships)

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