| Summary: | Permissions on directory /run/tor are too permissive. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Paul DeStefano <paul.destefano-redhat2> |
| Component: | tor | Assignee: | Nobody's working on this, feel free to take it <nobody> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 23 | CC: | lmacken, pwouters, s |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-02-02 09:27:56 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
|
Description
Paul DeStefano
2016-02-01 20:34:39 UTC
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. |