[tor-relays] new tor network graphs on OrNetStats

[nusenu]

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 that shows the
10 largest proven exit operator domains and their exit fraction in a bar chart:
https://nusenu.github.io/OrNetStats/index.html

In the long run I plan to publish (and re-implement) all graphs that currently
are nonpublic (and not on OrNetStats yet).
This should give more people a better view / understanding about what is 
happening/changing
on the tor network infrastructure.

kind regards,
nusenu

--
https://nusenu.github.io
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Relay Control Port

[nusenu]

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
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

Re: [tor-relays] Relay Control Port

[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).

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  Secure Email.
> 
> 
> ___
> tor-relays mailing list
> tor-relays@lists.torproject.org
> https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
> 
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays

[tor-relays] Relay Control Port

[sysmanager7 via tor-relays]

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

Re: [tor-relays] Burning Bridges

[meskio]

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 and buy new vms for the next year rather than renew 
> them? I don't know if it matters what pool a bridge is in.

Yes, is good to rotate the IP addresses of bridges. What you say is correct. It 
doesn't matter what pool you are in.

Only private bridges are good to be stable, as they are manually handled and 
you 
will need to notify the users of this bridge of the new IP address. But if you 
didn't configure your bridge specifically to be a private bridge (with the 
'PublishSherverDescriptor 0' option) and handled by hand your bridge data to 
bridge users you are not running one and will be good if you rotate the IP 
address once in a while.

Thanks for running a bridge.

-- 
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
 My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.

signature.asc
Description: signature
___
tor-relays mailing list
tor-relays@lists.torproject.org
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays