In torrc I have the control port commented out. I'm told the control port is not supposed to be listed on the relay itself. Below, is now what it says. How do I get rid of it? Control Socket: /run/tor/control GroupWritable RelaxDirModeCheck Thank you for your help :-) Sent with [ProtonMail](https://protonmail.com/) Secure Email.
Relays typically don't need a ControlPort or ControlSocket. That said, having one that is only available on localhost (or via the local filesystem with proper permissions) isn't really a problem. If you really don't want that ControlSocket and you're using something similar to Debian, it is getting set in /usr/share/tor/tor-service-defaults-torrc. Comment it out there and reload tor. Warning: that these files in /usr/share/tor aren't supposed to be edited, and if the tor package ever has an update that changes them, the update will be less smooth (e.g. it will refuse to work non-interactively, or it may clobber your changes). Hope that helps. Matt On 9/10/21 10:06, sysmanager7 via tor-relays wrote:
In torrc I have the control port commented out. I'm told the control port is not supposed to be listed on the relay itself. Below, is now what it says. How do I get rid of it? Control Socket: /run/tor/control GroupWritable RelaxDirModeCheck
Thank you for your help :-) Sent with ProtonMail <https://protonmail.com/> Secure Email.
_______________________________________________ tor-relays mailing list tor-relays@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
Matt Traudt:
Relays typically don't need a ControlPort or ControlSocket.
That said, having one that is only available on localhost (or via the local filesystem with proper permissions) isn't really a problem.
If you really don't want that ControlSocket and you're using something similar to Debian, it is getting set in /usr/share/tor/tor-service-defaults-torrc. Comment it out there and reload tor.
Warning: that these files in /usr/share/tor aren't supposed to be edited, and if the tor package ever has an update that changes them, the update will be less smooth (e.g. it will refuse to work non-interactively, or it may clobber your changes).
That file is not meant to be changed indeed. The better way to disable ControlSocket is to edit the torrc file (not the defaults-torrc): ControlSocket 0 will disable it regardless what the same option says in the defaults file. kind regards, nusenu -- https://nusenu.github.io
participants (3)
-
Matt Traudt -
nusenu -
sysmanager7