Delivery-Date: Mon, 13 Jul 2015 05:12:22 -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.1 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,T_DKIM_INVALID,T_RP_MATCHES_RCVD,UNPARSEABLE_RELAY
	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 B754B1E04F8;
	Mon, 13 Jul 2015 05:12:20 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 6214C375BE;
	Mon, 13 Jul 2015 09:12:16 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id 3AC91375E3
 for <tor-talk@lists.torproject.org>; Mon, 13 Jul 2015 09:12:13 +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 wHnWQUltWEqS for <tor-talk@lists.torproject.org>;
 Mon, 13 Jul 2015 09:12:13 +0000 (UTC)
Received: from mx1.riseup.net (mx1.riseup.net [198.252.153.129])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (not verified))
 by eugeni.torproject.org (Postfix) with ESMTPS id 155373740B
 for <tor-talk@lists.torproject.org>; Mon, 13 Jul 2015 09:12:13 +0000 (UTC)
Received: from plantcutter.riseup.net (plantcutter-pn.riseup.net [10.0.1.121])
 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits))
 (Client CN "*.riseup.net",
 Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK))
 by mx1.riseup.net (Postfix) with ESMTPS id 1F21640E74
 for <tor-talk@lists.torproject.org>; Mon, 13 Jul 2015 09:12:10 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=riseup.net; s=squak;
 t=1436778730; bh=gdBtoTW2/30ruz3jFodMUqYBCHJon6opdOOyQppcL1g=;
 h=Date:From:To:Subject:References:In-Reply-To:From;
 b=JoNxZWAhAy8EZf1DABpQx5xtEe9yBlNq228e69UABlPDMucsXMJWyIVj4DDB/eC7k
 cvUeYq9p/NEqDqDkB/zgUk84mAebanAjP3KnQv6u6f+/yEPY+oVh2+4JmFHqbIMhMF
 p4bgxWPS1jMZ7Zj1/R/9OYOwJSMH0GrOHYEeisCI=
Received: from [127.0.0.1] (localhost [127.0.0.1])
 (Authenticated sender: mirimir) with ESMTPSA id 3AAE41FDFC
Message-ID: <55A380EE.4040608@riseup.net>
Date: Mon, 13 Jul 2015 03:12:14 -0600
From: Mirimir <mirimir@riseup.net>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:31.0) Gecko/20100101 Thunderbird/31.7.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <20150713075138.GA1792@alarmpi> <55A3728D.80103@riseup.net>
 <20150713082915.GB1792@alarmpi>
In-Reply-To: <20150713082915.GB1792@alarmpi>
X-Virus-Scanned: clamav-milter 0.98.7 at mx1
X-Virus-Status: Clean
Subject: Re: [tor-talk] Tor browser for ARM architecture
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>

On 07/13/2015 02:29 AM, Pickfire wrote:
> 
> On Mon, Jul 13, 2015 at 02:10:53AM -0600, Mirimir wrote:
>> On 07/13/2015 01:51 AM, Pickfire wrote:
>>> Hi, is there a tor browser for ARM architecture?
>> I've built it in Raspbian on Raspberry Pi2.
> 
> I hope you can show me the link. I am using Pi2 too.

Update the following for the latest Tor browser release.

See https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking
and
https://gitweb.torproject.org/builders/tor-browser-bundle.git/tree/gitian/descriptors/linux/gitian-firefox.yml#l8

$ sudo apt-get install --no-install-suggests --no-install-recommends
libasound2-dev libcurl4-openssl-dev libglib2.0-dev libgtk2.0-dev
libdbus-1-dev libdbus-glib-1-dev libgstreamer-plugins-base0.10-dev
libxt-dev libtool autoconf autoconf2.13 g++ libpulse-dev git yasm
zip unzip mesa-common-dev hardening-wrapper pkg-config
$ git clone https://git.torproject.org/tor-browser.git
$ cd tor-browser
$ git branch -a
$ git checkout remotes/origin/tor-browser-31.5.0esr-4.5-1
$ make $CONFIGURE_ARGS -f client.mk configure
CONFIGURE_ARGS="--with-tor-browser-version=4.5a4
--enable-update-channel=alpha"
$ nano /home/pi/tor-browser/.mozconfig
   ...
   #ac_add_options --enable-tor-browser-update
   ...
$ make $MAKEOPTS -f client.mk build        <= takes several hours
$ make -C obj-* package INNER_MAKE_PACKAGE=true

get tor-browser-linux32-4.5a4_en-US.tar.xz
move to ~/

$ tar -xvfJ tor-browser-linux32-4.5a4_en-US.tar.xz
$ nano
~/tor-browser_en-US/Browser/TorBrowser/Data/Browser/profile.default/prefs.js
   .............................................................
   ...
   user_pref("extensions.torlauncher.prompt_at_startup", false);
   user_pref("extensions.torlauncher.start_tor", false);
   ...
   .............................................................
$ cp -a ~/tor-browser/obj-armv7l-unknown-linux-gnueabihf/dist/firefox/*
~/tor-browser_en-US/Browser/

start browser and change SocksPort to 192.168.2.1:9150

>> But I was doing a Whonix-like setup, with a Tor-gateway Pi2 and a
>> workspace Pi2, so I only built the browser component.
> 
> What do you mean by that?

I used two Pi2. The gateway Pi2 runs only Tor, and had a second USB NIC.
The workspace Pi2 runs Tor browser etc. Both have iptables rules to
allow only necessary traffic, and to prevent leaks. Even if the
workspace Pi2 gets pwned, it can't reach the Internet except through the
Tor gateway Pi2.
-- 
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

