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

Re: Abuse ticket

To: or-talk@xxxxxxxxxxxxx
Subject: Re: Abuse ticket
From: Roger Dingledine <arma@xxxxxxx>
Date: Tue, 17 Mar 2009 03:03:43 -0400
Delivered-to: archiver@xxxxxxxx
Delivered-to: or-talk-outgoing@xxxxxxxx
Delivered-to: or-talk@xxxxxxxx
Delivery-date: Tue, 17 Mar 2009 03:03:46 -0400
In-reply-to: <bd9056300903161718q73291f80j22fa8d5636a5d9c0@xxxxxxxxxxxxxx>
References: <bd9056300903161718q73291f80j22fa8d5636a5d9c0@xxxxxxxxxxxxxx>
Reply-to: or-talk@xxxxxxxxxxxxx
Sender: owner-or-talk@xxxxxxxxxxxxx
User-agent: Mutt/1.5.13 (2006-08-11)

On Tue, Mar 17, 2009 at 01:18:10AM +0100, slush wrote:
> I dont want to close HTTP ports 8-), but next report of abusive traffic will
> lead to shutting down Tor or whole VPS :-(. So is there any "best practice",
> what I should do now? DMCA response is probably not fitting to this issue...

See also
https://wiki.torproject.org/noreply/TheOnionRouter/TorGuideUniversities

The basic idea there is to start talking to people before incidents
happen, since they're more likely to listen then. This suggestion doesn't
help you so much in your current situation, though.

The other suggestions in the thread might be useful too -- especially
Phobos's suggestion of trying to take your ISP out of the loop in the
abuse responses.

--Roger

References:
- Abuse ticket
  - From: slush

Prev by Author: Why Tor is slow and what we're going to do about it
Next by Author: Re: Bridge scanning resistance
Previous by thread: Re: Abuse ticket
Next by thread: Re: Abuse ticket
Index(es):
- Author
- Thread