Hide Forgot
Description of problem: Tor is complaining after startup: Permissions on directory /run/tor are too permissive. Before Tor can create a control socket in "/run/tor/control", the directory "/run/tor" needs to exist, and to be accessible only by the user account that is running Tor. (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.) Version-Release number of selected component (if applicable): tor-0.2.7.6-5.fc23.x86_64 How reproducible: Always since recent update, possibly since F23. Steps to Reproduce: 1. Install tor 2. configure 3. start service Actual results: Tor starts, but complains. Expected results: No complaints Additional info:
Thanks for the bug report! However, I can't reproduce your problem. Can you please post the output of: ls -ld /run/tor Also, please check /etc/tor directory for "torrc.rpmnew" file.
Gosh, you're very welcome! I've never been thanked for a bug report before. Oops, I should have thought you would want that. $ ls -ld /run/tor drwxr-x---. 2 toranon toranon 60 Feb 1 16:30 /run/tor/ Aha! You are right; there is a new torrc. I got the bug announcement for 2.7.6, I think, and just installed it when it hit the repos without thinking to check. There were new lines in there about group permissions, so I bet that's all it was. Let me restart...yep, it's good. Thanks! Sorry, sysadmin error.
(In reply to Paul DeStefano from comment #2) > Aha! You are right; there is a new torrc. I got the bug announcement for > 2.7.6, I think, and just installed it when it hit the repos without thinking > to check. There were new lines in there about group permissions, so I bet > that's all it was. Let me restart...yep, it's good. > > Thanks! Sorry, sysadmin error. This was actually an error on my part (though I fixed it before it left updates-testing). In tor-0.2.7.6-3 I added ControlSocket/Cookie stuff but forgot the group permissions stuff. I did fix the problem before it left updates-testing, so most users would just jump straight to tor-0.2.7.6-5 and not have any issues. But anyone who installed -3 from updates-testing might encounter the same problem you saw.
Actually, I think my error did make it to stable in 0.2.7.6-4.
So, quick question: why did /etc/tor/torrc change ownership and permission? It was 600 toranon:toranon, now it's 644 root:root. That's a significant change, and now provision was made for it. (I have 2.7.6-5 now, wasn't a problem with -4 pkg.)
(In reply to Paul DeStefano from comment #5) > So, quick question: why did /etc/tor/torrc change ownership and permission? > It was 600 toranon:toranon, now it's 644 root:root. That's a significant > change, and now provision was made for it. (I have 2.7.6-5 now, wasn't a > problem with -4 pkg.) The permissions of /etc/tor/torrc in the RPM have been the same for many years. Permissions were probably changed manually using chmod/chown.