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

Re: [tor-bugs] #17873 [Tor]: replacing 0.0.0.0 listeners at runtime fails

#17873: replacing 0.0.0.0 listeners at runtime fails
-------------------------+------------------------------------
 Reporter:  cypherpunks  |          Owner:
     Type:  defect       |         Status:  new
 Priority:  Low          |      Milestone:  Tor: 0.2.8.x-final
Component:  Tor          |        Version:
 Severity:  Minor        |     Resolution:
 Keywords:  easy         |  Actual Points:
Parent ID:               |         Points:
  Sponsor:               |
-------------------------+------------------------------------

Comment (by cypherpunks):

 Requiring a restart to change this setting might be OK, but exiting
 because of an "invalid config" doesn't seem OK to me. For remote machines
 that are only reachable via hidden service SSH, it can actually be
 extremely inconvenient/expensive.

 Is there any ticket about making it safer to reload the config, eg,
 falling back to the previously-read config if the new one fails?

 Regardless of that, loading carefully-tested known-to-be-valid configs
 should not cause tor to exit!

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