Delivery-Date: Sun, 18 Jan 2015 21:39:34 -0500
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.3 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	FROM_LOCAL_NOVOWEL,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,URIBL_BLOCKED
	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 A89D01E0032
	for <archiver@seul.org>; Sun, 18 Jan 2015 21:39:32 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id EBA5F33087;
	Mon, 19 Jan 2015 02:39:27 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D86D63307E
 for <tor-talk@lists.torproject.org>; Mon, 19 Jan 2015 02:39:23 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at 
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 ur50sWGXZCoh for <tor-talk@lists.torproject.org>;
 Mon, 19 Jan 2015 02:39:23 +0000 (UTC)
Received: from mout.gmx.com (mout.gmx.com [74.208.4.200])
 (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id BE5E33307B
 for <tor-talk@lists.torproject.org>; Mon, 19 Jan 2015 02:39:23 +0000 (UTC)
Received: from [127.0.0.1] ([99.190.181.188]) by mail.gmx.com (mrgmxus001)
 with ESMTPSA (Nemesis) id 0LhfdP-1XR2Fd1xBZ-00mov1 for
 <tor-talk@lists.torproject.org>; Mon, 19 Jan 2015 03:39:20 +0100
Message-ID: <54BC6E22.50504@gmx.com>
Date: Sun, 18 Jan 2015 20:38:26 -0600
From: Joe Btfsplk <joebtfsplk@gmx.com>
User-Agent: Mozilla/5.0 (Windows NT 6.0; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.4.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <327062943.20150115130813@denstarfarm.us>
 <54B82BB9.6090306@torservers.net>
 <20150115214248.2333BC0390@smtp.hushmail.com>
 <344955553.20150116064103@denstarfarm.us> <54B9676F.1050804@gmx.com>
 <20150116232821.60511C0106@smtp.hushmail.com> <54B9BBD2.9030505@gmx.com>
 <20150117214116.3E3EEC0358@smtp.hushmail.com>
In-Reply-To: <20150117214116.3E3EEC0358@smtp.hushmail.com>
X-Provags-ID: V03:K0:sskQa8lJmLZdy32ucWSG7CfciBmaGEcPaGfavv521F41I+q4qs6
 rsI27hnc4YwI6Y9QVVTBB2DhHODJa5EBjJSWTifitVCK/CEIZ2avgZDcN48ugM7aCZNwyBZ
 K0Pr8iU59HD411vHpCAncN2vuOQMHPtBHmaP2X4c3O/ERT4T/vB+dYV3lnH0AhExekh19y8
 uFcWS/5BOCPGiXbHOX2HQ==
X-UI-Out-Filterresults: notjunk:1;
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Fox News bans my Tor Browser
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>


On 1/17/2015 3:41 PM, l.m wrote:
> "Joe Btfsplk" wrote:
>
>> Just one example:  Say,  https://ixquick.com/ (or Startpage), requires a
>> captcha.  Getting a new identity *often* doesn't remove the captcha
>> requirement - but sometimes does.
>> I started looking at possible reasons why.
 From what I've seen on many sites, including Ixquick / Startpage, is 
their presentation of captchas is VERY much related to the specific IP 
and / or the specific exit relay country.  Once those are changed 
(manually - by me) to say,
1) an IPa (or range) that isn't on some black list - or ones they've 
just had more than usual problems with, in the past, or
2) a country they don't have a lot of problems from,
they don't present captchas.  Those captchas *require* JS, so you must 
enable, even if want to solve the captcha.
On MANY sites, even w/ JS enabled, the *captchas don't work.*
Upshot?  By waiting around for Tor / TBB to change the circuit by 
itself, you may wait a hell of a long time, to get on a site, that 
(often) works fine w/ TBB, if you use the "right" country & a clean IPa.

So what do you do, especially when the captcha doesn't work (assuming 
you don't mind enabling JS)?  Wait for 10, 30, 50 min., for Tor to - 
maybe - build a circuit, using a country (or IP range) that a site 
hasn't "blacklisted?"  But, there's no guarantee (I've seen) that Tor 
will ever build a circuit any time soon, that doesn't use a country 
that's objectionable to the site.

Again, unless I just decide to wait hours, days to connect to a site 
that's balking at a specific exit relay country (or IP range), I just 
manually close the circuit, until it stops using eastern european exits, 
etc.  Then the sites usually connect fine.  I really don't want to have 
to do that, but unless I want to wait forever to connect to some sites, 
it's the only way I've found.

Many of the sites don't give captchas, or any message, when they see a 
country or IP they don't like.
-- 
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

