1. 02 Nov, 2017 2 commits
  2. 23 Oct, 2017 2 commits
  3. 18 Oct, 2017 3 commits
  4. 17 Oct, 2017 1 commit
  5. 04 Oct, 2017 1 commit
    • boklm's avatar
      Bug 23585: fix build with runc version 1.0.0~rc2 · 8c4c05dd
      boklm authored
      Some distributions are packaging runc version 1.0.0~rc2, which seems to
      be half between runc 0.1.1 and runc 1.0.0.
      This version requires the same command line parameters as version 1.0.0,
      however it requires a config.json in the same format as 0.1.1.
      The output from `runc --version` on 1.0.0~rc2 is:
      runc version spec: 1.0.0-rc2-dev
      So we add a var/runc_spec100 function which is true when the runc
      version spec is exactly 1.0.0 (as returned by runc stable 1.0.x
      releases), and use it in projects/common/runc-config.json.
  6. 03 Oct, 2017 1 commit
  7. 02 Oct, 2017 2 commits
  8. 29 Sep, 2017 2 commits
    • Georg Koppen's avatar
      Bump sandboxed-tor-browser version · 71299134
      Georg Koppen authored
      This is mainly for shipping a new version right after release as our alpha
      release broke 0.0.13 (see: #23692).
    • Richard Pospesel's avatar
      Bug 22501: Requests via javascript: violate FPI · ee2f0609
      Richard Pospesel authored and Georg Koppen's avatar Georg Koppen committed
      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
      This behaviour can be turned off by disabling the 'noscript.fixLinks'
      flag, so we do so for each Tor Browser build target's
  9. 28 Sep, 2017 1 commit
  10. 26 Sep, 2017 3 commits
  11. 22 Sep, 2017 11 commits
  12. 21 Sep, 2017 7 commits
  13. 19 Sep, 2017 1 commit
    • boklm's avatar
      Bug 23039: fix detection of runc version · 1f054c59
      boklm authored
      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
      We don't support versions older than 0.1.1.
  14. 15 Sep, 2017 2 commits
  15. 11 Sep, 2017 1 commit
    • boklm's avatar
      Bug 23454: restore stderr in build logs · 75af4379
      boklm authored
      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.