Delivery-Date: Thu, 03 Jul 2014 05:26:59 -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.7 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	FREEMAIL_FROM,NORMAL_HTTP_TO_IP,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,
	T_DKIM_INVALID 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 43BC91E048C
	for <archiver@seul.org>; Thu,  3 Jul 2014 05:26:58 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1840D2F3BF;
	Thu,  3 Jul 2014 09:26:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id B1C1E2E752
 for <tor-talk@lists.torproject.org>; Thu,  3 Jul 2014 09:17:41 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 AxYJk7MVaQSq for <tor-talk@lists.torproject.org>;
 Thu,  3 Jul 2014 09:17:41 +0000 (UTC)
Received: from new1-smtp.messagingengine.com (new1-smtp.messagingengine.com
 [66.111.4.221])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 968442DD87
 for <tor-talk@lists.torproject.org>; Thu,  3 Jul 2014 09:17:41 +0000 (UTC)
Received: from compute3.internal (compute3.nyi.mail.srv.osa [10.202.2.43])
 by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id C7101ABA;
 Thu,  3 Jul 2014 05:10:59 -0400 (EDT)
Received: from web1 ([10.202.2.211])
 by compute3.internal (MEProxy); Thu, 03 Jul 2014 05:10:59 -0400
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=swift-mail.com; h=
 message-id:from:to:mime-version:content-transfer-encoding
 :content-type:subject:date; s=mesmtp; bh=Y7ilwhPuilJKquZ8l2IaWPW
 gRcQ=; b=HrEnMU60HLAN0v64viCH+ooybglHcj9KUmUlh0WvmPUdSaLYr8TuycS
 E4haN0B3daJwiNRtotNZv9eI0F2g+v0y4IS9Wz5R/6MRpKj0ofFRjM/nZw91gZ1/
 ZWY05OjCYZwIqr+7jOaBH2XgGhd0MQieDHW00JzX92bz3GmIRNJE=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=
 messagingengine.com; h=message-id:from:to:mime-version
 :content-transfer-encoding:content-type:subject:date; s=smtpout;
 bh=Y7ilwhPuilJKquZ8l2IaWPWgRcQ=; b=Gco10zaLJVWR1WoZPQDxOH5HJcRx
 q5HN4k16irL7ss3gADTR1/szrA3C5/WTsh3Pu4R7orq37FVffvdKvjMqXHXkM6eA
 +QrtLWdtugpnsPpgZYoelSGavIV5HOu/vYdECD5S5jZ4LakC+ykDUjHFttxsR8cn
 /YtFqOWVJtX3iYk=
Received: by web1.nyi.mail.srv.osa (Postfix, from userid 99)
 id 29E77F01E3C; Thu,  3 Jul 2014 05:10:59 -0400 (EDT)
Message-Id: <1404378659.31048.137619933.3620B7D8@webmail.messagingengine.com>
X-Sasl-Enc: pICdFjJyjmHVmzECfP2ID1VaoQQnwaAePYfp9rardHh/ 1404378659
From: Bron Taylor <bron.taylor@swift-mail.com>
To: tor-talk@lists.torproject.org
MIME-Version: 1.0
X-Mailer: MessagingEngine.com Webmail Interface - ajax-f9f22a3d
Date: Thu, 03 Jul 2014 17:10:59 +0800
Subject: [tor-talk] Does an Exit Node will be tagged with an "Exit" flag?
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 there,

    I used the TorDNSEL to verify an ip address of an exit node whether
    I can sent some kind of traffic through that node and found
    something is weired. First the information of the node can be found
    in the cached consensus file on my system with running a tor client.
    The following is the information i got from the file:

r RaspberryPiNode W0bcalLslxBCGL+ZSEf+rcrB4kg
0i+Gakd+PPsGt7NB80GVzBNnfhA 2014-07-03 00:41:38 188.2.94.252 443 80
s Named Running V2Dir Valid
v Tor 0.2.3.25
w Bandwidth=5
p accept 25,110,119,143,443,465,995

The node is claiming that is accepting mail related traffic exit through
it, however, we can noticed that this node doesn't come with an "Exit"
flag. Therefore, I tried to send a dns query to TorDNSEL to see if the
node is in ExitList and the policy is as the same as I seen on my host:

The dns query is as the following:

dig 252.94.2.188.25.27.196.125.74.ip-port.exitlist.torproject.org

And I got the answer
"252.94.2.188.25.27.196.125.74.ip-port.exitlist.torproject.org. 1799 IN
A 127.0.0.2" from Google Public DNS. Moreover, the answer from TorDNSEL
told that the node with the ip address "188.2.94.252" is an ExitNode and
allow any smtp traffic to exit through it. However, at the same time,
the cached-consensus file doesn't show that the node is published with
"ExitFlag". I would like to ask if an Exit Node will comes with a "Exit"
flag or not? Thanks!

-- 
BR, BT
-- 
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

