Delivery-Date: Sun, 21 Feb 2016 15:18:50 -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 780BC1E04B5;
	Sun, 21 Feb 2016 15:18:48 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 9446D396D5;
	Sun, 21 Feb 2016 20:18:42 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id D49EE3969B
 for <tor-talk@lists.torproject.org>; Sun, 21 Feb 2016 20:18:39 +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 qbclh2Nuza_g for <tor-talk@lists.torproject.org>;
 Sun, 21 Feb 2016 20:18:39 +0000 (UTC)
Received: from mail-ob0-x22c.google.com (mail-ob0-x22c.google.com
 [IPv6:2607:f8b0:4003:c01::22c])
 (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 B52CC39697
 for <tor-talk@lists.torproject.org>; Sun, 21 Feb 2016 20:18:36 +0000 (UTC)
Received: by mail-ob0-x22c.google.com with SMTP id jq7so149431591obb.0
 for <tor-talk@lists.torproject.org>; Sun, 21 Feb 2016 12:18:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=bentasker.co.uk; s=google;
 h=mime-version:in-reply-to:references:date:message-id:subject:from:to
 :content-type; bh=ovmXE6jHedUdM8HWDpauEWUcQ+qhBBHAxbPSnsawibU=;
 b=irBU5wvq7swzwIvQEfLPzzXL7NNG1Xn7zTRIav0GFQvrVey+37BxDKJhG7BNYz+fHK
 LhDi2qBmiG9CDV6xlcnMjKYRuu+qvMOHv8SsUIB3WUbIuodF0nLEOPdj5MtfRCHGQM2X
 zs44kG3Hoel5lcJC8kmvjMjZpsGL+z0w/4TCo=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:mime-version:in-reply-to:references:date
 :message-id:subject:from:to:content-type;
 bh=ovmXE6jHedUdM8HWDpauEWUcQ+qhBBHAxbPSnsawibU=;
 b=Ua1ifagtiPHv74kG/lfRlXVBHLH3mxJSDQSiDhYVdR5eIwrTT1wSBREKk0vipZl0MQ
 HgN4NI3NyeP4ikF+iuf/p5rhYZ3mMOtMHldGr33cfJeNQOP0eQc3RPpT31jnfcWcmT5a
 wXBpZoPdmTMeQe1lZYy6KqAL4Ybt9uWvXFQ2wZ/2jdGYPIudT9/p2CWI1/74vOILceHd
 q3EkQiqvCN/jZtwkAH6m4zFt8ZN0jA4dNiYHIo/JE+u/5SBHm1Bi1Rn748q7qdxT2GYp
 R7dOreiSltQjFfXw4AqcjkNSpPiKLyqk8482lpiSRfZzCbG9xQN9wlS0AsbAVBiVnV04
 9A8g==
X-Gm-Message-State: AG10YOSLpamm/bUbd31EQ7t5gSbtZXVccvPjun24zUn8M1C5BjNoEfSX2wPNi/whNZMEoYokON4E03P1ufX87Q==
MIME-Version: 1.0
X-Received: by 10.60.162.102 with SMTP id xz6mr20656148oeb.62.1456085914436;
 Sun, 21 Feb 2016 12:18:34 -0800 (PST)
Received: by 10.76.69.99 with HTTP; Sun, 21 Feb 2016 12:18:34 -0800 (PST)
X-Originating-IP: [81.134.152.4]
In-Reply-To: <CAKkunMbnp4UkEH98ysnNDjM6+ON-QA=XMcVNV3cLnZXYLQvrhA@mail.gmail.com>
References: <267a369a2d18b7fffbbe43d7e3f64e04@openmailbox.org>
 <4447BCF0-27C5-47D9-A9AD-76261F0BFFF2@riseup.net>
 <CAKkunMbnp4UkEH98ysnNDjM6+ON-QA=XMcVNV3cLnZXYLQvrhA@mail.gmail.com>
Date: Sun, 21 Feb 2016 20:18:34 +0000
Message-ID: <CABMkiz5HDjayzywjCvebQL3dbzQav8Yj5msfGQG5CZ3D0UsVPQ@mail.gmail.com>
From: Ben Tasker <ben@bentasker.co.uk>
To: tor-talk@lists.torproject.org
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Is it possible to use Tor without showing a Tor IP
 to the destination?
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>

> So basically they see that someone signs up using the VPS that you've paid
for using your real name and account?

Providers do exist that don't ask for details and accept payment via
Bitcoin - so it's not impossible to do in such a way that simply
threatening the provider won't be sufficient.

Personally, though, I think it's easy to underestimate/miss some of the
risks inherent in chaining connections like that. More does not always lead
to better privacy/security. If I was going to do it though, I think I'd
probably run a hidden service on the VPN VPS rather than wasting exit
bandwidth.

On Sun, Feb 21, 2016 at 8:12 PM, Anders Andersson <pipatron@gmail.com>
wrote:

> On Sun, Feb 21, 2016 at 7:17 PM, Scfith Rise up <scfith@riseup.net> wrote:
> > I can point you in a direction that I took to accomplish this without
> having to resort to a third party VPN. I am running my own VPN from a VPS
> and added it to my proxychains file. Here is the github for proxychains-ng
> that I highly recommend. This setup accomplishes what you ask, a list of ip
> addresses that it chains through to the final destination. Your tor
> connection can be one of them or not as you wish. Enjoy.
>
> So basically they see that someone signs up using the VPS that you've
> paid for using your real name and account? Why do you even use Tor to
> connect to the VPS? If they want to know who's behind the account
> they'll just send a threatening enough letter to the VPS owner.
> --
> 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
>



-- 
Ben Tasker
https://www.bentasker.co.uk
-- 
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

