Delivery-Date: Fri, 08 Aug 2014 04:39:45 -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.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD 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 3081A1E0462;
	Fri,  8 Aug 2014 04:39:44 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id BEC6A28B2B;
	Fri,  8 Aug 2014 08:39:41 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 5619C21BBF
 for <tor-talk@lists.torproject.org>; Fri,  8 Aug 2014 08:39:38 +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 HhVMPjgoXXLY for <tor-talk@lists.torproject.org>;
 Fri,  8 Aug 2014 08:39:38 +0000 (UTC)
Received: from jessica.everdot.org (unknown [IPv6:2001:470:1f0b:1c12::1])
 (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 234B7209EC
 for <tor-talk@lists.torproject.org>; Fri,  8 Aug 2014 08:39:38 +0000 (UTC)
Received: from mail.everdot.org (primail.everdot.org [IPv6:2001:470:dc2e:5::2])
 (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by jessica.everdot.org (Postfix) with ESMTPS id 17F89FA062C
 for <tor-talk@lists.torproject.org>; Fri,  8 Aug 2014 10:39:34 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1])
 by mail.everdot.org (Postfix) with ESMTP id 1779C9122EDA
 for <tor-talk@lists.torproject.org>; Fri,  8 Aug 2014 10:39:33 +0200 (CEST)
X-Virus-Scanned: amavisd-new at everdot.org
Received: from mail.everdot.org ([127.0.0.1])
 by localhost (everdot.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id CtRCCLUO-9y2 for <tor-talk@lists.torproject.org>;
 Fri,  8 Aug 2014 10:39:24 +0200 (CEST)
Received: from meilong (unknown [IPv6:2001:470:dc2e:2:404a:7238:7265:5dcc])
 (using SSLv3 with cipher ECDHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 by mail.everdot.org (Postfix) with ESMTPSA id C48719122C89
 for <tor-talk@lists.torproject.org>; Fri,  8 Aug 2014 10:39:23 +0200 (CEST)
Date: Fri, 8 Aug 2014 10:39:17 +0200
From: =?ISO-8859-1?B?1nl2aW5k?= Saether <oyvinds@everdot.org>
To: tor-talk@lists.torproject.org
Message-ID: <20140808103917.2b4f455a@meilong>
In-Reply-To: <53E3E530.7010105@gmx.com>
References: <3660653D-B230-40CA-B641-2C7D815DEE47@mail.bitmessage.ch>
 <53E3BE07.7010105@riseup.net> <53E3E530.7010105@gmx.com>
X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.24; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Subject: Re: [tor-talk] Craigslist now blocking all Tor IPs? bad people use
 Tor
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: multipart/mixed; boundary="===============8332433389140514424=="
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

--===============8332433389140514424==
Content-Type: multipart/signed; micalg=PGP-SHA1;
 boundary="Sig_/vsJF.My8LKOTmV0U=CJkFwt"; protocol="application/pgp-signature"

--Sig_/vsJF.My8LKOTmV0U=CJkFwt
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

> Most users have seen sites refuse to allow connections from a
> specific Tor IPa.  Sometimes they state the reason as being the
> specific IPa on a blacklist.
> Often, if you force a new exit relay in TBB, then you can connect to
> the site.
>=20
> So what happens to all the Tor network addresses that get blacklisted
> as a result of abuse (which is quite common).
> Someone / something must be dealing with those issues, or else much
> of the network would eventually be blacklisted.

I know from reading this list that Tor project people sometimes contact
sites who block Tor and ask them to solve their issues some other way
but I have the distinct impression that they will not do so unless the
site in question is a government propaganda operation like Wikipedia or
YouTube and similar.

The real issue here is that bad people do use Tor. One or a few people
using it can cause real harm and more importantly cost. One of my own
sites receive about 10k abusive http POST requests per day from the Tor
network. I fully understand why many people do not want this cost when
there is no obvious benefit. The few legitimate Tor users that may want
to visit your site tend to block advertisements anyway. Thus, blocking
Tor can easily be seen as something that can reduce costs increase
shareholder value.

If you want those who block Tor to stop doing so then your best course
of action is probably to contact them yourself and help them implement
better solutions that prevent abuse from both Tor and non-Tor users. Do
not expect anyone to do this for you. There are ways to deal with abuse
from the Tor network without blocking it but implementing these
solutions does cost time and money. If you can present a solution with
little or no cost or convince them why they should accept a reduced
bottom line just to please the two Tor users who are not abusive then
just do it. If you can't then you should just accept that it is, in
many cases, just not worth the cost and trouble.

--Sig_/vsJF.My8LKOTmV0U=CJkFwt
Content-Type: application/pgp-signature; name=signature.asc
Content-Disposition: attachment; filename=signature.asc

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iEYEARECAAYFAlPkjLkACgkQNBSJHnwv/Kq2RwCfQwnx9RhNyeJbMjyfE56QemGH
wnIAoKg9G2I3XZeanrGWL4XzY2Diha9L
=7YP4
-----END PGP SIGNATURE-----

--Sig_/vsJF.My8LKOTmV0U=CJkFwt--

--===============8332433389140514424==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

-- 
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

--===============8332433389140514424==--

