Skip to content
Snippets Groups Projects
  1. Nov 02, 2017
  2. Oct 23, 2017
  3. Oct 18, 2017
  4. Oct 17, 2017
  5. Oct 04, 2017
    • 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. Oct 03, 2017
  7. Oct 02, 2017
  8. Sep 29, 2017
    • 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
      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.
      ee2f0609
  9. Sep 28, 2017
  10. Sep 26, 2017
  11. Sep 22, 2017
  12. Sep 21, 2017
  13. Sep 19, 2017
    • 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
      runc.
      
      We don't support versions older than 0.1.1.
  14. Sep 15, 2017
Loading