Delivery-Date: Sun, 03 Aug 2014 09:53:02 -0400
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=-3.5 required=5.0 tests=BAYES_00,
	RCVD_IN_BL_SPAMCOP_NET,RCVD_IN_DNSWL_MED,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 F18CC1E030C;
	Sun,  3 Aug 2014 09:53:00 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 4A27E30CB8;
	Sun,  3 Aug 2014 13:52:56 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 2CF6130BFB
 for <tor-talk@lists.torproject.org>; Sun,  3 Aug 2014 13:52:53 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
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 y70UZQvjy2vb for <tor-talk@lists.torproject.org>;
 Sun,  3 Aug 2014 13:52:53 +0000 (UTC)
X-Greylist: delayed 592 seconds by postgrey-1.34 at eugeni;
 Sun, 03 Aug 2014 13:52:52 UTC
Received: from whonix.org (whonix.org [92.243.7.197])
 by eugeni.torproject.org (Postfix) with ESMTP id F143630808
 for <tor-talk@lists.torproject.org>; Sun,  3 Aug 2014 13:52:52 +0000 (UTC)
Received: from 127.0.0.1 (tor-exit-node.dnslab.nl [95.211.229.158])
 by whonix.org (Postfix) with ESMTPSA id 54EA113F7
 for <tor-talk@lists.torproject.org>; Sun,  3 Aug 2014 15:42:56 +0200 (CEST)
Message-ID: <53DE3C5D.8020200@whonix.org>
Date: Sun, 03 Aug 2014 13:42:53 +0000
From: Patrick Schleizer <patrick-mailinglists@whonix.org>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <53D727D8.7010902@riseup.net>
In-Reply-To: <53D727D8.7010902@riseup.net>
Subject: Re: [tor-talk] using locally installed Tor in TBB
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>

shmick@riseup.net:
> in 3.6.3 TBB linux amd-64 i changed the port to 9050
> 
> my local install of Tor is on the jessie alpha channel
> 
> when i close & restart TBB i get:
> 
> Something Went Wrong!
> Tor is not working in this browser.

This happens because of missing Tor ControlPort access.

There are no instructions for how to use TBB with system Tor. But it is
possible...

Maybe you can add this to torproject.org's wiki?

Environment variable:

## Deactivate tor-launcher,
## a Vidalia replacement as browser extension,
## to prevent running Tor over Tor.
## https://trac.torproject.org/projects/tor/ticket/6009
## https://gitweb.torproject.org/tor-launcher.git
export TOR_SKIP_LAUNCH=1

## The following TOR_SOCKS_HOST and TOR_SOCKS_PORT variables
## do not work flawlessly, due to an upstream bug in Tor Button:
## "TOR_SOCKS_HOST, TOR_SOCKS_PORT regression"
## https://trac.torproject.org/projects/tor/ticket/8336
#export TOR_SOCKS_HOST="127.0.0.1"
#export TOR_SOCKS_PORT="9050"

What should work quite well is using env var "export TOR_SKIP_LAUNCH=1"
combined with rinetd, redirecting traffic from TBB's ports 9150 and 9151
to 127.0.0.1 with a config like this:

127.0.0.1 9150 127.0.0.1 9050
127.0.0.1 9151 127.0.0.1 9051

You also need some form of ControlPort authentication.

export TOR_CONTROL_PASSWD="password"

tor --hash-password password

See Tor manual HashedControlPassword.
https://www.torproject.org/docs/tor-manual.html.en

Add the

HashedControlPassword hashedpassword
to /etc/tor/torrc and reload (/restart?) Tor.

> this is repeatable behaviour opening/closing TBB
> 
> some Tor log looks ok though and apart from logs it obviously does work
> on 9050
> 
> [NOTICE] Bootstrapped 85%: Finishing handshake with first hop.
> [NOTICE] Bootstrapped 90%: Establishing a Tor circuit.
> [NOTICE] Tor has successfully opened a circuit. Looks like client
> functionality is working.
> [NOTICE] Bootstrapped 100%: Done.
> [NOTICE] New control connection opened.
> 
> as an aside would it be discouraged to use the alpha in TBB and not the
> bundled Tor version 0.2.4.22 (git-345e00dc68a052fe) ?
> 
> pros/cons either way ?

Pros:
- easier to keep your entry guards longer

Cons:
- more difficult to set up

Cheers,
Patrick

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

