Delivery-Date: Mon, 13 Apr 2015 16:14:00 -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 0EDAD1E105C
	for <archiver@seul.org>; Mon, 13 Apr 2015 16:13:58 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E7618330F9;
	Mon, 13 Apr 2015 20:13:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AD54C31B88
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 20:13:50 +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 b1YUWwaEUAt8 for <tor-talk@lists.torproject.org>;
 Mon, 13 Apr 2015 20:13:50 +0000 (UTC)
Received: from smtp3.hushmail.com (smtp3.hushmail.com [65.39.178.200])
 (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 884BA21013
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 20:13:50 +0000 (UTC)
Received: from smtp3.hushmail.com (localhost [127.0.0.1])
 by smtp3.hushmail.com (Postfix) with SMTP id D6CDDE01F4
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 20:13:47 +0000 (UTC)
Received: from smtp.hushmail.com (w8.hushmail.com [65.39.178.52])
 by smtp3.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Mon, 13 Apr 2015 20:13:47 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id AAB07E042D; Mon, 13 Apr 2015 20:13:47 +0000 (UTC)
MIME-Version: 1.0
Date: Mon, 13 Apr 2015 16:13:47 -0400
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <552C1EAF.1030403@sophiehassfurther.com>
References: <5527BB80.8010708@sophiehassfurther.com>
 <20150410183853.GA32173@riseup.net> <552820C1.8050203@sophiehassfurther.com>
 <20150410215018.F057CC0D3A@smtp.hushmail.com>
 <5528C834.7020305@sophiehassfurther.com>
 <20150413162129.5039CE0432@smtp.hushmail.com>
 <552C1EAF.1030403@sophiehassfurther.com> 
Message-Id: <20150413201347.AAB07E042D@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
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 Sophie,

"Sophie Hassfurther"  wrote:
>How do I look up which ports work on which exit 
>nodes? I tried searching Atlas, but I didn't find 
>out how to do a reverse search.

Glad to see the problem appears sorted. To find exit policies I used
the cat and grep commands on microdesc data. This data is available on
the CollectTor website as well as locally in your Tor Browser folder.
After loading Tor Browser, do a search for cached-microdescs in the
Tor Browser install folder. If you then open a terminal at the
location and use (for simplicity):

cat cached-microdescs | grep accept

That gives you an idea of accept policies. If you add to that:

cat cached-microdescs | grep accept | grep portnumber

That gives you an idea of how many exits (that you know about) which
accept portnumber. If you add to that:

cat cached-microdescs | grep accept | grep portnumber | wc -l

You'll have (very roughly) the number of exits. I'll leave it to you
to search the man pages for better expressions to use with grep ;) In
your case the number of exits accepting port 25 was quite small.
--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

