Problems on torrc.d-style configuration directories
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Hello everyone! I met some troubles when testing the new torrc.d-style configuration directories feature (https://trac.torproject.org/projects/tor/ticket/1922). Could anyone share some ideas on the problem, please? I will be really appreciated. The following is what I did: 1. add the following line to /etc/apt/sources.list.d/torproject.list: deb http://deb.torproject.org/torproject.org tor-nightly-master-jessie main 2. update Tor to nightly version: sudo apt-get update 3. tor --version: Tor version 0.3.1.3-alpha-dev (git-a73d0fe9a87df762+b433dff). 4. sudo mkdir /etc/tor/services-available 5. sudo cp anon-connection-wizard.torrc /etc/tor/services-available/ 6. sudo mkdir /etc/tor/services-enable 7. sudo ln -s /etc/tor/services-available/anon-connection-wizard.torrc /etc/tor/services-enable/anon-connection-wizard.torrc 8. reload tor 9. since bridges are used in the anon-connection-wizard.torrc, when we use arm to check the connections, tor should connect to one of the bridges, if torrc.d style configuration worked. However, it didn't work. I also tried to remove the /etc/tor/torrc, and tor could not find a torrc file anymore. The latest related discussion on the ticket is as follows:
Weasel and I (aka Hans) sketched out how we would use it in the Debian package, closely following the Apache pattern but with naming that is more appropriate in Tor:
/etc/tor/torrc:: %include /etc/tor/services-enabled/*.torrc %include /etc/tor/instances-enabled/*.torrc
These dirs are present for the actual snippet files: /etc/tor/services-available /etc/tor/instances-available
These dirs include relative symlinks to *-available: /etc/tor/services-enabled /etc/tor/instances-enabled
For example: /etc/tor/services-enabled/sparkleshare.torrc --> ../services-available/sparkleshare.torrc
The sparkleshare package would include:
/etc/tor/services-available/sparkleshare.torrc
The davical package would include:
/etc/tor/services-available/davical.torrc
So I assumed it still worked. Could anyone please help me point out what I have done wrong? Or could anyone please point me to some docs about the new feature? I can see the source code of core Tor and write some docs on this, if this will be helpful, btw :) I really appreciate your help! Thank you! Best, iry -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJZRvsbAAoJEKFLTbxtzdU86OkP/REdnsdcJJHoGyTdyXYoqJ6n NgW3cKlEGjCZF5bxIQ+lIG6q85j3EfflPDov97VrVyCE8xr6TFG0dDs/sE4rPE/h GjYhBzM1WC5o55vyvdehTh80wl3/hSj/LehCJLOpBKAjoxuzeDHtyrkd3LG22y8i mi93wgfxBuEbqvstDVipWfJt/5JbBLtXS/QainQqFwwFHRxJpIZcSgvWR5UAXAyS IQLW7m91lwl9W/irQvhM8d4nnk0ciTGMPKoyEt3FWHs9jP9ewKvIvWlxJVYZEefW LlLHMVzbyqWZWnkLkCBNyBfZZ0Rk16YFrUuMkTUH83LO/kBSlWFOj3idN5gYwda/ aanJhtopLH1u1nP10TqF6c4e6Bu6tfCOUh8sdOp8s7iB7MJHvaPU3lJM1vDk55u1 +fSxcDOm7NuN7xrJ3elUKS+oeOU8Ah4h43L/9lJgrIZ6zdIdI1f0E4QXlIWbKIbf dkQJrG760R/6jG6JMnbiOFPwoFelLna1hX6USpbnVEfhh33n3t/t5EpK5kH/q2m9 /lCkMcBpa5XXVquGaeCCQ+2X4wQ31wlhka12GADtVkq3SohOnfKzRauJYN8OcHZH eNZlDMbO8j3y9IHEdM+mhT8a7XnnZokFINSjmjnOnAQdk8A8QjB5V/TIZQB1uJwd 1uUyayVwl9SQHy3P6yuH =SLHC -----END PGP SIGNATURE-----
On 19 Jun 2017, at 08:14, iry <iry@riseup.net> wrote:
Signed PGP part Hello everyone!
I met some troubles when testing the new torrc.d-style configuration directories feature (https://trac.torproject.org/projects/tor/ticket/1922). Could anyone share some ideas on the problem, please? I will be really appreciated. The following is what I did: ... tor should connect to one of the bridges, if torrc.d style configuration worked. However, it didn't work.
I also tried to remove the /etc/tor/torrc, and tor could not find a torrc file anymore.
Is there an %include directive in either /etc/tor/torrc or wherever your distribution keeps the defaults torrc?
The latest related discussion on the ticket is as follows:
Weasel and I (aka Hans) sketched out how we would use it in the Debian package ... So I assumed it still worked.
I'm not sure this feature has been implemented in the Debian torrc files yet. Some distributions don't change their configs based on alpha features: alpha features sometimes change. Others are just busy, and take time to update.
Could anyone please help me point out what I have done wrong?
You probably need a %include directive in /etc/tor/torrc. If you get this working, please submit a patch to the Debian bug tracker.
Or could anyone please point me to some docs about the new feature?
https://gitweb.torproject.org/tor.git/diff/doc/tor.1.txt?id=ba3a5f82f1138823...
I can see the source code of core Tor and write some docs on this, if this will be helpful, btw :)
https://gitweb.torproject.org/tor.git/commit/?id=ba3a5f82f11388237a3ba4995dd... T -- 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 ------------------------------------------------------------------------
Hi iry, The ticket for this feature is very old and contains some outdated information. The comment you quoted will not work as it is written because the %include functionality does not support wildcards. However, you can achieve the same result by adding the following line on your torrc: %include /etc/tor/services-enabled/ This will include all the files on /etc/tor/services-enabled/. You can find a short description of this feature on the tor man page, under the section "The configuration file format": Configuration options can be imported from files or folders using the %include option with the value being a path. If the path is a file, the options from the file will be parsed as if they were written where the %include option is. If the path is a folder, all files on that folder will be parsed following lexical order. Files starting with a dot are ignored. Files on subfolders are ignored. The %include option can be used recursively. Best regards, -- Daniel Pinto
participants (3)
-
Daniel Pinto -
iry -
teor