Delivery-Date: Wed, 04 May 2016 08:18:42 -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_SIGNED,
	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 89E0F1E0501;
	Wed,  4 May 2016 08:18:40 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 7D4EA3AA74;
	Wed,  4 May 2016 12:18:37 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A4F663AA71
 for <tor-talk@lists.torproject.org>; Wed,  4 May 2016 12:18:33 +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 y19bmp6RxWAo for <tor-talk@lists.torproject.org>;
 Wed,  4 May 2016 12:18:33 +0000 (UTC)
Received: from mail-wm0-x236.google.com (mail-wm0-x236.google.com
 [IPv6:2a00:1450:400c:c09::236])
 (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 5FF0D3AA56
 for <tor-talk@lists.torproject.org>; Wed,  4 May 2016 12:18:33 +0000 (UTC)
Received: by mail-wm0-x236.google.com with SMTP id g17so90603243wme.1
 for <tor-talk@lists.torproject.org>; Wed, 04 May 2016 05:18:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=ahmia-fi.20150623.gappssmtp.com; s=20150623;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to;
 bh=9p7Z41WsSno9VINkGp+3Bm1U8BBUxImLFbqHhONcDw4=;
 b=ZonDPZs643Uge0Hr4LnwhHA/Xdcn1bBmFjoIq99pSCbIug1eMP5GQ9Dka8H/N2KeHS
 nsU0Hb17pgoxwawHQd6H8EoENDH96vYJi1fVQuoI/2Ndw5ESTIw/QnCjiZz4tJiEeJ8F
 NmpKQFNF/K03XERvkKuJ1oIKoKoNPaK1EsodPKoqV9Sf6JiGOgSJcX3OHQlIlwMXNpt3
 4Z1rWqAgeeSC3qPEzWuIS0ki4j6MGVX1Z8G2m00lKHrw8AJYtrVlbwit2CiMtGtTwMiO
 ykgRiOWoPtCjFHQyfWVIMfwzFJPvRTjYQV9/SISYaNZHTjWs4pjPJXyouNpphqzzCvtX
 R95g==
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=9p7Z41WsSno9VINkGp+3Bm1U8BBUxImLFbqHhONcDw4=;
 b=jpCxyQ9Jxz1DK90vF4s+vFnmo+b8LhFiuDQ1hIf0fpcxdrwTl4RwfT8yP5VtrTNPkY
 GbVq58FUlnE5wm0DV35kQZWCuiTJ9oV9o9eLZqUmR3Lo3WWSu1ZK/13psgJe4aWBgyTw
 L76w0Be47J9LLZ4zwjx0UA4pK2VszktJLds16+/2x8mXUNXY16R7IwXXTHS6DzcFu+Ji
 9t8ka0cz59IU3+CCuJODInqeFmijPRMu3b0FXqrVb6Jn01hmDjlt7pYPfCywMLvERM73
 mdQ6u0A7ZPcUkmkOiQENlUnE3UWV5URPNbSBVwH1JNvNrMtIjvvvcWlS9uqby4m9+Bfz
 Ju1g==
X-Gm-Message-State: AOPr4FVCNxCWN2gaRGbYRm8B0vODPmcFGDmsMP9YFdHXHl3MicO3wMUNO682MWsUpv3ZtaP7w+lp0KArJNYLlw==
MIME-Version: 1.0
X-Received: by 10.28.175.143 with SMTP id y137mr16169766wme.21.1462364310345; 
 Wed, 04 May 2016 05:18:30 -0700 (PDT)
Received: by 10.28.35.4 with HTTP; Wed, 4 May 2016 05:18:30 -0700 (PDT)
X-Originating-IP: [130.230.147.130]
In-Reply-To: <5729E33D.3080706@mailbox.org>
References: <CAJ8LpWp_yr5KDSHKg0z72FL-s82QYNVaS9Ob5efzftViTqnA=Q@mail.gmail.com>
 <5729E33D.3080706@mailbox.org>
Date: Wed, 4 May 2016 15:18:30 +0300
Message-ID: <CAJ8LpWpTNxBvPqRut=ELX-XC2V60p8v0u5S7p+iRnE0Lu10M2A@mail.gmail.com>
From: "Nurmi, Juha" <juha.nurmi@ahmia.fi>
To: Tor Talk <tor-talk@lists.torproject.org>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
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>

> Are you sure it was a man-in-the-middle?
>
> May be, the other communication partner uses another device?

First we started a fresh conversation and messages went through. We
compared our fingerprints using other channel and they didn't match. After
this I restarted my Tor Messenger and then fingerprints matched. All the
time we used same devices.

Are there any other explanations than MITM?

-Juha
-- 
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

