Delivery-Date: Sun, 24 Jan 2016 17:12:01 -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.2 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,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 7739C1E051A;
	Sun, 24 Jan 2016 17:11:59 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 2550636811;
	Sun, 24 Jan 2016 22:11:53 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3772C36811
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 22:11:50 +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 gsGxzmmccHyd for <tor-talk@lists.torproject.org>;
 Sun, 24 Jan 2016 22:11:50 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
 (using TLSv1 with cipher AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by eugeni.torproject.org (Postfix) with ESMTPS id 0696834C90
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 22:11:50 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
 (envelope-from <gno-or-talk-2@m.gmane.org>) id 1aNSsr-00027p-Ck
 for tor-talk@lists.torproject.org; Sun, 24 Jan 2016 23:11:45 +0100
Received: from destiny.enn.lu ([94.242.246.23])
 by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 23:11:45 +0100
Received: from o.wendel by destiny.enn.lu with local (Gmexim 0.1 (Debian))
 id 1AlnuQ-0007hv-00
 for <tor-talk@lists.torproject.org>; Sun, 24 Jan 2016 23:11:45 +0100
X-Injected-Via-Gmane: http://gmane.org/
To: tor-talk@lists.torproject.org
From: Oskar Wendel <o.wendel@wp.pl>
Date: Sun, 24 Jan 2016 22:11:38 +0000 (UTC)
Lines: 34
Message-ID: <n83i6p$3c6$4@ger.gmane.org>
References: <n82b3t$g4v$1@ger.gmane.org> <56A53291.8060708@gmail.com>
 <56A53342.1010502@riseup.net>
 <B215E953-7E06-4502-9BD8-1D19B8987B79@riseup.net>
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: destiny.enn.lu
Subject: Re: [tor-talk] Using VPN less safe?
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>
MIME-Version: 1.0
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>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Flipchan <flipchan@riseup.net>:

> Instead of goin vpn->tor You could go i2p->tor

It's a bit offtopic, but still interesting. So you mean routing i2p 
through Tor?

I conducted some experiments some time ago (I don't trust i2p enough to 
run it through the clearnet and I wanted to play with it, so I tried to 
run it through Tor), but I couldn't get it to connect anywhere. Will i2p 
run with only outbound TCP (no inbound TCP, no UDP at all)? Is there some 
FAQ available on how to torify i2p?

Maybe it failed because I tried to stick to the Socks port approach, maybe 
it would be easier to do with the transparent proxy approach... I must try 
it this way.

- -- 
Oskar Wendel, o.wendel@wp.pl.REMOVE.THIS
Pubkey: https://pgp.mit.edu/pks/lookup?search=0x6690CC52318DB84C
Fingerprint: C8C4 B75C BB72 36FB 94B4 925C 6690 CC52 318D B84C
-----BEGIN PGP SIGNATURE-----

iQEcBAEBAgAGBQJWpUwYAAoJEGaQzFIxjbhMyAUH+wU9SilUb4UUu0FKAOctHrn8
qdzgdGPoIwJp2br6xcCHsG4ZPD42i+vrYXKkGwVY8mtSqURpqgcpoSCtuqJdweI9
qCTpgRaL1b08+DxBHbhaz0omCvXk93QiSQCYgg6T6dya0i1fMV4JlekLErxPIlvA
/fTItK/YiieTFbHeVFEEbjH7Jgc7TAqCWk6I/9zd5ch0skLFho1R/c6WqGU/hPC1
qvF4dEAd3RW1Q9WVUjDfMlzFMBL6V/to7MY8AiVrYGXd/hthsH+/PfJN/1B3O/dC
fvC7V/vks6AZxj0RJ9mBoA9NXYv/WVKzogno41ZPNnSePcZVhh+/JD9Ei9Seuuo=
=qlIg
-----END PGP SIGNATURE-----

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

