[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]

Re: [tor-relays] Handling abuse - like to get your help please



On Jun 20, 2016, at 4:19 AM, pa011 <pa011@xxxxxx> wrote:
> 
> Hi all,
> 
> thanks again for your hints - in my case they obviously find Tor less
> fancy - their response today is following:
> 
> "Hello.
> You need to take steps to ensure that the complaint would be no longer
> received.
> This software is only allowed if there are no complaints on the server."
> 
> As I cant close Port 80 and the next attack would be a different target
> I guess there is not much room for response :-(
> 
> Rgds
> 
> Paul


Paul,

This is a recurring issue that will not go away, because protecting malicious traffic is part of the foundational Tor philosophy. Tor very intentionally has no ability (beyond rudimentary port/host blocking) to control the type of traffic it carries, there are no plans to add any sort of IDS functionality, and filtering exit relay traffic is frowned upon by the Tor community. This is why abuse reports happen, and it's the primary reason that Tor relays are blocked by so many servicesâtypically not because folks are against personal privacy, but because they simply take a very practical approach to network security. So, if you (or your ISP) determine that the benefits of Tor arenât compelling enough to turn a blind eye to malicious Tor traffic and the abuse reports it generates, then your only real options are to either not run an exit, or not run Tor at all.

Thatâs just the way it is.

Jon

_______________________________________________
tor-relays mailing list
tor-relays@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays