> On 26 Nov 2015, at 05:36, Josef Stautner wrote:
>
> Hello @all,
>
> (I'm not sure if you guys are interested in a topic like this)
> I wrote a perl script to gather bandwidth data from my Tor exit relay.
> The script connects to the Tor control socket, fetches the running
hi,
I'm operating a tor exit with a relatively high bandwith rate for more
than 3 years.
My ISP receives more and more abuse tickets about my server regarding
netscans. These netscans are executed with dest. port 80 so I'm not able
to block them easily.
Any idea how to prevent netscans using my
Hi,
First rule is to use some firewall, 2nd is to disable that port for few
days. You will not lose exit flag becuase of this, just will give you time
to learn more about how to secure your node. Few friends
using FirewallBuilder to learn how to build their firewall system, maybe
you can start
Hello @all,
(I'm not sure if you guys are interested in a topic like this)
I wrote a perl script to gather bandwidth data from my Tor exit relay.
The script connects to the Tor control socket, fetches the running
config to extract the bandwidth limits and the reject rule count.
Afterwards the
Hi,
I’m a bit confused right now. I’ve upgraded my relay to Debian Jessie yesterday
and since then, arm keeps telling me
> [ARM_WARN] The torrc differs from what tor's using. You can issue a
> sighup to reload the torrc values by pressing x.
> - configuration value is missing from the torrc:
Hi Tim,
you hit me hard today because I didn't think about the privacy of the
users :-)
But the data points for read and write are just average values and the
time series database also only stores the average values. So I don't
think that just by looking at the graph you can track specific Hidden