Maybe something to add because I ran into a mistake:
ExitPolicy is a first match szenario.
The reject rules for abuse reports and stuff has to be the first one,
afterwards your accept rules and then a reject *:*.
For exampe my current policy is:
ExitPolicy reject 5.133.182.0/24 # WebIron report
My hosting provider also go these requests. Their terms of service requires
that I will answer something to acknowledge I got that.
I just answer "ok, I'll handle it" and that's it.
The reverse lookup of my nodes points to a hostname that shows the Tor
text. The host name is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm currently in the middle of a somewhat heated e-mail debate with
their vice-president.
Pasting the e-mails below would be indelicate, but their position is
that the Tor network is responsible for the abuse it generates and
should take measures to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I'm currently in the middle of a somewhat heated e-mail debate with
their vice-president.
Pasting the e-mails below would be indelicate, but their position is
that the Tor network is responsible for the abuse it generates and
should take measures to
>. . .I have to understand how my ISP reacts to this kind of things.
>For the moment I will keep a low profile and I will block the
>mentioned IP range for a month.
Webiron's system sends notifications to both the abusix.org contact
for the IP and to ab...@base-domain.tld for the reverse-DNS
Hi Christian,
sorry, I marked that message as "Todo" but forgot :-)
My replay to my provider is:
-
Hello Martin,
I've blocked the whole /24 (originally the target IP range is inside a
/16 but this would be too much) to prevent further
2015-11-16 12:46 GMT+01:00 Josef 'veloc1ty' Stautner :
> sorry, I marked that message as "Todo" but forgot :-)
Thank you. This is very helpful!.
> -
> Hello Martin,
>
> I've blocked the whole /24 (originally the target IP
> On 16 Nov 2015, at 22:58, Cristian Consonni wrote:
>
> Ok, so you did block a range for a limited period. I will need to
> learn how to do that.
Try:
ExitPolicy reject4 1.2.3.4/24:*
There's an extensive description of ExitPolicy in the tor man page.
Tim
Tim
2015-11-17 0:36 GMT+01:00 Dhalgren Tor :
> Webiron's system sends notifications to both the abusix.org contact
> for the IP and to ab...@base-domain.tld for the reverse-DNS name of
> the relay IP. So if you can configure abuse@ for the relay domain to
> forward to you, you
Hi guys,
I had a thought about writing a small Tor exit node companion app.
This would be a single executable that does 2 things:
- Serve HTTP port 80 traffic on a specific host name and show the
standard Tor web page for exit nodes
- Serve port 25 (SMTP) and forwards
Hi,
2015-10-21 22:23 GMT+02:00 teor :
> Would you mind putting the statement on the wiki or posting it to this list?
>
> It might help other exit operators to respond to these kind of abuse reports.
+1. Can somebody point me to this?
I have just received a notification from
++ 17/11/15 02:08 +0100 - Cristian Consonni:
>2015-11-17 0:36 GMT+01:00 Dhalgren Tor :
>> Webiron's system sends notifications to both the abusix.org contact
>> for the IP and to ab...@base-domain.tld for the reverse-DNS name of
>> the relay IP. So if you can configure
Il 17/Nov/2015 08:27, "Rejo Zenger" ha scritto:
>
> ++ 17/11/15 02:08 +0100 - Cristian Consonni:
> >2015-11-17 0:36 GMT+01:00 Dhalgren Tor :
> >> Webiron's system sends notifications to both the abusix.org contact
> >> for the IP and to
13 matches
Mail list logo