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

Closed (moved)
(moved)
Open
Created Mar 24, 2018 by David Fifield@dcf

tor sets `TOR_PT_EXIT_ON_STDIN_CLOSE=1` only for server transports, not client transports

At comment:2:ticket:24642, we were surprised to find that server transports get TOR_PT_EXIT_ON_STDIN_CLOSE=1 set, and client transports do not.

https://gitweb.torproject.org/tor.git/tree/src/or/transports.c?id=9e8b762fcecfece64aae70ae640aaa59fd227ca5#n1387

We expected that it would be set for both. Client PTs have code to deal with TOR_PT_EXIT_ON_STDIN_CLOSE, which it turns out has been going unused.

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