Delivery-Date: Sat, 25 Apr 2015 14:21:01 -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.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,T_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 CD42A1E0896
	for <archiver@seul.org>; Sat, 25 Apr 2015 14:20:58 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id D5F4634DF5;
	Sat, 25 Apr 2015 18:20:54 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 043B934D31
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 18:20:51 +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 OBqU72PcBSsH for <tor-talk@lists.torproject.org>;
 Sat, 25 Apr 2015 18:20:50 +0000 (UTC)
Received: from smtp10.hushmail.com (smtp10.hushmail.com [65.39.178.143])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "smtp.hushmail.com" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id CCD1634BBD
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 18:20:50 +0000 (UTC)
Received: from smtp10.hushmail.com (localhost [127.0.0.1])
 by smtp10.hushmail.com (Postfix) with SMTP id E4A55C0183
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 18:20:47 +0000 (UTC)
Received: from smtp.hushmail.com (w7.hushmail.com [65.39.178.32])
 by smtp10.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 18:20:47 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id CB91F40C09; Sat, 25 Apr 2015 18:20:47 +0000 (UTC)
MIME-Version: 1.0
Date: Sat, 25 Apr 2015 14:20:47 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <20150425174822.BA18A40C08@smtp.hushmail.com>
References: <20150416215238.37FBBC03DD@smtp.hushmail.com>
 <55315DC9.50802@sophiehassfurther.com>
 <20150424000609.73C53E04DA@smtp.hushmail.com>
 <5539FE14.8040503@sophiehassfurther.com>
 <20150425174822.BA18A40C08@smtp.hushmail.com> 
Message-Id: <20150425182047.CB91F40C09@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk]
	=?utf-8?q?TorBirdy_seems_to_connect_to_the_same_exit_n?=
	=?utf-8?q?ode=09again_and_again?=
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>

>The ip check hidden behind a warning dialog hinders obtaining 
>useful data. I'll keep that in mind.

On second thought there is an advantage to discouraging the use of the
check. If something went wrong with the socks port setting using the
check would leak the intention to use tor by connecting to
check.torproject.org. Not a big deal, unless the socks port isn't set
or becomes unset, and a bridge is being used by tor.

So caution is probably a better idea and have a proxy check first like
about:tor in Tor Browser.

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

