Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#35272 - [tor] default torrc is ancient
Attached to Project:
Community Packages
Opened by Björn Mandelvåg (koltrast) - Tuesday, 14 May 2013, 12:05 GMT
Last edited by Lukas Fleischer (lfleischer) - Tuesday, 04 June 2013, 12:52 GMT
Opened by Björn Mandelvåg (koltrast) - Tuesday, 14 May 2013, 12:05 GMT
Last edited by Lukas Fleischer (lfleischer) - Tuesday, 04 June 2013, 12:52 GMT
|
DetailsDescription:
The default torrc for tor is ancient, as clear from the first line: ## Last updated 22 July 2005 for Tor 0.1.0.13. SocksBindAddress for example is apparently deprecated in tor and will cause conflicts with more recent features. It seems it would be a good idea to make a thorough revision and get rid of all such legacy stuff still present. |
This task depends upon
Closed by Lukas Fleischer (lfleischer)
Tuesday, 04 June 2013, 12:52 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 0.2.3.25-3.
Tuesday, 04 June 2013, 12:52 GMT
Reason for closing: Fixed
Additional comments about closing: Fixed in 0.2.3.25-3.
The current torrc (tor-0.2.3.25-2) has the following config (excluding comments):
AllowUnverifiedNodes middle,rendezvous
DataDirectory /var/lib/tor
Group tor
Log notice syslog
RunAsDaemon 1
SocksBindAddress 127.0.0.1 # accept connections only from localhost
SocksPort 9050 # what port to open for local application connections
User tor
My torrc is the upstream provided sample config, but with the following options set:
DataDirectory /var/lib/tor
Log notice syslog
Resulting changes in behaviour:
1. It no longer forks
2. It no longer switches to the tor user
Both changes are addressed in my altered tor.service file making the user experience unchanged.
My new tor.service file also doesn't pass --quiet to the tor binary. Since we log to syslog we want systemd to pick this up, which it does. Previously "systemctl status tor" did not provide the logs.
I also removed mention of /etc/conf.d/tor from the tor.install file, since it no longer applies.