Delivery-Date: Mon, 13 Apr 2015 16:00:32 -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 1B6EC1E1051
	for <archiver@seul.org>; Mon, 13 Apr 2015 16:00:31 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 82B2834278;
	Mon, 13 Apr 2015 20:00:27 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 361353377D
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 20:00:24 +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 L3NyNKVyIo4F for <tor-talk@lists.torproject.org>;
 Mon, 13 Apr 2015 20:00:24 +0000 (UTC)
Received: from shell1.rawbw.com (shell1.rawbw.com [198.144.192.42])
 by eugeni.torproject.org (Postfix) with ESMTP id 0B8A733573
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 20:00:23 +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 t3DK0JoT034722
 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO)
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 13:00:20 -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: <552C2052.3030002@rawbw.com>
Date: Mon, 13 Apr 2015 13:00:18 -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: <5527BB80.8010708@sophiehassfurther.com>
 <20150410183853.GA32173@riseup.net> <552820C1.8050203@sophiehassfurther.com>
 <20150410215018.F057CC0D3A@smtp.hushmail.com>
 <5528C834.7020305@sophiehassfurther.com> <552AFCCA.6040609@rawbw.com>
 <20150413171551.E4E4BE042D@smtp.hushmail.com> <552C1189.2050501@rawbw.com>
 <20150413191331.9AF42E0433@smtp.hushmail.com> <552C1A33.20206@rawbw.com>
 <20150413195525.18C96E0432@smtp.hushmail.com>
In-Reply-To: <20150413195525.18C96E0432@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/13/2015 12:55, l.m wrote:
> Hi Yuri,
>
> I, er, don't think what you're proposing is the answer to the OP's
> problem.
>
> If they're using a port which is only supported by 3 exits they'll
> still have the problem. If one exit is blocked and they choose that
> one the mail server will see further attempts as possibly malicious.
> At least one factor is the need to avoid the blacklisted exits in the
> first place. That's hard to do if they've been using the same handful
> of exits. Someone may be attempting to break into their account and
> the blacklist of the exit may be warranted.
>
> Furthermore, it hasn't been identified that the problem is a
> connection which is remaining open across new identities. That's just
> a behavior observed for arbitrary traffic in the wild. It's should be
> highly unlikely for email traffic alone to cause this behavior. It
> would require their imap/smtp traffic to coincide with some webmail
> traffic across exits where one is blocked. It was me who mentioned it.
> That was before noticing the port number and it's rarity at exit
> policies.
>
> I've only ever seen the problem described as circuits held open (with
> TorBirdy) under very specific circumstances. It cannot yet be the
> cause of the OP's problem. Not enough troubleshooting done. It's
> actually more likely to be the port.
>
> Anyway, telnet isn't hard, you could just ask tor-talk. The hardest
> part is getting the right format of cookie for (default)
> authentication. It's harder to get Vidalia working.
> --leeroy

I think, agreement to disagree is in order!

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

