Delivery-Date: Sat, 31 Jan 2015 16:20:25 -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.8 required=5.0 tests=BAYES_00,FREEMAIL_FROM,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,URIBL_BLOCKED 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 A22531E0B9E
	for <archiver@seul.org>; Sat, 31 Jan 2015 16:20:22 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 2793E29171;
	Sat, 31 Jan 2015 21:20:19 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AA60028490
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 21:20:15 +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 3dQKdgQTC_6d for <tor-talk@lists.torproject.org>;
 Sat, 31 Jan 2015 21:20:15 +0000 (UTC)
Received: from smtp1.hushmail.com (smtp1.hushmail.com [65.39.178.135])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "smtp.hushmail.com", Issuer "Self-signed" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 757E8218F7
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 21:20:15 +0000 (UTC)
Received: from smtp1.hushmail.com (localhost [127.0.0.1])
 by smtp1.hushmail.com (Postfix) with SMTP id AB72B40108
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 21:20:12 +0000 (UTC)
Received: from smtp.hushmail.com (w3.hushmail.com [65.39.178.62])
 by smtp1.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Sat, 31 Jan 2015 21:20:12 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id 73ADAC03CC; Sat, 31 Jan 2015 21:20:12 +0000 (UTC)
MIME-Version: 1.0
Date: Sat, 31 Jan 2015 16:20:12 -0500
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <CAD2Ti28_ZejQcQ1cCU2E9XVyVGLWnvaVO-+Y8y=M5m0+LBmAvA@mail.gmail.com>
References: <54C96033.2060707@emails.veryspeedy.net>
 <CAD2Ti28_ZejQcQ1cCU2E9XVyVGLWnvaVO-+Y8y=M5m0+LBmAvA@mail.gmail.com> 
Message-Id: <20150131212012.73ADAC03CC@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] Running TBB with a remote tor process
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>

"grarpamp" wrote:
>>Lara wrote:
>>I have a OpenWRT router. And I can install tor on that. I would like
to
>>have a middle relay. Can I hook up my TBB (computer linked over
wifi) to
>>that tor session? Is it a bad idea? It would be on the same
subnetwork.

>TBB likely deploys and expects a specific torrc, and likely
>makes use of the tor controller. So long as you evaluate
>those parameters for the tor on the wrt when repointing tbb,
>things should be fine. TBB also starts up tor locally, etc. So
>you may have to hack at things to use just the enhanced
>FF component of TBB.

... and access  to the control port and socks port occurs in the
clear. You'll want to  secure them or you'll need to trust anyone else
on the same subnet  doesn't snoop. You could introduce another layer
of encryption using SSH  to provide security. As far as using the
process for browsing--do you trust the other systems on the subnet not
to  snoop on encrypted traffic. This will influence the cipher
strength used--and did that extra layer of encryption gain you
anything besides  installation complexity? 

Regarding using the tor relay as a client you might find the following
to be interesting reads.

http://freehaven.net/anonbib/cache/clog-the-queue.pdf
http://freehaven.net/anonbib/cache/torta05.pdf
http://freehaven.net/anonbib/cache/back01.pdf

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

