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

Closed (moved)
Open
Opened Oct 09, 2010 by Steven Murdoch@sjm217

Make tor_check_port_forwarding more generic

tor_check_port_forwarding() in util.c contains both code specific to tor-fw-helper as well as generic code for launching a child process. It might be useful to make this more generic so it could be used for launching other processes.

On this topic, in bug #1903 (moved), nickm said:

It seems that the code here does two things: one is a general task "Launch a child process and see what it says" and another is a more specific task "Launch a tor-fw-helper instance and act based on its output.)" It might be a good idea to disentangle these eventually, in case we ever want to launch anything else.

It might be cleaner to move the static variables from tor_check_port_forwarding into some kind of struct, in case we ever want to launch two things in the future.

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