Delivery-Date: Tue, 14 Oct 2014 13:44:56 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-4.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID autolearn=ham version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 341301E1071;
	Tue, 14 Oct 2014 13:44:55 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1509E30E17;
	Tue, 14 Oct 2014 17:44:51 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AD05130C4F;
 Tue, 14 Oct 2014 17:44:47 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id 776QgHRDRvC9; Tue, 14 Oct 2014 17:44:47 +0000 (UTC)
X-Greylist: delayed 369 seconds by postgrey-1.34 at eugeni;
 Tue, 14 Oct 2014 17:44:47 UTC
Received: from mail.intersafeit.com (mail.intersafeit.com [198.199.95.65])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 7ED4830C44;
 Tue, 14 Oct 2014 17:44:47 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by mail.intersafeit.com (Postfix) with ESMTP id AEBF0DF97B;
 Tue, 14 Oct 2014 10:38:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intersafeit.com;
 s=default; t=1413308314;
 bh=8JeVnamWv54gM1J/Rt1E4SbB1FG12/iFsnFHAlhlsnI=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=RkNAfKV6U9ztTeY5wtxI7Aso+tB9wOz8ivG1Zf9hbzYqTmPYRXZMkRR2Ja8K9r3te
 1ryrcQlxoFcxOvFpVhMviJFJ35Kw2kzLPL8rcgpgJWIG5mUT7ue3ow/fJLAxaPB13Q
 3YKsP3AeC3zc+5AvcsArUS0QPMMVhLRFviC6QFjo=
X-Virus-Scanned: Debian amavisd-new at mail.intersafeit.com
Received: from mail.intersafeit.com ([127.0.0.1])
 by localhost (mail.intersafeit.com [127.0.0.1]) (amavisd-new, port 10024)
 with LMTP id L3FnQ_KLLGoI; Tue, 14 Oct 2014 10:38:29 -0700 (PDT)
Received: from [172.24.1.30] (wdc-co1.WEST-DATACENTER.NET [69.36.160.253])
 (using TLSv1 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.intersafeit.com (Postfix) with ESMTPSA id 098BDDF970;
 Tue, 14 Oct 2014 10:38:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=intersafeit.com;
 s=default; t=1413308309;
 bh=8JeVnamWv54gM1J/Rt1E4SbB1FG12/iFsnFHAlhlsnI=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=2vm3IT4Aw4+Gk3j2z70VKbi/+1poGFQleHg0S8b2eLoHHo3dEC6BW8xVShquLXn6b
 igj/+4B/hWNWGUFHzbqxEFcDiIgSIPdHrBY30t93rwGc9He0UFvCMMma1wukpY+EJb
 LIAujvcqomKACXnB392ZTsnJ8qPreqa8ungAWXaQ=
Message-ID: <543D5F94.5020209@intersafeit.com>
Date: Tue, 14 Oct 2014 11:38:28 -0600
From: tor-exit0 <tor-exit0@intersafeit.com>
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64;
 rv:24.0) Gecko/20100101 Thunderbird/24.6.0
MIME-Version: 1.0
To: tor-relays@lists.torproject.org, tor-talk@lists.torproject.org
References: <9c75bcd857735052022e6c6594245178.squirrel@zsolxunfmbfuq7wf.onion>
In-Reply-To: <9c75bcd857735052022e6c6594245178.squirrel@zsolxunfmbfuq7wf.onion>
Subject: Re: [tor-talk] [tor-relays] GoodBadISPs revamp?
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On 10/12/2014 6:56 PM, subkeys@riseup.net wrote:
> [cross-posted on tor-talk and tor-relays]
> 
> i've found that the Tor GoodBadISPs list [1] is somewhat outdated on
> current hosts that allow Tor (exit) relays to be hosted. i'm trying to
> find a cheap host that allows exits to be operated from their services,
> and navigating the outdated list and finding an operator that isn't
> extremely expensive is time consuming (some entries go back to 2010!).
> 

I may have an update for Digital Ocean here soon. Over the weekend my
exit node was used by someone brute forcing wordpress logins. As
expected the network to my droplet was disabled and I've been
communicating with them since. They seemed respectful that I could show
my droplet wasn't compromised and they directed me to their TOS which
doesn't disallow tor traffic but does hold one responsible for the traffic.

My latest response to them is that I'm happy to address abuse but I can
only do it if I'm informed about it however their TOS suggests that they
may terminate droplets if abuse occurs which doesn't give me time to be
responsible. I already run a limited exit policy to avoid DMCA hassle
but any response to abuse by it's very nature occurs after abuse has
taken place. I'm hoping to hear from them whether they'll allow
responsible actions for abuse or if they will simply terminate droplets
that have a history behind them.

-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

