Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • 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
  • #21967
Closed (moved) (moved)
Open
Issue created Apr 17, 2017 by George Kadianakis@asn

obfs4proxy not killed when unused

Seems like Tor does not successfuly kill obfs4proxy when it's no longer used. It's unclear why. Maybe obfs4proxy never receives the SIGTERM, or never notices that the stdin is closed?

Experiment:

  • Startup Tor Browser using default obfs4 bridges.
  • Check that obfs4proxy process has spawned (ps -fax | grep obfs)
  • Reconfigure Tor Browser to not use bridges at all.
  • Check that obfs4proxy process is still there...
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking