Hi,
up until now OrNetStats mainly consisted of tables with lots of
numbers about tor network stats that can be interactively searched,
but graphs are usually a lot easier to comprehend, that is why
I'll be adding more graphs to OrNetStats.
Today I've added the first new graph on the main page
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
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
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
Hello torix,
Quoting torix via tor-relays (2021-08-28 22:35:53)
> I think I remember Roger Dingledine saying somewhere that bridges' ips
> gradually get learned and put on ban lists.
>
> I have some bridges bought for the year. When renewal time comes up, does it
> make sense to let them go
All:
After enabling Tor debug logging, we were able to verify the procedure of the
router_do_orport_reachability_checks() function.
The router_do_orport_reachability_checks() function creates a circuit using a
random Guard and Middle Relay with the Exit Relay always being itself.
This can be
