Delivery-Date: Sat, 25 Apr 2015 18:35:27 -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,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 26F171E0B4F
	for <archiver@seul.org>; Sat, 25 Apr 2015 18:35:26 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7807034BCE;
	Sat, 25 Apr 2015 22:35:22 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id F2E9A34B93
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 22:35:18 +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 mDbiLwRQurau for <tor-talk@lists.torproject.org>;
 Sat, 25 Apr 2015 22:35:18 +0000 (UTC)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by eugeni.torproject.org (Postfix) with ESMTP id C66F934B91
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 22:35:18 +0000 (UTC)
Received: from yuri.doctorlan.com (c-50-184-63-128.hsd1.ca.comcast.net
 [50.184.63.128]) (authenticated bits=0)
 by shell1.rawbw.com (8.14.9/8.14.9) with ESMTP id t3PMZFks048790
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <tor-talk@lists.torproject.org>; Sat, 25 Apr 2015 15:35:15 -0700 (PDT)
 (envelope-from yuri@rawbw.com)
X-Authentication-Warning: shell1.rawbw.com: Host
 c-50-184-63-128.hsd1.ca.comcast.net [50.184.63.128] claimed to be
 yuri.doctorlan.com
Message-ID: <553C16A2.8060300@rawbw.com>
Date: Sat, 25 Apr 2015 15:35:14 -0700
From: Yuri <yuri@rawbw.com>
User-Agent: Mozilla/5.0 (X11; FreeBSD amd64;
 rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <20150416215238.37FBBC03DD@smtp.hushmail.com>
 <55315DC9.50802@sophiehassfurther.com>
 <20150424000609.73C53E04DA@smtp.hushmail.com>
 <5539FE14.8040503@sophiehassfurther.com>
 <20150425174822.BA18A40C08@smtp.hushmail.com>
 <20150425182047.CB91F40C09@smtp.hushmail.com>
In-Reply-To: <20150425182047.CB91F40C09@smtp.hushmail.com>
Subject: Re: [tor-talk] TorBirdy seems to connect to the same exit node
 again 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-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 04/25/2015 11:20, l.m wrote:
> 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.

If this is the concern that request to check.torproject.org might 
compromise security, this is the clear indication that TorBirdy/TBB 
aren't adequate for the requirements. Clearly, such people should switch 
to VM isolation, and there is no need to ever go to check.torproject.org 
from there, and there is no risk even if one does.

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

