summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
...
* Fold in 7.0.6 changelog and update release dateGeorg Koppen2017-10-03
|
* Bug 23384: install and configure unattended-upgrades on ↵Nicolas Vigier2017-10-02
| | | | build-sunet-a.torproject.net
* Bug 23384: install dma (lightweight mail transport agent) on ↵Nicolas Vigier2017-10-02
| | | | build-sunet-a.torproject.net
* Bump sandboxed-tor-browser versionGeorg Koppen2017-09-29
| | | | | This is mainly for shipping a new version right after release as our alpha release broke 0.0.13 (see: #23692).
* Bug 22501: Requests via javascript: violate FPIRichard Pospesel2017-09-29
| | | | | | | | | | | | | By default NoScript attempts to find URLs in "javascript:.*" strings found in <a> element href atributes and in <option> element value attributes. When such links (or options) are clicked/selected, NoScript attempts to navigate the page to said URL. These navigations are treated as intternal requests, and get pacced onto the catch-all circuit. This behaviour can be turned off by disabling the 'noscript.fixLinks' flag, so we do so for each Tor Browser build target's extension-overrides.js.
* Bug 23680: document the types of builds (testbuild/nightly/alpha) in ↵Nicolas Vigier2017-09-28
| | | | README.HACKING
* Bug 23630: Clarify README.HACKING on using a firefox git repositoryNicolas Vigier2017-09-26
|
* Preparing a -build5Georg Koppen2017-09-26
|
* Bug 23654: fix ja dmg file nameNicolas Vigier2017-09-26
|
* Bug 23384: install libyaml-perl on build-sunet-a.torproject.netNicolas Vigier2017-09-22
|
* Bump build versionGeorg Koppen2017-09-22
|
* Bug 22692: Don't use mremap in selfrando codeGeorg Koppen2017-09-22
|
* Revert "Pick up new selfrando tag (needed for bug 22692)"Georg Koppen2017-09-22
| | | | This reverts commit b6b18835b675dc1cae04faf474474d6a2ec65677.
* Bug 23384: fix syntax to work with ansible 2.2Nicolas Vigier2017-09-22
| | | | https://docs.ansible.com/ansible/latest/porting_guide_2.0.html#deprecated
* Bug 23384: install dependencies for update_responses on ↵Nicolas Vigier2017-09-22
| | | | build-sunet-a.torproject.net
* Picking up new tor-browser tagGeorg Koppen2017-09-22
|
* There is no -2 tor-browser branch right nowGeorg Koppen2017-09-22
|
* Pick up new selfrando tag (needed for bug 22692)Georg Koppen2017-09-22
|
* Release preparations for 7.5a5Georg Koppen2017-09-22
| | | | Versions bump and Changelog update
* Updating the torbutton keyGeorg Koppen2017-09-22
|
* Bug 16010: Enabling the sandbox on WindowsGeorg Koppen2017-09-21
|
* Bug 23384: Fix ssh key for mcsNicolas Vigier2017-09-21
|
* Fix typos in ChangelogGeorg Koppen2017-09-21
|
* Fold in missing Changelog for 7.0.4Georg Koppen2017-09-21
|
* Bug 23384: Add user mcs on build-sunet-a.torproject.netNicolas Vigier2017-09-21
|
* Bug 23396: Updating the msvcr100.dll we shipGeorg Koppen2017-09-21
| | | | | We update the location to get the .dll as well taking Mike out of the browser loop.
* Updating rbm due to bug 23557Georg Koppen2017-09-21
|
* Bug 23039: fix detection of runc versionNicolas Vigier2017-09-19
| | | | | | | | | | | In the previous patch, we wrongly assumed that all runc 0.1.1 versions exited with 0 when given an unknown command, and used that to detect the version. It seems it is not true on all systems. We are now using the 'runc --version' command to find the version of runc. We don't support versions older than 0.1.1.
* Bug 23039: add support for runc 1.0.0Nicolas Vigier2017-09-15
| | | | | | | | | | | | | | | | | | | | | | The var_p/runc100 option is used to detect the version of runc we are using. The format of the output of `runc --version` is different in both versions, so it is not easy to parse. However I noticed that runc 0.1.1 does not exit with an error when we try to use a command that does not exist while runc >= 1.0.0 does, so we use that to detect the runc version we are using. When using runc >= 1.0.0, we use `runc run` instead of `runc start': https://github.com/opencontainers/runc/commit/c669b8d1568633c68bd915561ceb2e5ecc1bfc6a In the runc config.json file, the format of the capabilities has been changed. Instead of having one list of capabilities, there are now separate lists for bounding, effective, inheritable, permitted and ambient capabilities (and we use the same list for all of them): https://github.com/opencontainers/runtime-spec/commit/eb114f057094dd2314682d55f8cb9c189915ac86 We also add /proc/timer_list and /sys/firmware to the "maskedPaths", as those paths are now listed by default in the config.json file generated by `runc spec` with runc 1.0.0.
* Bumping rbm commit for bug 23513Georg Koppen2017-09-15
|
* Bug 23454: restore stderr in build logsNicolas Vigier2017-09-11
| | | | | | | | | | In #23425 we redirected the output from runc start to /dev/null to avoid annoying messages saying "stdin: is not a tty". However this also removes stderr from build logs. The command producing the `stdin: is not a tty` message is the `chown -R` command from runc/remote_put, so we now only hide stderr from that part while keeping it for the runc command running the build script.
* Add tmp to .gitignoreNicolas Vigier2017-09-08
| | | | | With #23403 we started using the tor-browser-build/tmp directory for the builds.
* Bug 23425: fix build when there is no terminalNicolas Vigier2017-09-07
| | | | | | | | | | | | | Set process.terminal to false when building, but keep it to true when we open a debugging shell. https://github.com/opencontainers/runtime-spec/blob/master/config.md#process To do that we update the runc config.json in runc/remote_exec rather than only once in runc/remote_start. We also redirect runc stderr to /dev/null to avoid some messages saying "stdin: is not a tty" during the build.
* Bug 23403: Use tor-browser-build/tmp rather than /tmp as default tmp_dirNicolas Vigier2017-09-07
|
* README.HACKING: explain how to test an rbm patchNicolas Vigier2017-09-07
|
* Picking up new rbm commitGeorg Koppen2017-09-07
|
* Bug 23417: set nightly version number to 'tbb-nightly'Nicolas Vigier2017-09-06
|
* NoScript version bumpGeorg Koppen2017-09-06
|
* Bug 23408: Don't include 'ALL' in nightly filenamesGeorg Koppen2017-09-05
| | | | | | In test builds only the en-US locale is provided, this 'ALL' in the filename is confusing. And the nightlies are not being built multi- lingual for a while now in tor-browser-bundle
* Fold in stable changelogGeorg Koppen2017-09-05
|
* Bug 23384: install tor, torsocks, screen on build-sunet-a.torproject.netNicolas Vigier2017-09-04
|
* Bug 23384: Add user gk on build-sunet-a.torproject.netNicolas Vigier2017-09-04
|
* Bug 23384: Add user boklm on build-sunet-a.torproject.netNicolas Vigier2017-09-04
|
* Bug 23384: install packages needed for building Tor Browser on ↵Nicolas Vigier2017-09-04
| | | | build-sunet-a.torproject.net
* README: mention that rbm is included as a git submoduleNicolas Vigier2017-08-30
|
* Typo fixes in READMEGeorg Koppen2017-08-29
|
* Bug 23258: Fix broken HTTPS-Everywhere on higher security levelsGeorg Koppen2017-08-29
| | | | | | | | | | | | Shipping HTTPS-Everywhere based on the new WebExtensions model broke its functionality on higher security levels as our JavaScript blocking does not whitelist `moz-extension:` which is needed. It turns out that vanilla Firefox 52 ESR is affected as well but differently: Backorting https://bugzilla.mozilla.org/show_bug.cgi?id=1329731 does not help us as NoScript is regulating JavaScript related things. This fixes #21270 as well.
* Add Felix's obfs4 bridges to the built-in bridges.Isis Lovecruft2017-08-29
| | | | * FIXES #23166: https://bugs.torproject.org/23166
* Fix some typos in README.HACKINGGeorg Koppen2017-08-28
|
* Fix typo in README.MAKEFILEGeorg Koppen2017-08-28
|
generated by cgit v1.2.1 (git 2.18.0) at 2024-02-08 07:19:10 +0000