[tor-bugs] #12631 [Tor Browser]: Tor Browser for ARM architecture

[Tor Bug Tracker & Wiki]

#12631: Tor Browser for ARM architecture
-----------------------------+------------------------
     Reporter:  mttp         |      Owner:
         Type:  project      |     Status:  new
     Priority:  normal       |  Milestone:
    Component:  Tor Browser  |    Version:
   Resolution:               |   Keywords:  tbb-gitian
Actual Points:               |  Parent ID:
       Points:               |
-----------------------------+------------------------

Comment (by mirimir):

 I've built Firefox in Tor Browser 4.5a4 on a Raspberry Pi 2, running
 Raspbian wheezy on a 32GB class 10 microSDHC card. It took 6-7 hours at
 100% CPU, and I had to cool the Pi 2 with a small fan to prevent
 overheating. I followed the instructions in
 <https://trac.torproject.org/projects/tor/wiki/doc/TorBrowser/Hacking> at
 "Building Just Firefox" exactly, except that I commented out
 "ac_add_options --enable-tor-browser-update" in "~/tor-browser/.mozconfig"
 after configuring.

 As instructed, I overwrote the Firefox folder in tor-browser_en-US (from
 tor-browser-linux32-4.5a4_en-US.tar.xz) with the Firefox folder from the
 build. Had I been using just the one Pi, that would have been sufficient.
 However, given that I'm using this workspace Pi with a Tor gateway Pi, a
 little tweaking was required.

 To avoid the possibility of Tor over Tor, I deleted the Tor folder in Tor
 Browser. In order to have Tor Browser run without a local tor process, I
 added two lines to "prefs.js" in the profiles:

 | user_pref("extensions.torlauncher.prompt_at_startup", false);
 | user_pref("extensions.torlauncher.start_tor", false);

 Once Tor Browser would run, I changed SocksPort to "192.168.2.1:9150", and
 disabled the TorLauncher extension. All of the expected extensions are
 present. On the gateway Pi, I used this "/etc/tor/torrc":

 | SocksPort 127.0.0.1:9050
 | SocksPort 192.168.2.1:9050
 | SocksPort 192.168.2.1:9100
 | SocksPort 192.168.2.1:9150
 |
 | SocksPolicy accept 127.0.0.1
 | SocksPolicy accept 192.168.2.0/16
 | SocksPolicy reject *
 |
 | DnsPort 127.0.0.1:53 IsolateDestPort
 | DnsPort 192.168.2.1:53 IsolateDestPort
 |
 | VirtualAddrNetwork 10.192.0.0/10
 | AutomapHostsOnResolve 1
 |
 | ControlPort 9151
 | CookieAuthentication 1
 |
 | Log notice file /var/log/tor/notices.log
 | RunAsDaemon 1
 | DataDirectory /var/lib/tor

 I don't believe that the iptables rules on the gateway Pi are relevant
 here, but I'll be happy to add them if desired. I installed torsocks and
 rinetd on the workspace Pi, and used this "/etc/rinetd.conf":

 | bindaddress    bindport  connectaddress  connectport
 | 127.0.0.1      9050      192.168.2.1     9050
 | 127.0.0.1      9151      192.168.2.1     9151

 Browsing <https://check.torproject.org>, I get that that the browser is
 using Tor, and there's no warning that it's not Tor Browser. After hitting
 "New Tor Circuit for this Site" in Torbutton, the page reloads with a new
 IP address. However, Torbutton still complains that Tor isn't running, and
 I don't know how to fix that.

 I also plan to test a deterministic build from
 <https://git.torproject.org/builders/tor-browser-bundle.git>. But I
 presume that would depend on having some version of Ubuntu with Gitian
 running on Raspberry Pi. I know of two possibilities so far: Ubuntu 14.04
 LTS <https://wiki.ubuntu.com/ARM/RaspberryPi> and Ubuntu 14.10 / Linaro
 15.01 <http://www.raspberrypi.org/forums/viewtopic.php?f=56&t=98997>. I
 gather that they differ in how they're compiled for ARMv7 and ARMHF.

--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/12631#comment:4>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online