Delivery-Date: Mon, 22 Feb 2016 08:11:30 -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_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 46DC41E03B6;
	Mon, 22 Feb 2016 08:11:28 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 80DFF390B7;
	Mon, 22 Feb 2016 13:11:23 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 7703738FEB
 for <tor-talk@lists.torproject.org>; Mon, 22 Feb 2016 13:11:19 +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 IkwNEOPigCQe for <tor-talk@lists.torproject.org>;
 Mon, 22 Feb 2016 13:11:19 +0000 (UTC)
Received: from mail-wm0-x22e.google.com (mail-wm0-x22e.google.com
 [IPv6:2a00:1450:400c:c09::22e])
 (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 3117138D03
 for <tor-talk@lists.torproject.org>; Mon, 22 Feb 2016 13:11:16 +0000 (UTC)
Received: by mail-wm0-x22e.google.com with SMTP id c200so170423906wme.0
 for <tor-talk@lists.torproject.org>; Mon, 22 Feb 2016 05:11:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=subject:to:references:from:message-id:date:user-agent:mime-version
 :in-reply-to:content-type:content-transfer-encoding;
 bh=NiOVrlwct5wK/ac2bk12W3Vv2+M64W6a9iQjv8W9jx8=;
 b=TJy5uloYpZKQrsL6kzny+U1lRYxFtmUPwG4D8PgkdMcK0bBlIrfQUlEJcuKF9vF1Pv
 s+/g0oIsWNxWoBqregQeFkQq3R1HOEubsbGi+C+O7ph53n7G0v5tFhJ/36067svA5LMo
 qagq1ZqVXvWDkiZQOiwAY7RuwH3a+6HigSty0+swGPafDZnEbbMLm9n8uyr6JKti8iM7
 Z64ZBHP3C7cZVrpKc6hQxXqP5uE9+UdSm3XgMgj58CXGuHDeMdwr0oEeJwvz1BKqrocv
 eoSnKRWxLAhYL9DfUO+TAoTDCq6wYqEprt6DMihvZk9vzTHWZUSqmmaE0hbHhKamJd4m
 L2Gg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:subject:to:references:from:message-id:date
 :user-agent:mime-version:in-reply-to:content-type
 :content-transfer-encoding;
 bh=NiOVrlwct5wK/ac2bk12W3Vv2+M64W6a9iQjv8W9jx8=;
 b=YBzc5KowAzqT5+Yx6qWwFS7bIdQz/0clzICx4ipRERGjjljnqUTwc8j1JTjcdPTm9F
 hY9XWKudqhD1AiZpdg0qitecT1bBY+2x67Twg/e9VvM3iGppwAdZPYNAAYg1TG/U9ua4
 jYL59n3qz/Laby1tSIsb+6YXzkBipAUD5FTOODlO7nm8k3YLovjd0BJfvHarNuFddyOw
 LAP/C2TbZUA3PFbRMCccjScmyRWN8yi/8JQXMU72KyLtSPROw5HWy93Tk3LDQZvFuq6A
 EE2UihP1gtFiCBw3mGWQlyzWis+dt/FFf+l3puptjmkOYm4ugsfoZE3YAUUVydbubAep
 W6PA==
X-Gm-Message-State: AG10YOTZEgeTDxSdvh7B7ZsnROAF1K4qNhuxWjlchQiSC6v7CAq4EhTyg+QgI2gpepnkvA==
X-Received: by 10.28.104.87 with SMTP id d84mr12844854wmc.56.1456146673334;
 Mon, 22 Feb 2016 05:11:13 -0800 (PST)
Received: from [192.168.1.10] (ANice-654-1-129-250.w86-203.abo.wanadoo.fr.
 [86.203.216.250])
 by smtp.googlemail.com with ESMTPSA id i5sm24586910wjx.15.2016.02.22.05.11.12
 for <tor-talk@lists.torproject.org>
 (version=TLSv1/SSLv3 cipher=OTHER);
 Mon, 22 Feb 2016 05:11:12 -0800 (PST)
To: tor-talk@lists.torproject.org
References: <267a369a2d18b7fffbbe43d7e3f64e04@openmailbox.org>
 <4447BCF0-27C5-47D9-A9AD-76261F0BFFF2@riseup.net>
 <CAKkunMbnp4UkEH98ysnNDjM6+ON-QA=XMcVNV3cLnZXYLQvrhA@mail.gmail.com>
 <CABMkiz5HDjayzywjCvebQL3dbzQav8Yj5msfGQG5CZ3D0UsVPQ@mail.gmail.com>
 <4456E28E-CDAF-4C64-988B-E52DB3DF97C9@riseup.net>
From: Aymeric Vitte <vitteaymeric@gmail.com>
X-Enigmail-Draft-Status: N1110
Message-ID: <56CB08F1.8050805@gmail.com>
Date: Mon, 22 Feb 2016 14:11:13 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; rv:38.0) Gecko/20100101
 Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <4456E28E-CDAF-4C64-988B-E52DB3DF97C9@riseup.net>
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="windows-1252"
Content-Transfer-Encoding: quoted-printable
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

Even when you know what you are doing there can be some funny side
effects, this is really specific and not entirely related to the
original problematic of this thread but just shows that you can't master
everything even when you think you do, and anybody I believe can one day
make mistake while setting up the vpns, tor, proxies tunnels, router
conf, etc (a bit like users messing up with the Tor toggle mode when it
existed), please see
https://github.com/Ayms/torrent-live#deanonymizing-the-vpn-peers

"It has to be noted that the method works for whatever combination of
VPNs, anonymizer networks (like Tor) or proxies the peers are using."

Sorry for the brief description, maybe more later for those that are
interested.


Le 21/02/2016 21:30, Scfith Rise up a =E9crit :
> Mr. Andersson is assuming a lot. There are definitely tried and true meth=
ods 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 bu=
rn 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 t=
he 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 p=
aid
>> 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 l=
ead
>> 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> wr=
ote:
>>>> 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 V=
PS
>>> 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 o=
f 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

-- =

Get the torrent dynamic blocklist: http://peersm.com/getblocklist
Check the 10 M passwords list: http://peersm.com/findmyass
Anti-spies and private torrents, dynamic blocklist: http://torrent-live.org
Peersm : http://www.peersm.com
torrent-live: https://github.com/Ayms/torrent-live
node-Tor : https://www.github.com/Ayms/node-Tor
GitHub : https://www.github.com/Ayms
-- =

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

