Delivery-Date: Mon, 09 May 2016 02:28:54 -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.1 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,T_DKIM_INVALID,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 AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 2225B1E0AE8;
	Mon,  9 May 2016 02:28:53 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 1AC143A577;
	Mon,  9 May 2016 06:28:48 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 58B243A2C9
 for <tor-talk@lists.torproject.org>; Mon,  9 May 2016 06:28:44 +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 MThE3m7ShvIy for <tor-talk@lists.torproject.org>;
 Mon,  9 May 2016 06:28:44 +0000 (UTC)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com
 [IPv6:2607:f8b0:400c:c05::22a])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 3374F38333
 for <tor-talk@lists.torproject.org>; Mon,  9 May 2016 06:28:44 +0000 (UTC)
Received: by mail-vk0-x22a.google.com with SMTP id s184so54355484vkb.3
 for <tor-talk@lists.torproject.org>; Sun, 08 May 2016 23:28:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to;
 bh=MTcBI43Cn9gYGEYpn9RBhQ14f82gXv9smQnjLQ5aErA=;
 b=ZNy/zIDe0sesSxdUcjkx5C8GZTeA1x9rKSZJA7+YfmEhKQ1zJ772MxVCoxEC054AAe
 lrmivdv4sErnr8zEU9nO4okQM4G9Lu7xL6EGcjdzwKhE+HzCLHrpjGczmqniiNyDMsfq
 dNK2nE7Ekbxk552zhDEQ2igPMcDh3ds4cKkVTHfS8RtUs7rml3fJidYGbALqeQTc+tkJ
 Oks+87znYWE2J4UaxOaXUXpKNO5/Zmo6FYdVuy6fn3yMBCGr5BYWSDP+YvTcapO9MdUL
 Fcv5hQfe5I6ov9FbXL/KFpPFN/40fzJgyEX6G0WNaHXPo8v/R2njCmnSCfb8qjPVqQdO
 Xsiw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to;
 bh=MTcBI43Cn9gYGEYpn9RBhQ14f82gXv9smQnjLQ5aErA=;
 b=T+FdxcraPPPyXe6mRxZKkQf5dgw8WccGL4E9AWPG/flnahD+2ACgMWrCgsPf0YVuJD
 sVOkMlw5h1BBKzFOeuuawiXSpFI6bnabiU9dcPZJir5icwPmc13wMvl6gPF00wLMyJtq
 zsh3oBI54vRpWncVdOYesJaBwSVPc3okSIQZd885oSiUIK3dcZpWThYGC6A9g2rTvfUF
 CmASbSvUPqaYAvCc1zhWWQ98pUsl36SjODb9iSP7a5cM1HXzkdnxT04R85vBmgvtToV2
 6EuBz05BFZEXFg43FCtxc5H6rMbbyrGfG/pxcAYsEzy/FeKTXVXZyIGSl2bsg+cNPkEF
 8v7A==
X-Gm-Message-State: AOPr4FXHdkCqCT411CVczr4pyMFtRdJnj0z3EM2frLBdNsLSWv5HYOYasyVklp5WtPa+5IfyR2xlDhD34O3Gsw==
MIME-Version: 1.0
X-Received: by 10.159.36.51 with SMTP id 48mr19427316uaq.74.1462775321566;
 Sun, 08 May 2016 23:28:41 -0700 (PDT)
Received: by 10.159.33.33 with HTTP; Sun, 8 May 2016 23:28:41 -0700 (PDT)
In-Reply-To: <CAJ8LpWp_yr5KDSHKg0z72FL-s82QYNVaS9Ob5efzftViTqnA=Q@mail.gmail.com>
References: <CAJ8LpWp_yr5KDSHKg0z72FL-s82QYNVaS9Ob5efzftViTqnA=Q@mail.gmail.com>
Date: Mon, 9 May 2016 02:28:41 -0400
Message-ID: <CAD2Ti29Lj538m-Z8PdOTBDAtM6pV0LFDGMV9evWWPfrTxffG9A@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] MITM attack: How to see Tor Messenger's exit node?
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>

On 5/4/16, Nurmi, Juha <juha.nurmi@ahmia.fi> wrote:
> There seems to be a man-in-the-middle attack. The attacker probably is an
> exit node.
> ...
> Is there a way to see the exit node that Tor messenger is currently using?
> I need this info to test the exit node and report it to Tor Project if it
> seems to perform this man-in-the-middle attack.


You could see, monitor, and verify the exit in use, both in realtime
and historically, by any and all apps, regardless if they have such
info builtin, and without installing extra tools, if people adopted this...

# Combine setevents circ and stream
https://trac.torproject.org/projects/tor/ticket/11179

Till then we're going to continue to be bombarded by
'What exit use?', 'How my system / apps using tor'.
-- 
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

