Delivery-Date: Tue, 02 Feb 2016 18:28:53 -0500
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=-3.3 required=5.0 tests=BAYES_00,DKIM_ADSP_ALL,
	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 ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 1A6581E0C75;
	Tue,  2 Feb 2016 18:28:52 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id C8BED3973A;
	Tue,  2 Feb 2016 23:28:46 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 7B25039732
 for <tor-talk@lists.torproject.org>; Tue,  2 Feb 2016 23:28:43 +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 WNVmYl_LDUCR for <tor-talk@lists.torproject.org>;
 Tue,  2 Feb 2016 23:28:43 +0000 (UTC)
Received: from smtp3.openmailbox.org (smtp3.openmailbox.org [62.4.1.37])
 (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 4D9E03971E
 for <tor-talk@lists.torproject.org>; Tue,  2 Feb 2016 23:28:43 +0000 (UTC)
X-Greylist: delayed 616 seconds by postgrey-1.34 at eugeni;
 Tue, 02 Feb 2016 23:28:43 UTC
Received: by mail2.openmailbox.org (Postfix, from userid 1004)
 id B96672AC3F5F; Wed,  3 Feb 2016 00:18:23 +0100 (CET)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=openmailbox.org;
 s=openmailbox; t=1454455103;
 bh=/50NCtVgzlqyw03txG8PlrwiOUlCtbQYST9gTKQJEnk=;
 h=Date:From:To:Subject:From;
 b=LDbg8CU4V2K/a7xR17mcKMryLvgeZLtHMmmPxYyf61+eFphSGT7f0k2NIRe8/Uy8x
 Gf0D4OSKKGA0g6pKZcNbH/BLLkjp4S3mJqD2mvzfy68vAwpLNVEj/JFboAXpzhr0z3
 v0ZWgbzSvX+D7pb+cih6N0HTRE7UjDjAx3n2FXHk=
Received: from www.openmailbox.org (openmailbox-b2 [10.91.69.220])
 by mail2.openmailbox.org (Postfix) with ESMTP id 9DC842AC10F2
 for <tor-talk@lists.torproject.org>; Wed,  3 Feb 2016 00:18:23 +0100 (CET)
MIME-Version: 1.0
Date: Tue, 02 Feb 2016 23:18:23 +0000
From: blobby@openmailbox.org
To: tor-talk@lists.torproject.org
Message-ID: <ccdb66c6046b492cff1abc9f44e160ce@openmailbox.org>
X-Sender: blobby@openmailbox.org
User-Agent: Roundcube Webmail/1.0.6
Subject: [tor-talk] =?utf-8?q?Why_does_Facebook_claim_my_Russian_exit_node?=
 =?utf-8?q?_is_in_Colombia=3F?=
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Can someone please explain why services like Facebook and Gmail are so 
wrong when they attempt to geo-locate exit nodes.

As an example, I set ExitNodes to {ru} and logged into my Facebook. This 
locked my account. When I logged in Facebook told me there was a 
suspicious login. It claimed the IP address of the exit node in Russia 
resolved to Colombia! I checked the IP address with WHOIS - it's in 
Russia.

Can anyone tell me why exit nodes are frequently placed in a totally 
wrong location by companies like Facebook which must have complex 
algorithms to detect where their customers are from.

Is it something to do with the exit node as I can't imagine how Facebook 
could get it so wrong.
-- 
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

