Delivery-Date: Fri, 16 Jan 2015 14:33:13 -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 057861E04BA
	for <archiver@seul.org>; Fri, 16 Jan 2015 14:33:12 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1A30D329FF;
	Fri, 16 Jan 2015 19:33:07 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 46FD732B7B
 for <tor-talk@lists.torproject.org>; Fri, 16 Jan 2015 19:33:04 +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 wQ5VTbeQUtLg for <tor-talk@lists.torproject.org>;
 Fri, 16 Jan 2015 19:33:04 +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 2459B329FC
 for <tor-talk@lists.torproject.org>; Fri, 16 Jan 2015 19:33:01 +0000 (UTC)
Received: from [127.0.0.1] ([99.190.181.188]) by mail.gmx.com (mrgmxus002)
 with ESMTPSA (Nemesis) id 0MVuyU-1YEKDC0z6G-00X1zS for
 <tor-talk@lists.torproject.org>; Fri, 16 Jan 2015 20:32:58 +0100
Message-ID: <54B9676F.1050804@gmx.com>
Date: Fri, 16 Jan 2015 13:33:03 -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>
In-Reply-To: <344955553.20150116064103@denstarfarm.us>
X-Provags-ID: V03:K0:FFq5ZHrCfTrlGGIe35rOcyQxhwNJM7tCYXBjPNGyp30lFuPhrgI
 V+FWiacW7qdaOPNrL0sx4tK0LmZZip1OeL5RayiPsTzbUdrsWx0apCmuz3rvIcI4n0L3SKG
 n64zRxVFOmz43+H5O2xm2XqfJhw0WhPUBlTTPVf75Ljhww+ZxviR3DRMoOdnUXWz+Il9XXn
 mcYDu2bZx4yQFDBBT1idQ==
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/16/2015 5:41 AM, Rocky_Tor wrote:
>> It might be the changing exit node from new identity.
> I  did  try changing identities. After numerous "tries", I was successful
> onto  FoxNews.  Then shortly that too changed and I was backed to being
> blocked.
For me, TBB is sometimes blocked on sites where it generally is not.
My description here has worked on *some* sites, but fails on others.

Like, https://ixquick.com/do/search  & Startpage.  When they "block,"  
those 2 sites usually give a captcha.
On those 2 sites (& a fair # of others) just clicking the "new identity" 
on tor button often removes the captcha, or other site access issues, if 
no captcha.

New identity sometimes fails to allow access - even on sites it normally 
works.  Maybe ? because of the geo-location of  new identity is near the 
old one; or new identity's IPa is also on a spam list, etc?

I still (sometimes) use Vidalia [1], - allows more quickly choosing a 
new identity w/ exit relays far from the one getting blocked.
Often, if clicking New Identity on TorButton doesn't solve a site access 
issue, selecting a exit in a much different geo-location solves it.

[1] I don't know that Vidalia is still considered "anonymity safe", in 
later TBB versions - like 4.02, 4.03.
COMMENTS on that?

On Cloudfront supplied captchas on sites, I still find that entering 
captchas or changing identities to be mostly unsuccessful.

Can someone explain about using the following methods -  mentioned earlier?
> You might try adding TrackHostExits ..
>   You might also try AllowDotExit.

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

