#1922: torrc.d-style configuration directories ------------------------------+--------------------------------------------- Reporter: aa138346 | Type: enhancement Status: new | Priority: normal Milestone: Tor: unspecified | Component: Tor Client Version: | Keywords: Parent: | ------------------------------+---------------------------------------------
Comment(by arma): One answer here might be to let other applications modify Tor's config without needing to learn how to modify the torrc file. For example, we could imagine a 'tor-bridge' debian package that just adds a torrc.d/bridge-torrc file. Then you could become a bridge without needing a controller and without needing a text editor. We could also imagine a tor-relay deb. Weasel, what do you think of this idea? Are debs like this a good idea, or is this approach bad precedent because it would bloat the number of total debs in the world too far? It *might* also be useful for controllers like Vidalia on OSes where the Tor deb runs as a daemon and doesn't run as the user. In those cases we've talked about having Vidalia launch a script that prompts the user for her root password and then moves the new torrc file into place. Having it move its torrc into a Vidalia-specific name might keep things saner -- and might be doable without root if the torrc.d directory is owned by a group that the Vidalia deb puts the user into, as we might need to do to get !ControlSocket going. On the other hand, ultimately it might instead just complicate the issue further once there are two controllers that each write their own config file. If we do it, we'd want to sort out what to do if lines in different config files contradict each other. -- Ticket URL: <https://trac.torproject.org/projects/tor/ticket/1922#comment:2> Tor Bug Tracker & Wiki <https://trac.torproject.org/> The Tor Project: anonymity online _______________________________________________ tor-bugs mailing list [email protected] https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs
