Delivery-Date: Tue, 03 Feb 2015 17:46:29 -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 29DE31E0DC7
	for <archiver@seul.org>; Tue,  3 Feb 2015 17:46:28 -0500 (EST)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 90DD733689;
	Tue,  3 Feb 2015 22:46:24 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 09D1A33619
 for <tor-talk@lists.torproject.org>; Tue,  3 Feb 2015 22:46:20 +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 etGezdPWIq3O for <tor-talk@lists.torproject.org>;
 Tue,  3 Feb 2015 22:46:19 +0000 (UTC)
Received: from smtp5.hushmail.com (smtp5.hushmail.com [65.39.178.142])
 (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 C5A19306AB
 for <tor-talk@lists.torproject.org>; Tue,  3 Feb 2015 22:46:19 +0000 (UTC)
Received: from smtp5.hushmail.com (localhost [127.0.0.1])
 by smtp5.hushmail.com (Postfix) with SMTP id E107260229
 for <tor-talk@lists.torproject.org>; Tue,  3 Feb 2015 22:46:16 +0000 (UTC)
Received: from smtp.hushmail.com (w6.hushmail.com [65.39.178.92])
 by smtp5.hushmail.com (Postfix) with ESMTP
 for <tor-talk@lists.torproject.org>; Tue,  3 Feb 2015 22:46:16 +0000 (UTC)
Received: by smtp.hushmail.com (Postfix, from userid 99)
 id CBEDF200D0; Tue,  3 Feb 2015 22:46:16 +0000 (UTC)
MIME-Version: 1.0
Date: Tue, 03 Feb 2015 17:46:16 -0500
To: tor-talk@lists.torproject.org
From: "l.m" <ter.one.leeboi@hush.com>
In-Reply-To: <54D00F0A.5080802@whonix.org>
References: <54C3C353.7020709@whonix.org> <54C40BC0.7020601@mykolab.com>
 <54C47651.6040100@whonix.org> <54C49889.3030004@mykolab.com>
 <54C69944.80807@whonix.org> <20150131183209.2D8C5C03CC@smtp.hushmail.com>
 <54CDA1A6.6090703@whonix.org> <20150201230016.5406CC03CC@smtp.hushmail.com>
 <54D00F0A.5080802@whonix.org> 
Message-Id: <20150203224616.CBEDF200D0@smtp.hushmail.com>
X-Content-Filtered-By: Mailman/MimeDel 2.1.15
Subject: Re: [tor-talk] How to make TBB useable as "system Tor", as Tor,
	Vidalia, pluggable transports system level replacement?
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>


"Patrick Schleizer" wrote:
>Being able to use the tor-launcher graphical user 
>interface is what this proposal is for.

You still can. Tor launcher is an extension for firefox. It's not the
same as Vidalia. You would still need to launch the tor process
separately for system use. You could use Tor Browser + tor-launcher to
configure torrc for you but that's it. You can continue to use
tor-launcher within Tor Browser. The tor-launcher extension cannot
launch a tor process then exit while keeping tor in memory for you.
Unloading the browser unloads the extension and the tor process.

On the other hand you could use Vidalia to control the system tor
process. Then make the extension changes previously mentioned to
continue using tor-launcher with TBB. You would need to be careful
with the control port password configuration. i.e. making sure it
matches between torrc and TBB launcher script. Yes, I know Vidalia
isn't supported by Tor Project anymore and it's full of bugs. You
could still use the improved new identity in TBB and be able to use
Vidalia. You wouldn't gain anything over configuration of torrc
manually and you could just as easily do with Vidalia and connect to
the control port for issuing NEWNYM.

If you're proposing tor-launcher replace Vidalia in controlling a
system tor process--it's not possible for an extension to fill that
role. 

>By asking on this list, we were hoping for advice on 
>where/how in tor-launcher's source code one could 
>best make these modifications to reach this goal. I 
>should have probably posted this on on tbb-dev 
>rather than tor-talk.

Graphical control of a system tor process isn't TBB related. tbb-dev
would be concerned with how to get Vidalia like features into a
running TBB process. To my knowledge they're already working on that.
This isn't what you're asking for though. You're just as well off
posting here to tor-talk. You might convince someone to fix the bugs
in Vidalia or to write a new Vidalia inspired gui ;)

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

