Delivery-Date: Fri, 17 Apr 2015 15:24:13 -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 20D151E02E5
	for <archiver@seul.org>; Fri, 17 Apr 2015 15:24:11 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id A4A9C3446E;
	Fri, 17 Apr 2015 19:24:05 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 9B5EE34468
 for <tor-talk@lists.torproject.org>; Fri, 17 Apr 2015 19:24:02 +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 4szWspVvF12F for <tor-talk@lists.torproject.org>;
 Fri, 17 Apr 2015 19:24:02 +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 6B3AB3444F
 for <tor-talk@lists.torproject.org>; Fri, 17 Apr 2015 19:24:02 +0000 (UTC)
Received: from 127.0.0.1 (chomsky.torservers.net [77.247.181.162])
 by dd15500.kasserver.com (Postfix) with ESMTPSA id A5FA65CE01A3
 for <tor-talk@lists.torproject.org>; Fri, 17 Apr 2015 21:23:56 +0200 (CEST)
Message-ID: <55315DC9.50802@sophiehassfurther.com>
Date: Fri, 17 Apr 2015 19:23:53 +0000
From: Sophie Hassfurther <sophie@sophiehassfurther.com>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <20150416215238.37FBBC03DD@smtp.hushmail.com>
In-Reply-To: <20150416215238.37FBBC03DD@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

> You mentioned trying to perform a similar look-up for exit policies
> using Atlas.
Yes, I tried "25" or "port 25" in Atlas' search, but did not get any
results... it seemed like the most intuitive place to look for port
info. Searching in the local database did not occur to me, before you
mentioned it.

S.

l.m:
> Hi again,
> 
> To demonstrate further the importance of port choice I think a
> clarification is in order. From tor's spec [0] an exit may specify an
> accept or reject policy. So the number of exits that may allow your
> exiting traffic (in this case mail) is those that "accept" and those
> that don't "reject". Keep that in mind when parsing your data in
> whichever method. The count is roughly 12 exits for port 25 versus 657
> for port 587. The choice of exit is influenced by exit bandwidth and
> successful use (in the short-term).
> 
> You mentioned trying to perform a similar look-up for exit policies
> using Atlas. I didn't see an easy way to do so from the protocol [1]
> used by Atlas. It's possible to perform the same inspection of exit
> policy (as parsing/cat+grep local data) using the wget command with a
> parametrization of the details method. There's no built in way to just
> get the count of exits allowing some exit traffic. Or is there? Maybe
> this would be a useful feature? It would allow a more informed choice
> (12 versus 657 out of ~1000).
> 
> --leeroy
> 
> [0] https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt#n2273
> [1] https://onionoo.torproject.org/protocol.html
> 
-- 
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

