Version bumps and Changelog update

Sukhbir Singh authored Aug 21, 2018 and Georg Koppen committed Aug 29, 2018

Since https://bugzilla.mozilla.org/show_bug.cgi?id=1463749 is fixed in
Firefox 60.2 ESR, we re-enable the verification of langpack checksums.

This new versions picks up a fix for #26548.

Add the option `mar_compression` to update_responses_config.yml to
select the compression format used in the mar files.

Currently we are using bzip2 for the previous alpha, xz for the new
alpha, and bzip2 for both the previous and new stable.

Fixed missing items in Changelog, correct sha256sum for new NoScript

Versions bump and Changelog update

boklm authored Aug 15, 2018 and Georg Koppen committed Aug 16, 2018

In a previous patch for bug 25485 we changed how we set LD_LIBRARY_PATH
in start-tor-browser. However this change is not taken into account when
the browser is restarted by the updater. To avoid this issue we replace
the firefox binary by a wrapper setting LD_LIBRARY_PATH.

boklm authored May 29, 2018 and Georg Koppen committed Aug 15, 2018

We still need the other half of the fix for actually providing higher
entropy (see bug 12968, comment:17ff. for discussion).

Fix build issue introduced by the fix for #25485.

We ship our version of libstdc++.so.6 for backward compatibility of Tor
Browser on older systems like Ubuntu 16.04. However, a newer version of
the library may be installed on the user's system and we should detect
and use that. This commit adds support for detecting the library using a
C++ program that uses the latest ABI; if the program executes, we should
use the system library, and if not (for the older systems), we add our
libstdc++.so.6 to LD_LIBRARY_PATH.

Richard Pospesel authored Aug 01, 2018 and boklm committed Aug 03, 2018

runc version on Ubuntu 18.04 is 1.0.1 which is not currently handled in
rbm.conf, so the runc_spec100 flag does not get set properly.  This
patch changes it so the runc_spec100 flag is set if a spec string
greater than 1.0.0 is found.

Ben Burrill authored Jul 26, 2018 and Georg Koppen committed Jul 31, 2018

Prior to this change, arguments with spaces were flattened, so running

    ./start-tor-browser.desktop --search "hello world"

would be converted to

    ./start-tor-browser.desktop --search hello world

opening up two windows, one search for "hello" and one trying to connect
to http://world

Fixes #18022 as well.

STIX moved away from SourceForge to GitHub breaking download during Tor
Browser build; see
https://lists.torproject.org/pipermail/tor-dev/2018-July/013357.html

Sukhbir Singh authored Jun 23, 2018 and Georg Koppen committed Jul 25, 2018

We now build with -DWIDL_EXPLICIT_AGGREGATE_RETURNS on Windows to fix
this issue; see https://bugzilla.mozilla.org/show_bug.cgi?id=1411401 for
more information.

David Fifield authored Jul 15, 2018 and Georg Koppen committed Jul 18, 2018

This works around a hang in the client that occurred once it had logged
a certain amount of information to its stderr. Now, if not logging to a
file, snowflake-client will log nothing rather than writing to stderr.
The corresponding tor bug is #26360.

We also update keyring/tbb-windows-installer.gpg as Moritz is using a
new key for signing the tag:
7A3D AD44 08A0 009B 4DE9  C855 858E E1C3 B8A4 568D

Tom Ritter authored Jul 12, 2018 and boklm committed Jul 12, 2018

Does not affect the console output, will use more disk space in log files.

Richard Pospesel authored Jun 26, 2018 and Georg Koppen committed Jun 29, 2018

Fixup for 26039.  WebExtension extensions can't read/write prefs, so the
base contents of extension-overrides.js are completely unnecessary.  The
WebExtension versions of noscript and httpseverywhere seem to be nearly
complete re-writes (noscript in particular is much simpler) so our
custom options appear to be no longer required (though a complete audit
of noscript should probably be done just to be sure we don't need to fix
any bad behaviour).

The updated build script for tor-browser now dumps all of the
build-determined prefs (pluggable transport strings, localization
options) into a generated-prefs.js file created at build time, which is
then appended to 000-tor-browser.js as before.

The pdfjs option is no longer needed since the disableRange option seems
to break pdfjs altogether in latest ESR60.  Also, setting the user pref
in 000-tor-browser.js does not work since pdfjs overwrites it with its
own value (any future patch setting pdfjs options needs to modify the
default values table)