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

Re: [tor-bugs] #13213 [Tor]: Tor should tell its pluggable transports when DisableNetwork gets set/unset

#13213: Tor should tell its pluggable transports when DisableNetwork gets set/unset
------------------------+--------------------------------
     Reporter:  arma    |      Owner:
         Type:  defect  |     Status:  needs_review
     Priority:  normal  |  Milestone:  Tor: 0.2.6.x-final
    Component:  Tor     |    Version:
   Resolution:          |   Keywords:  tor-pt
Actual Points:          |  Parent ID:
       Points:          |
------------------------+--------------------------------
Changes (by yawning):

 * status:  new => needs_review


Comment:

 So this was a lot easier than I thought it would be, since the way tor
 handles pt configuration is to mark all running instances for termination,
 and selectively re-enable them based on the new config.

 https://github.com/yawning/tor/tree/bug13213

 With my branch, when DisableNetwork is set, PTs will not be launched, and
 any existing client/server plugins will be terminated.  It additionally
 does not affect the validation of said config directives. Tested with
 `kill -HUP`, `vi`, and `ps`.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/13213#comment:6>
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