Delivery-Date: Sun, 01 Feb 2015 01:53:55 -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.8 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_MED,
	RP_MATCHES_RCVD,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 E5C661E09F2
	for <archiver@seul.org>; Sun,  1 Feb 2015 01:53:53 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id E5E4432AFA;
	Sun,  1 Feb 2015 06:53:49 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id F3C2C32A51
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 06:53:46 +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 q0Y0Hb7RjDRJ for <tor-talk@lists.torproject.org>;
 Sun,  1 Feb 2015 06:53:46 +0000 (UTC)
Received: from mx.dvllc.co (mx.dvllc.co [108.61.207.97])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "mx.dvllc.co",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id AAF73329B9
 for <tor-talk@lists.torproject.org>; Sun,  1 Feb 2015 06:53:46 +0000 (UTC)
Received: from localhost (172-7-164-197.lightspeed.sndgca.sbcglobal.net
 [172.7.164.197]); 
 by mx.dvllc.co (OpenSMTPD) with ESMTPS id cadc81c8;
 TLS version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO;
 for <tor-talk@lists.torproject.org>;
 Sat, 31 Jan 2015 22:53:42 -0800 (PST)
Received: from work-pc.lan (Work-PC.lan [10.0.0.201]);
 by mail.dvllc.co (OpenSMTPD) with ESMTPS id 47a2d6f8;
 TLS version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO;
 for <tor-talk@lists.torproject.org>;
 Sat, 31 Jan 2015 22:53:41 -0800 (PST)
To: tor-talk@lists.torproject.org
References: <54CB577A.9000100@riseup.net> <54CD1B02.70304@whonix.org>
 <54CD85A8.6080601@riseup.net>
Date: Sat, 31 Jan 2015 22:53:11 -0800
MIME-Version: 1.0
From: Seth <list@sysfu.com>
Message-ID: <op.xtc9exdbbgbjo9@work-pc.lan>
In-Reply-To: <54CD85A8.6080601@riseup.net>
User-Agent: Opera Mail/1.0 (Win32)
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-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

On Sat, 31 Jan 2015 17:47:20 -0800, Mirimir <mirimir@riseup.net> wrote:

> On 01/31/2015 11:12 AM, Patrick Schleizer wrote:
>> See also:
>> https://trac.torproject.org/projects/tor/wiki/doc/TorPlusVPN
>
> | you -> VPN/SSH -> Tor
> |
> | You can route Tor through VPN/SSH services. That might prevent
> | your ISP etc from seeing that you're using Tor (VPN/SSH
> | Fingerprinting below). On one hand, VPNs are more popular than
> | Tor, so you won't stand out as much, on the other hand, in some
> | countries replacing an encrypted Tor connection with an encrypted
> | VPN or SSH connection, will be suspicious as well. SSH tunnels
> | are not so popular.
> |
> | Once the VPN client has connected, the VPN tunnel will be the
> | machine's default Internet connection, and TBB (Tor Browser
> | Bundle) (or Tor client) will route through it.
> |
> | This can be a fine idea, assuming your VPN/SSH provider's
> | network is in fact sufficiently safer than your own network.
> |
> | Another advantage here is that it prevents Tor from seeing who
> | you are behind the VPN/SSH. So if somebody does manage to break
> | Tor and learn the IP address your traffic is coming from, but
> | your VPN/SSH was actually following through on their promises
> | (they won't watch, they won't remember, and they will somehow
> | magically make it so nobody else is watching either), then
> | you'll be better off.
>
> OK, that seems about right.
>
> How is that consistent with "go to jail"?

I didn't make the claim, I just linked to it. If you want to challenge the  
claim, best take it up with the person making it.

I think he makes a good point in this slide however.

----------------------------------------------------

* VPNs provides _privacy_

* TOR provides _anonymity_

* Confuse the two at your peril
-- 
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

