-
Notifications
You must be signed in to change notification settings - Fork 17
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
feature request: add support for ControlSocket #13
Comments
Yes, I also would appreciate this. ControlSockets are better to handle. |
Hi! |
Hi! Sorry, didn't see the config file or the variable is missing in the default file. I tried it first with tor_control_port, but that didn't work. Thanks a lot for your work. I looks great and the webserver also have a low CPU usage. Better than everything I've used before. Regards, |
How do I configure multiple instances in this config file?
Thanks a lot! |
This is - as stated in the config file - not yet implemented:
|
I'm filing this here as a github issue so I get notifications if there are any updates on this. I mentioned this previously on the tor-relays ML [1].
Rationale:
In ansible-relayor [2] I support ControlSocket only (no controlPort) for simplicity (no TCP port required, no password handling, just filesystem permissions).
It would be great if theonionbox would support ControlSocket to connect to tor.
[1] https://lists.torproject.org/pipermail/tor-relays/2016-September/010409.html
[2] https://github.com/nusenu/ansible-relayor
The text was updated successfully, but these errors were encountered: