Delivery-Date: Sat, 31 Jan 2015 00:42:18 -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.7 required=5.0 tests=BAYES_00,DKIM_ADSP_CUSTOM_MED,
	DKIM_SIGNED,FREEMAIL_FROM,RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,
	URIBL_BLOCKED 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 B76B71E0B3D
	for <archiver@seul.org>; Sat, 31 Jan 2015 00:42:16 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id CAF5F32F4F;
	Sat, 31 Jan 2015 05:42:13 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 7D4DC32F38
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 05:42:10 +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 Dm0YU51LW8sV for <tor-talk@lists.torproject.org>;
 Sat, 31 Jan 2015 05:42:10 +0000 (UTC)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com
 [IPv6:2607:f8b0:4003:c06::22e])
 (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits))
 (Client CN "smtp.gmail.com",
 Issuer "Google Internet Authority G2" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 5777A32B3A
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 05:42:10 +0000 (UTC)
Received: by mail-oi0-f46.google.com with SMTP id a141so37926890oig.5
 for <tor-talk@lists.torproject.org>; Fri, 30 Jan 2015 21:42:08 -0800 (PST)
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=mH+92OqzPrvFdb99IT7ijS6tKykpbfYFMYrnI2MwpCE=;
 b=CsdZiR+QVyGc3+YC9Ji1T7SdqCPw9Kpuqg2bdwH391b88TwHWNhsqMlCWnrvEy72bK
 eQdKn4lKJsT9bVn2m4jzf/rAN8pZPxFYzGS6hLyi+rrLKfQlTFHKI3Xyv4Wr6YSicWTj
 Nd3ME34xzxq9GWq86I2Dhk/LxgrAU78h6ZNljBvqb39xC2Y2tGxtOMOZHVtY6+qDIKAv
 OHbGDbQftQyY7O9eox/ZtAWuJrWxl9oRumeFjDrQSs7ZdZiycTALkKCj6nwEVoQ0EHaZ
 tlxyLpt2knmUMtnentvJHEmkLsGssNHo4/0CKDrTzHdzqhJL4mCSY8+KloUAnMJSXmjc
 14tQ==
MIME-Version: 1.0
X-Received: by 10.182.241.133 with SMTP id wi5mr5874883obc.10.1422682928091;
 Fri, 30 Jan 2015 21:42:08 -0800 (PST)
Received: by 10.60.31.71 with HTTP; Fri, 30 Jan 2015 21:42:08 -0800 (PST)
In-Reply-To: <54CC3D22.8040707@riseup.net>
References: <54CB577A.9000100@riseup.net> <54CB59D5.5040300@riseup.net>
 <54CB5D63.5000108@techwang.com> <54CB689A.3010402@riseup.net>
 <op.xtahyknnbgbjo9@work-pc.lan> <54CC27AE.5060805@riseup.net>
 <op.xtaza906bgbjo9@work-pc.lan> <54CC3D22.8040707@riseup.net>
Date: Sat, 31 Jan 2015 00:42:08 -0500
Message-ID: <CAD2Ti2-Z54O38qZb-EFUwqLy5o1Be7wxVPDhS391F29t6TGSCQ@mail.gmail.com>
From: grarpamp <grarpamp@gmail.com>
To: tor-talk@lists.torproject.org
Subject: Re: [tor-talk] Tor -> VPN Clarification
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 Fri, Jan 30, 2015 at 9:25 PM, Mirimir <mirimir@riseup.net> wrote:
> On 01/30/2015 06:19 PM, Seth wrote:
>> If I remember correctly it has to do with the ability to correlate VPN
>> traffic on the last 'leg' of the connection from you to your VPN
>> provider vs traffic on the last leg of journey from Tor exit to your
>> desired destination.
>
> How is that any worse than adversaries correlating traffic between your
> ISP and entry guards with traffic between exit nodes and destinations?
>
> Tor is by definition vulnerable to such adversaries.
>
> I've been thinking about testing such matters.
> What's the best open-source software for traffic correlation?
>
> actually usable without coding from basic principles.

Ask the NSA.
They're about the only ones with need for such tools.
You might make some basic proof of example with netflow
tools whether as in unix kernel and/or third party, plus the free splunk.
Watch your own service plus you and ten of your friends accessing it
simultaneously. Give a presentation at a con, maybe they'll recruit you :)
-- 
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

