Delivery-Date: Sun, 21 Feb 2016 15:30:35 -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,UNPARSEABLE_RELAY
	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 779601E04CF;
	Sun, 21 Feb 2016 15:30:33 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 593A439927;
	Sun, 21 Feb 2016 20:30:26 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 90F553990C
 for <tor-talk@lists.torproject.org>; Sun, 21 Feb 2016 20:30:22 +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 o0m0lEWxY2a2 for <tor-talk@lists.torproject.org>;
 Sun, 21 Feb 2016 20:30:22 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 51B9C3946A
 for <tor-talk@lists.torproject.org>; Sun, 21 Feb 2016 20:30:22 +0000 (UTC)
Received: from piha.riseup.net (unknown [10.0.1.163])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 5A1FC1A1E81
 for <tor-talk@lists.torproject.org>; Sun, 21 Feb 2016 20:30:19 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1456086619; bh=Iel17WE5QH2EjYJ483Wt0V1jVdjgiDZ3HQFCpD9GZk8=;
 h=From:Subject:Date:References:In-Reply-To:To:From;
 b=Pd/JnfTLHHufIiQaxXBZh8EuzKPCTZDZpW/jtI1f8w21mO4Dg40faPgclPiYl/XOZ
 zyiCRnKuL4NON/ifViWgEc6NkI5G2LjGCFSfAafNMyq8zQ382CX0tTRXhkaDGHfcNj
 v2hOqV8zGuWq7/mWOzLBGuLShrdRmHZksLdEqqNM=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: scfith) with ESMTPSA id 1F9A91C022A
From: Scfith Rise up <scfith@riseup.net>
Mime-Version: 1.0 (1.0)
Message-Id: <4456E28E-CDAF-4C64-988B-E52DB3DF97C9@riseup.net>
Date: Sun, 21 Feb 2016 15:30:17 -0500
References: <267a369a2d18b7fffbbe43d7e3f64e04@openmailbox.org>
 <4447BCF0-27C5-47D9-A9AD-76261F0BFFF2@riseup.net>
 <CAKkunMbnp4UkEH98ysnNDjM6+ON-QA=XMcVNV3cLnZXYLQvrhA@mail.gmail.com>
 <CABMkiz5HDjayzywjCvebQL3dbzQav8Yj5msfGQG5CZ3D0UsVPQ@mail.gmail.com>
In-Reply-To: <CABMkiz5HDjayzywjCvebQL3dbzQav8Yj5msfGQG5CZ3D0UsVPQ@mail.gmail.com>
To: tor-talk@lists.torproject.org
X-Virus-Scanned: clamav-milter 0.98.7 at mx1.riseup.net
X-Virus-Status: Clean
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>

Mr. Andersson is assuming a lot. There are definitely tried and true methods to make purchases online and setup identities for these types of things. At the end of the day, yes the VPS provider is the weakest link. But you can use one that has no logs, carries a warrant canary, etc. and you can burn your VPS IP address as often as you need or spin up new ones as often as you need too. This is just one of many approaches and requires you to know what you are doing in locking down the VPS besides knowing how to buy it the right way, etc. 

On Feb 21, 2016, at 3:18 PM, Ben Tasker <ben@bentasker.co.uk> wrote:

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

