|
Hi,
If you are hosting it with XS4ALL, contact them. They have a
policy on Tor exits, and should be able to do something.
Cheers,
Thom
On 18/08/16 10:24, majacobs wrote:
Block ports that spread worm(like) virii would also mean
closing ports 80 and 443. I am afraid that is no option
the white rider
On 18 Aug 2016, at 08:23,
majacobs <tor@xxxxxxxxxxxxxx>
wrote:
Cut off three times
because of worm spread alert. I ran an exit node for
just a couple of weeks. First came in while i was
away on holiday . Could not connect to my vpn but
noticed that one of my consumer routers send a
reboot message around the first day of my vacation
and didn't think about it again , that is till I got
home and really started to run the node . Node 0d0a
was running fine and well when the net was cut of
for a second time just a few days before the third
and last time. I contacted support , sought advice I
was told to better run a relay.
No way! I thought!
To cut a story short, I
know run in bridged mode (obsfs4proxy) but I am
looking for solutions as to how Tor can help not
seeing exit-nodes coming and going because of worm
spreading?
Tor doesn't discriminate based on traffic, so this is
a hard problem.
Over the long term, encourage destinations (or server
providers) to block particular problematic traffic, rather
than entire IP addresses or servers.
Over the short term, block the ports that the worm
uses to spread.
Tim
Tim Wilson-Brown (teor)
teor2345 at gmail dot com
PGP C855 6CED 5D90 A0C5 29F6 4D43 450C BA7F 968F 094B
ricochet:ekmygaiu4rzgsk6n
xmpp: teor at torproject dot org
_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays
|