Delivery-Date: Sat, 12 Jul 2014 10:41:42 -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=-4.9 required=5.0 tests=BAYES_00,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 690DD1E092C
	for <archiver@seul.org>; Sat, 12 Jul 2014 10:41:40 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 2F46E3025F;
	Sat, 12 Jul 2014 14:41:39 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id AB1AF3047A
 for <tor-talk@lists.torproject.org>; Sat, 12 Jul 2014 14:38: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 cfvNjZ-yNXqA for <tor-talk@lists.torproject.org>;
 Sat, 12 Jul 2014 14:38:53 +0000 (UTC)
Received: from mail.bitmessage.ch (mail.bitmessage.ch [146.228.112.252])
 by eugeni.torproject.org (Postfix) with SMTP id 4374430477
 for <tor-talk@lists.torproject.org>; Sat, 12 Jul 2014 14:38:53 +0000 (UTC)
Received: from 127.0.0.1 (BITMESSAGE [127.0.0.1]) by mail.bitmessage.ch
 ; Sat, 12 Jul 2014 16:38:48 +0200
Message-ID: <53C14875.5090901@bitmessage.ch>
Date: Sat, 12 Jul 2014 14:38:45 +0000
From: Nusenu <BM-2D8wMEVgGVY76je1WXNPfo8SrpZt5yGHES@bitmessage.ch>
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <53823B2A.2010104@bitmessage.ch> <5383AB5F.3010002@riseup.net>
In-Reply-To: <5383AB5F.3010002@riseup.net>
Subject: [tor-talk] New Identity Warning without Control Port Access (was:
 Re: OK to disable TorLauncher addon in TBB in Transparent Torification
 Setup?)
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>

>> I'm running Torbrowser on a system that is transparently routed
>> through Tor. Is it OK to disable the TorLauncher Addon within
>> Torbrowser in such a setup or has that any negative
>> consequences?
> 
> Using TOR_SKIP_LAUNCH is tested by more people. See: 
> https://trac.torproject.org/projects/tor/wiki/doc/TorifyHOWTO/WebBrowsers#UseTorBrowserwithoutbundledTorNIX

Thank
> 
you for this info. This seems to work fine (TOR_SKIP_LAUNCH).

Since I use it I also get a proper error message that tells me that
Torbutton cannot safely give me a new identity. It does not have
access to the Tor Control Port.

Is is it considered a bug to *not* display this warning when *not*
using TOR_SKIP_LAUNCH=1 in transparent torification mode?


>> (background: I can't execute that script multiple times
>> concurrently to open a new URL in an existing torbrowser
>> session.)
> 
> Try this: /home/user/tor-browser_en-US/Browser/firefox --profile 
> "Data/Browser/profile.default" --new-tab "torproject.org"
> 
> [Soon a tb-launcher package might get released by me for this
> purpose. Then you can type "torbrowser --new-tab link" and a new
> link will be opened in existing browser session.]

What is the current state on this?


thanks!

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

