Hello,
is it possible to include files into torrc? Something like this:
# /etc/tor/torrc ORPort 443 # Policies are kept in separate file for readability Include /etc/tor/policies
I checked https://www.torproject.org/docs/tor-manual.html.en but could not find anything. As an alternative, one can of course generate torrc from other files, but I'd rather use an include feature, if available.
-Ralph
Ralph,
I don't believe so based on what I've read. I have not personally tried it.
John
On Sep 9, 2016, at 13:23, Ralph Seichter tor-relays-ml@horus-it.de wrote:
Hello,
is it possible to include files into torrc? Something like this:
# /etc/tor/torrc ORPort 443 # Policies are kept in separate file for readability Include /etc/tor/policies
I checked https://www.torproject.org/docs/tor-manual.html.en but could not find anything. As an alternative, one can of course generate torrc from other files, but I'd rather use an include feature, if available.
-Ralph _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On 09 Sep (20:22:47), Ralph Seichter wrote:
Hello,
is it possible to include files into torrc? Something like this:
# /etc/tor/torrc ORPort 443 # Policies are kept in separate file for readability Include /etc/tor/policies
I checked https://www.torproject.org/docs/tor-manual.html.en but could not find anything. As an alternative, one can of course generate torrc from other files, but I'd rather use an include feature, if available.
Not possible to "include" sub torrc files unfortunately.
David
-Ralph _______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
On Friday 09 September 2016 20:22:47 Ralph Seichter wrote:
# /etc/tor/torrc ORPort 443 # Policies are kept in separate file for readability Include /etc/tor/policies
There is a ticket that handles this feature:
https://trac.torproject.org/projects/tor/ticket/1922
Regards,
torland
On 09.09.16 20:37, tor-admin@torland.is wrote:
There is a ticket that handles this feature: https://trac.torproject.org/projects/tor/ticket/1922
Thank you for pointing me to the issue tracker, and thanks also to the other list members who replied. I was pretty certain that I was not the first person to ask for such a feature.
-Ralph
On 10 Sep 2016, at 04:50, Ralph Seichter tor-relays-ml@horus-it.de wrote:
On 09.09.16 20:37, tor-admin@torland.is wrote:
There is a ticket that handles this feature: https://trac.torproject.org/projects/tor/ticket/1922
Thank you for pointing me to the issue tracker, and thanks also to the other list members who replied. I was pretty certain that I was not the first person to ask for such a feature.
-Ralph
If you're trying to apply the same policies across a number of relays on the same box, --defaults-torrc FILE can be used to provide default settings, and then each torrc can contain only the unique settings.
But on some OSs / distributions (like Debian), the defaults torrc file is in /usr/share/tor, not /etc/tor.
So if you want to modify it permanently, you'll need to protect that file from your package manager (using something like dpkg-divert), or change the --defaults-torrc path in your service manager (and if you're on Debian, that file is in /lib/systemd/system, and so you'll need to do dpkg-divert on it).
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B ricochet:ekmygaiu4rzgsk6n xmpp: teor at torproject dot org
If you're trying to apply the same policies across a number of relays on the same box, --defaults-torrc FILE can be used to provide default settings, and then each torrc can contain only the unique settings.
But on some OSs / distributions (like Debian), the defaults torrc file is in /usr/share/tor, not /etc/tor.
So if you want to modify it permanently, you'll need to protect that file from your package manager (using something like dpkg-divert), or change the --defaults-torrc path in your service manager (and if you're on Debian, that file is in /lib/systemd/system, and so you'll need to do dpkg-divert on it).
Instead of modifying the shipped unit file + dpkg-* you can also replace specific unit file settings using the so called drop-in files:
systemd.unit man page (debian stable):
Along with a unit file foo.service, a directory foo.service.d/ may exist. All files with the suffix ".conf" from this directory will be parsed after the file itself is parsed. This is useful to alter or add configuration settings to a unit, without having to modify their unit files. Make sure that the file that is included has the appropriate section headers before any directive.
https://www.freedesktop.org/software/systemd/man/systemd.unit.html https://wiki.archlinux.org/index.php/Systemd#Drop-in_files
On 11.09.2016 04:16, teor wrote:
If you're trying to apply the same policies across a number of relays on the same box, --defaults-torrc FILE can be used to provide default settings, and then each torrc can contain only the unique settings.
Thanks, but I am looking for ways to use shared policies on different servers, each with different core settings (e.g. bandwidth). Syncing a policies file and including it seemed the most convenient way to do it, but until that feature becomes available, I'll stick to generating torrc.
-Ralph
tor-relays@lists.torproject.org
-
David Goulet -
Ivan Markin -
John Ricketts -
nusenu -
Ralph Seichter -
teor -
tor-admin＠torland.is