Delivery-Date: Sun, 21 Feb 2016 15:12:59 -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 295FF1E04FE;
	Sun, 21 Feb 2016 15:12:57 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id B3B4F3984D;
	Sun, 21 Feb 2016 20:12:52 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id A1E3E3983C
 for <tor-talk@lists.torproject.org>; Sun, 21 Feb 2016 20:12:48 +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 jDDJAMZXFX7Z for <tor-talk@lists.torproject.org>;
 Sun, 21 Feb 2016 20:12:48 +0000 (UTC)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com
 [IPv6:2a00:1450:400c:c09::233])
 (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 5A9E4397FE
 for <tor-talk@lists.torproject.org>; Sun, 21 Feb 2016 20:12:48 +0000 (UTC)
Received: by mail-wm0-x233.google.com with SMTP id a4so136659158wme.1
 for <tor-talk@lists.torproject.org>; Sun, 21 Feb 2016 12:12:48 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
 h=mime-version:in-reply-to:references:from:date:message-id:subject:to
 :content-type:content-transfer-encoding;
 bh=rPNf00N6clGP+UBrC9lT+FVh1A6RFS3xEHNZiMFgbBQ=;
 b=ykb24vgSGbf98ZiJdSvMA/7vZuZCvrJbPjKvUxC33l8CoQpa2Des54oGWb2izOvQis
 3++Z8Fm/S24U7vpaUFhnDUGZuOD2Iqpo5xluHy03yV/aO7ztQjmhPo8jnfSIrcXmstui
 ColBGZs1r21xGeApVTI2PgOveCK0Fj2cg66PhOBYb2+YPoWV3s5dWVwkv9Tt0ZcRqlc5
 u6HPfO2gcJYGjLsR108e3cfLI0MsW7M7U1veMaJVNh62SSlu8iNDelRl/q+Ngg9OqoIA
 FOn1S0vuRqX9VzJ7deIc1CieM1piIQLuPSmVJq2lSqYmYCGsXkYrl2B6WrSHT7rZ8I2B
 Z85g==
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:from:date
 :message-id:subject:to:content-type:content-transfer-encoding;
 bh=rPNf00N6clGP+UBrC9lT+FVh1A6RFS3xEHNZiMFgbBQ=;
 b=F1lRfiSYRtR2t0dJ/7GyJOoii3o5mx76MPjpWazW0MgHeehByPO7EpDUta3qudJBeK
 fqTeCHkj87frX4KKVj+FzcGcrn/aKfPFSonDVaofB3pCak/CCrx3T3Eb6EGNGK0gGvfc
 CrF++aAyt2KAlNyuloR0UwkBbxnavE8+XRB19b83gYDCj17bt4DyRnSi7RSImTC5m6sN
 B5E1fQyGG86va8avsWPEZ9NIyEYttEnj5jSwcLlilv45KBfXxJgwwGqtO7Y9wc3cm824
 HZy/Qp7gCen1l/JIqeGWweM8d+jd5FzCdrN7kfHI2zFWtD3d3ksudoyGDohICNabbTRv
 sMUQ==
X-Gm-Message-State: AG10YOQoKn8bbeC7WtPzb8WGW0Wfy/shWbsFpd0p+PlTy3I9/VVG8ZgbTVpy6o4vh5ygrotAChJJod6U/dDMPw==
X-Received: by 10.194.121.99 with SMTP id lj3mr27743450wjb.55.1456085565485;
 Sun, 21 Feb 2016 12:12:45 -0800 (PST)
MIME-Version: 1.0
Received: by 10.28.113.216 with HTTP; Sun, 21 Feb 2016 12:12:05 -0800 (PST)
In-Reply-To: <4447BCF0-27C5-47D9-A9AD-76261F0BFFF2@riseup.net>
References: <267a369a2d18b7fffbbe43d7e3f64e04@openmailbox.org>
 <4447BCF0-27C5-47D9-A9AD-76261F0BFFF2@riseup.net>
From: Anders Andersson <pipatron@gmail.com>
Date: Sun, 21 Feb 2016 21:12:05 +0100
Message-ID: <CAKkunMbnp4UkEH98ysnNDjM6+ON-QA=XMcVNV3cLnZXYLQvrhA@mail.gmail.com>
To: tor-talk@lists.torproject.org
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>

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

