Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

syslog tor warnings #402

Closed
AlverGant opened this issue Mar 5, 2019 · 3 comments
Closed

syslog tor warnings #402

AlverGant opened this issue Mar 5, 2019 · 3 comments

Comments

@AlverGant
Copy link

First of all congratulations on this great project!

I am seeing warnings on syslog regarding the tor user and I would like to ask if there are security implications to it.

[warn] /run/tor is not owned by this user (bitcoin, 1002) but by debian-tor (111). Perhaps you are running Tor as the wrong user?
[warn] 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 and group account that is running Tor. (On some Unix systems, anybody who can list a socket can connect to it, so Tor is being careful.)

@AlverGant
Copy link
Author

It's strange, looking at internet.tor.sh script, /var/run/tor is given bitcoin user ownership during installation:
sudo chown -R bitcoin:bitcoin /var/run/tor/
but that is being overriden after reboot:
drwxr-sr-x 2 debian-tor debian-tor 40 Mar 5 13:52 tor
Is it normal?
The version installed is
tor/stable,now 0.3.5.8-1~d90.stretch+1 armhf [installed]

@rootzoll rootzoll added this to the 1.1 Release milestone Mar 5, 2019
@rootzoll
Copy link
Collaborator

rootzoll commented Mar 5, 2019

Thanks for checking that out. I think I saw that kind of error during implementation but thought I fixed it with the code you quoted - but I havent seen (maybe overlooked) that overwrite after reboot.

TODO: check for v1.1 release with test systems if this overwrite on reboot is reproducable.

@nyxnor
Copy link
Contributor

nyxnor commented Apr 16, 2021

Close this. Tor [WARN] fixes above is the recent discussion about this.

@rootzoll rootzoll removed this from the Future Release Collector milestone Mar 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants