Delivery-Date: Sat, 11 Apr 2015 03:07:51 -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 3B21B1E0E5A
	for <archiver@seul.org>; Sat, 11 Apr 2015 03:07:48 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B67E9343D7;
	Sat, 11 Apr 2015 07:07:42 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A3A1D343A1
 for <tor-talk@lists.torproject.org>; Sat, 11 Apr 2015 07:07:39 +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 FuSoSXaiGgao for <tor-talk@lists.torproject.org>;
 Sat, 11 Apr 2015 07:07:39 +0000 (UTC)
Received: from dd15500.kasserver.com (dd15500.kasserver.com [85.13.136.184])
 (using TLSv1.1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 7319A3436C
 for <tor-talk@lists.torproject.org>; Sat, 11 Apr 2015 07:07:39 +0000 (UTC)
Received: from 127.0.0.1 (unknown [176.108.160.241])
 by dd15500.kasserver.com (Postfix) with ESMTPSA id 753525CE01A3
 for <tor-talk@lists.torproject.org>; Sat, 11 Apr 2015 09:07:34 +0200 (CEST)
Message-ID: <5528C834.7020305@sophiehassfurther.com>
Date: Sat, 11 Apr 2015 07:07:32 +0000
From: Sophie Hassfurther <sophie@sophiehassfurther.com>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <5527BB80.8010708@sophiehassfurther.com>
 <20150410183853.GA32173@riseup.net> <552820C1.8050203@sophiehassfurther.com>
 <20150410215018.F057CC0D3A@smtp.hushmail.com>
In-Reply-To: <20150410215018.F057CC0D3A@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-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>

Hi Leeroy,

Thanks for the reply!

I am using the latest Tor Browser bundle (4.0.8), and checked the
signature before installing. Updating does not work for me anymore, I
have to upgrade to a new machine and newer OSX, will do asap.

I think what you describe might be correct - so far choosing a new
identity in Tor did not work for me, but restarting the Tor Browser
worked. So maybe some circuits did not close?

Just a general question: is it normal to get connected to the same exit
node almost all the time, when I start my mail program?

Thanks for the support everyone
S.


l.m:
> Hi,
> 
> I would like to ask if you're using the Tor Browser bundle with or
> without modification. When the new identity is used in Tor Browser
> (it's my understanding--please correct if wrong) that the circuits
> related to open tabs are allowed to close. This is because the NEWNYM
> signal is issued while also closing the connections for the currently
> open tabs. The existing circuits close naturally because they are
> already dirty. Then later tabs use new circuits and all is well in
> anonland.
> 
> A complication can arise when using other applications (like TorBirdy)
> with the Tor Browser bundle. The problem is some mail server
> connections fail to close and persist across new identities (NEWNYM)
> issued by Tor Browser. This makes later mail server connections appear
> to split with an existing connection through one exit and new
> connections through some other exit. Closing tabs in Tor Browser won't
> fix it. Closing circuits related to tabs won't fix it. What needs to
> happen is to have the existing mail server connection (having not
> closed on it's own) forcefully closed by closing the related circuit.
> 
> I'm unclear if this is (partially) a fault of the mail server. I've
> seen the same behavior in other applications so it may also be a
> failure at the exit. If you see this problem increasingly occurring
> you might try setting up a Vidalia instance in parallel with the Tor
> Browser bundle. (I wouldn't normally suggest it except for
> troubleshooting). You would then be able to see the offending circuit
> held open.
> 
> --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

