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

Closed (moved)
Open
Opened Oct 24, 2018 by Alexander Færøy@ahf🍍Developer

Signal mechanism from PT processes to Tor

Once #28179 (moved) is done we now have bi-directional communication between the PT process and Tor itself.

We need a method where a PT process can signal to Tor different events that has occurred. This could be things like "Unable to connect to {host}:{port}".

Once we receive these messages from the PT we should expose them via the ControlPort for Tor Browser and friends to be able to act upon them.

This ticket is a tracker ticket for all of this work. Ideally we need to figure out the right way to do this mechanism (is it an update to the PT spec?) and we might also want to update goptlib to support this feature to let PT developers use it right away.

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