Difference between revisions of "Porting/Tor Browser"

From RCS Wiki
Jump to navigation Jump to search
(→‎Morph Firefox ESR into Pseudo Tor Browser: Fix #include usage for ESR102)
(→‎Morph Firefox ESR into Pseudo Tor Browser: Tor Browser Team has replaced Gitolite with GitLab)
 
(2 intermediate revisions by the same user not shown)
Line 13: Line 13:
  
 
# Install Firefox ESR and Tor.
 
# Install Firefox ESR and Tor.
−
# <code>curl --output 000-tor-browser-0.js http://gzgme7ov25seqjbphab4fkcph3jkobfwwpivt5kzbv3kqx2y2qttl4yd.onion/tor-browser.git/plain/browser/app/profile/000-tor-browser.js?h=tor-browser-102.5.0esr-12.0-1-build4</code> (substitute the tag for whatever Tor Browser release you want to use)
+
# <code>curl --output 000-tor-browser-0.js http://eweiibe6tdjsdprb4px6rqrzzcsi22m4koia44kc5pcjr7nec2rlxyad.onion/tpo/applications/tor-browser/-/raw/tor-browser-102.5.0esr-12.0-2-build1/browser/app/profile/000-tor-browser.js</code> (substitute the tag for whatever Tor Browser release you want to use)
 +
# <code>curl --output 001-base-profile.js http://eweiibe6tdjsdprb4px6rqrzzcsi22m4koia44kc5pcjr7nec2rlxyad.onion/tpo/applications/tor-browser/-/raw/tor-browser-102.5.0esr-12.0-2-build1/browser/app/profile/001-base-profile.js</code> (use the same tag as the above line)
 
# <code>grep -v "^# " 000-tor-browser-0.js | grep -v "^#expand" > 000-tor-browser-1.js</code>
 
# <code>grep -v "^# " 000-tor-browser-0.js | grep -v "^#expand" > 000-tor-browser-1.js</code>
 
# <code>sed -r 's/#include (.*\.js)$/#include "\1"/' 000-tor-browser-1.js > 000-tor-browser-2.js</code>
 
# <code>sed -r 's/#include (.*\.js)$/#include "\1"/' 000-tor-browser-1.js > 000-tor-browser-2.js</code>
Line 21: Line 22:
 
# <code>rm 000-tor-browser-*.js</code>
 
# <code>rm 000-tor-browser-*.js</code>
 
# <code>sudo mv 000-tor-browser.js /usr/share/firefox-esr/browser/defaults/preferences/</code>
 
# <code>sudo mv 000-tor-browser.js /usr/share/firefox-esr/browser/defaults/preferences/</code>
−
# Launch Firefox; install HTTPS Everywhere from the Mozilla Addons repo.
 
  
 
The above trick works because most of Tor Browser's patches are upstreamed to Firefox, and are just hidden behind prefs.  Setting Tor Browser's prefs in a standard Firefox ESR instance yields a setup that resembles Tor Browser.
 
The above trick works because most of Tor Browser's patches are upstreamed to Firefox, and are just hidden behind prefs.  Setting Tor Browser's prefs in a standard Firefox ESR instance yields a setup that resembles Tor Browser.

Latest revision as of 17:48, 7 December 2022

The POWER port of Tor Browser is mostly complete and is currently awaiting upstream review. The primary challenge of this port was that Tor Browser uses an unusual build system (rbm) in order to ensure reproducible builds. While Tor's configuration of rbm can cross-compile for Windows and macOS targets, it is not configured out of the box to cross-compile for GNU/Linux targets. As a result, the porting efforts focused on modifying Tor's rbm configuration to support cross-compiling for non-x86 GNU/Linux targets. This also yielded a working port for ARM, which is also awaiting upstream review.

Current source code is at:

If you're interested in joining the effort, talk to JeremyRand.

Morph Firefox ESR into Pseudo Tor Browser

Users who need Tor Browser on POWER, can't build from source, and can't wait for official binaries from The Tor Project can use the following workaround to morph Firefox ESR into something that resembles Tor Browser (tested on Debian Buster and Debian Bullseye):

  1. Install Firefox ESR and Tor.
  2. curl --output 000-tor-browser-0.js http://eweiibe6tdjsdprb4px6rqrzzcsi22m4koia44kc5pcjr7nec2rlxyad.onion/tpo/applications/tor-browser/-/raw/tor-browser-102.5.0esr-12.0-2-build1/browser/app/profile/000-tor-browser.js (substitute the tag for whatever Tor Browser release you want to use)
  3. curl --output 001-base-profile.js http://eweiibe6tdjsdprb4px6rqrzzcsi22m4koia44kc5pcjr7nec2rlxyad.onion/tpo/applications/tor-browser/-/raw/tor-browser-102.5.0esr-12.0-2-build1/browser/app/profile/001-base-profile.js (use the same tag as the above line)
  4. grep -v "^# " 000-tor-browser-0.js | grep -v "^#expand" > 000-tor-browser-1.js
  5. sed -r 's/#include (.*\.js)$/#include "\1"/' 000-tor-browser-1.js > 000-tor-browser-2.js
  6. cpp -E -D XP_LINUX=1 -D MOZ_BUNDLED_FONTS=1 -o 000-tor-browser-3.js 000-tor-browser-2.js
  7. grep -v "^# " 000-tor-browser-3.js > 000-tor-browser-4.js
  8. sed "s/9150)/9050)/" 000-tor-browser-4.js > 000-tor-browser.js
  9. rm 000-tor-browser-*.js
  10. sudo mv 000-tor-browser.js /usr/share/firefox-esr/browser/defaults/preferences/

The above trick works because most of Tor Browser's patches are upstreamed to Firefox, and are just hidden behind prefs. Setting Tor Browser's prefs in a standard Firefox ESR instance yields a setup that resembles Tor Browser.

How secure is this?

It's not ideal. Among other things, you don't get the protection of TorButton (such as first-party stream isolation). That said, your browser fingerprint will probably be very similar to real Tor Browser. I've found empirically that even Cloudflare's fingerprinting code thinks I'm using real Tor Browser. It's not going to be as good as real Tor Browser, but it's probably the best thing you can get on POWER if you're not able to build real Tor Browser from source.

Build instructions

Use one of these (depending on which platform you're building for): 

make nightly-linux-arm

make nightly-linux-ppc64le

Errors / Troubleshooting

Unfixed

Fixed

syscall not declared

/var/tmp/build/firefox-f8f42fea2af3/js/src/jsnativestack.cpp:69:31: error: 'syscall' was not declared in this scope

  • This is because jsnativestack.cpp forgot to #include <unistd.h>.
  • This is fixed in all releases of Tor Browser based on ESR 60.
  • For ESR 52, I fixed it by applying a short patch to add the missing include.

getpid not declared

/var/tmp/build/firefox-f8f42fea2af3/js/src/jsnativestack.cpp:77:27: error: 'getpid' was not declared in this scope

  • Also caused by missing #include <unistd.h> in jsnativestack.cpp
  • Same fixes as above.

Missing libssp.so.0 (file is actually gone)

./firefox: error while loading shared libraries: libssp.so.0: cannot open shared object file: No such file or directory

  • Workaround: copy libssp.so* from the gcc-cross output tar into the Browser directory of the firefox output.
  • Fixed in the Firefox rbm build script as of 2018 Oct 10.

Segfault

Segfault immediately on startup in libxul.so

Missing libssp.so.0 (file is present but Tor Browser doesn't see it)

./firefox: error while loading shared libraries: libssp.so.0: cannot open shared object file: No such file or directory

  • Workaround: add the Browser directory to your LD_LIBRARY_PATH in order for Tor Browser to find the library.
  • Fixed by editing the startup shell script.

SSE2 not detected

  • Workaround: just manually comment out the SSE2 check in the shell script.
  • Fixed by editing the startup shell script.

Missing Pluggable Transports

The fteproxy and snowflake pluggable transports are disabled for non-x86 GNU/Linux targets. These pluggable transports are already non-mandatory for building Tor Browser, and getting them to build for cross-compiled GNU/Linux targets was deemed to be too much of a time sink.

Task list

  • (DONE!) Finish porting this to Firefox ESR 60.
  • (DONE!) Build openssl without errors.
  • (DONE!) Build libevent without errors.
  • (DONE!) Build tor without errors.
  • (DONE!) Build firefox-langpacks without errors.
  • (DONE!) Build tor-launcher without errors.
  • (DONE!) Build torbutton without errors.
  • (DONE!) Build python without errors.
  • (DONE!) Build https-everywhere without errors.
  • (DONE!) Build fonts without errors.
  • (DONE!) Build meek without errors.
  • (DONE!) Build obfs4 without errors.
  • (DONE!) Build tor-browser without errors.
  • (DONE!) Build release without errors.
  • (DONE!) Add linux-arm targets to Makefile.
  • (DONE!) Test the openssl, libevent, tor, firefox-langpacks, tor-launcher, torbutton, python, https-everywhere, fonts, meek, obfs4, tor-browser, and release binaries.
  • (DONE!) Re-enable the fteproxy and snowflake projects (low priority).
  • (DONE!) Generalize the GNU/Linux cross-compiling changes so that they work on target arches besides armhf. (ppc64be, ppc64le, and aarch64 are all likely to be useful.)
  • Fine-tune the compiler settings. (Are we inadvertently excluding some ARM devices that we want to support? Should we enable Neon?)

Upstream Tickets

Retrieved from "https://wiki.raptorcs.com/w/index.php?title=Porting/Tor_Browser&oldid=4070"