Delivery-Date: Fri, 22 May 2015 17:26:34 -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 ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id 7B3671E0F1C
	for <archiver@seul.org>; Fri, 22 May 2015 17:26:32 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E7E0E35879;
	Fri, 22 May 2015 21:26:27 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 50E1F35818
 for <tor-talk@lists.torproject.org>; Fri, 22 May 2015 21:26:24 +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 Uol-YFQdvDCf for <tor-talk@lists.torproject.org>;
 Fri, 22 May 2015 21:26:24 +0000 (UTC)
Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com
 [IPv6:2607:f8b0:4001:c05::235])
 (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 351DF35753
 for <tor-talk@lists.torproject.org>; Fri, 22 May 2015 21:26:21 +0000 (UTC)
Received: by igbsb11 with SMTP id sb11so322936igb.0
 for <tor-talk@lists.torproject.org>; Fri, 22 May 2015 14:26:19 -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
 :content-type; bh=VmJg4h64/95ppoqcF6tcgcLS0f8tVTLl0zmfgeD3QFM=;
 b=kSNt4FIvaoZMtM9MjEUMz5h+2xecy4viZ8l1T/TPBsxmP9O6CjA1J0ftOiQAtyvR9Y
 p6mExN8tMAgJjRXRfwCj5GKbaRqeqCrfOVUEpV0eWs5rXNkLuccqzxut+loGxqvwcRnv
 KlnMn0SmbqKyBj/fPm43pAAAw/TiTHxmvdWJkJU6IHTZm/UKGxwMZnhsC5/gk1Y1QmM9
 RQ253UWGiQF+VthoDFrM+PmoK87DyZYwcL9KBqLn1GDW9dQlwPpt7UZdM0aQxdMi8lFm
 R6IrFp7RNC4dW5EqIijPcKJCUas3ZzMg6x0PtZ8+TQoahiKBsIHHOfyfeO0GSQl5v165
 BBsw==
MIME-Version: 1.0
X-Received: by 10.43.65.19 with SMTP id xk19mr12035205icb.20.1432329979017;
 Fri, 22 May 2015 14:26:19 -0700 (PDT)
Received: by 10.36.34.203 with HTTP; Fri, 22 May 2015 14:26:18 -0700 (PDT)
In-Reply-To: <555F9ACE.4020707@rawbw.com>
References: <555F9ACE.4020707@rawbw.com>
Date: Fri, 22 May 2015 17:26:18 -0400
Message-ID: <CAA+0wAH0RPP4Ga0Qj77wMS70PaF7gmtBJLqjCxOZ+DFyqyQOmw@mail.gmail.com>
From: Rishab Nithyanand <rishabn.uci@gmail.com>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] New Astoria Tor client is said to be better than
	plain Tor
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>

Hey Guys,

I'm one of the authors of Astoria. It's a very new system that tries to
improve the current Tor relay selection algorithm by using the
state-of-the-art in AS path inference and measurement tools to detect the
possibility of having the same AS on the paths between the (client, entry)
and (exit, destination).

Our evaluation shows that it does quite well to avoid asymmetric
correlation attacks, but the performance is a bit off from Tor (metric:
page load times for Alexa Top 100 from 10 countries).

But to be clear: the only thing changed is the entry and exit node
selection in the Tor circuit construction. We don't require any
modifications to the Tor eco-system and infrastructure.

Unlike previous AS aware clients, we also perform load balancing to not
overwhelm the slower relays, consider the case where it is impossible to
build any attacker-free circuits, and also consider that ASes from the same
organization might collude with each other.

This blew up less than 24 hours after updating our paper on Arxiv. We're
working on cleaning up the source code and will have it ready soon (about a
week).

Rishab


On Fri, May 22, 2015 at 5:08 PM, Yuri <yuri@rawbw.com> wrote:

> This story
> http://www.dailydot.com/politics/tor-astoria-timing-attack-client/ has
> been injected into all possible news streams today.
>
> Is there any merit to it?
>
> Yuri
> --
> 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

