[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-bugs] #15434 [Tor]: Tor dies if you send it a HUP before it read its config, and doesn't take PTs with it

#15434: Tor dies if you send it a HUP before it read its config, and doesn't take
PTs with it
------------------------+-----------------------------
     Reporter:  TvdW    |      Owner:
         Type:  defect  |     Status:  new
     Priority:  normal  |  Milestone:
    Component:  Tor     |    Version:  Tor: 0.2.6.5-rc
   Resolution:          |   Keywords:
Actual Points:          |  Parent ID:
       Points:          |
------------------------+-----------------------------

Comment (by yawning):

 Somewhat related #5085.

 I believe the issue is generic, and not obfs4proxy specific on the pt
 side.  I suspect obfs4proxy is prone to displaying issues here because
 it's managing to get through the managed pt configuration protocol before
 tor crashes, while obfsproxy and fte (in the example), are slower to start
 up and fail to write the response over stdout.

 In theory something like #10047 could be done PT side if tor didn't close
 the stdin on the PT process, and I'm strongly tempted to add a
 "PT_EXIT_ON_STDIN_CLOSE" env var to the pt protocol to facilitate this.

 All of this is orthogonal to "tor shouldn't crash on an early HUP".

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/15434#comment:1>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs