Delivery-Date: Sat, 06 Feb 2016 15:46:15 -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=-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 ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 7907B1E00E5;
	Sat,  6 Feb 2016 15:46:13 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B6A0A39A65;
	Sat,  6 Feb 2016 20:46:06 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 7C53D39A5E
 for <tor-talk@lists.torproject.org>; Sat,  6 Feb 2016 20:46:03 +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 FR0wE0fNOar7 for <tor-talk@lists.torproject.org>;
 Sat,  6 Feb 2016 20:46:03 +0000 (UTC)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com
 [IPv6:2607:f8b0:4003:c06::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 53BB039A57
 for <tor-talk@lists.torproject.org>; Sat,  6 Feb 2016 20:46:03 +0000 (UTC)
Received: by mail-oi0-x22a.google.com with SMTP id j125so60938375oih.0
 for <tor-talk@lists.torproject.org>; Sat, 06 Feb 2016 12:46:03 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=literati-org.20150623.gappssmtp.com; s=20150623;
 h=mime-version:references:in-reply-to:from:date:message-id:subject:to
 :content-type; bh=w7RYH2kQvlewKWo31dvolqfuEkYUzHwxQCspgbcMlwk=;
 b=IxZvFMVNfCoJ+SdA9rM1su7tX42egvbT6wJlWZ7v8mkjiDtbSJTNnvL4vb4cu6plEp
 cUUSGZMrUSZmPv83Yg3tWxmtqWdyBa95pdZtR96rsT8/FCpiQ8oFUKBvBRnHqKaZVXTX
 msauF6o+iZTN7XZVU15fZONZ0yXnr/mxXwMmy0AGgpOiWwO9t1qyzsMx/mjoFATB1Wl6
 tizTDiVkPa7g7WmeskGg6OUXvbmD94p1rqOyINUDUrbgLrKDdw+Ww6UjVDcle3Oocxjp
 9GH7BeQuobiGgvQzUa85f2FIi6kpQR5ERn+BFycuwc9nH6Arovqa7b9aJ3NJdLYXcGD+
 5QHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:references:in-reply-to:from:date
 :message-id:subject:to:content-type;
 bh=w7RYH2kQvlewKWo31dvolqfuEkYUzHwxQCspgbcMlwk=;
 b=kxfHsHR+jZNAMJjm1m6DCbjHDS/76+5TpEeV5F66G+BQWzwnQGaqpuojkpYtzdES+y
 BmB1t9SA4hZcYUOZf2wozB8HPYyY+gayULb7azCokQ0wXQdCUguG3Pye3hPXzjrgwZHy
 z9le7REsK3fe5NrYlFvslaAWa1kcS+YSbnb6HTgd3pfnVt92vtOE8cosAzlcac+ZqLcp
 FC8CfFAmZccK2/KYOyZ40geQpCmOCzgPI93rV0/pxcR7g5Xa9rJtNuz3ybwcHT4CgLM3
 +ckuBAEJIW2Dfnd9LNEjNJe7YNu0dCSDGM25v6kughqvrflYBmFqEtz5rlQ6Tfip/2TD
 F1VA==
X-Gm-Message-State: AG10YORHhqyBBW/gQa1MNsQPXJkNSc3x7xIMoBKJCK1kiISvWjYYuk9IaQ0SlH7EClsNPkPZIH2rTTTPdW8oaQ==
X-Received: by 10.202.48.149 with SMTP id w143mr13687202oiw.109.1454791561016; 
 Sat, 06 Feb 2016 12:46:01 -0800 (PST)
MIME-Version: 1.0
References: <ccdb66c6046b492cff1abc9f44e160ce@openmailbox.org>
In-Reply-To: <ccdb66c6046b492cff1abc9f44e160ce@openmailbox.org>
From: Sean Lynch <seanl@literati.org>
Date: Sat, 06 Feb 2016 20:45:51 +0000
Message-ID: <CAHKdp-njTc4_aURGD8PdyzhvUKcLFK688Xsb4W7vAdwCSFx5GA@mail.gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Why does Facebook claim my Russian exit node is in
	Colombia?
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>

Geolocation data for IPs is of varying quality. Facebook's likely comes
from a combination of commercial and open/free sources, along with some
machine learning based on features of people coming from those IPs. For the
most part, I doubt Facebook is trying to look at/parse the whois data
directly, since often the address of the owner of a block has nothing to do
with the actual location of a block.

On Tue, Feb 2, 2016 at 3:28 PM <blobby@openmailbox.org> wrote:

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

