1. 11 Nov, 2018 1 commit
  2. 09 Nov, 2018 2 commits
  3. 31 Oct, 2018 1 commit
  4. 25 Oct, 2018 2 commits
  5. 23 Oct, 2018 1 commit
  6. 15 Oct, 2018 3 commits
  7. 10 Oct, 2018 2 commits
  8. 18 Sep, 2018 1 commit
    • teor's avatar
      Travis: use the Homebrew addon · e8c7d7d3
      teor authored
      Use the Travis Homebrew addon to install packages on macOS. The package
      list is the same, but the Homebrew addon does not do a `brew update` by
      default.
      
      This makes builds faster, at the cost of using slightly older packages.
      
      Implements ticket 27738.
      e8c7d7d3
  9. 14 Sep, 2018 2 commits
    • Nick Mathewson's avatar
      Revise our assertion and bug macros to work with -Wparentheses · bb465be0
      Nick Mathewson authored
      On GCC and Clang, there's a feature to warn you about bad
      conditionals like "if (a = b)", which should be "if (a == b)".
      However, they don't warn you if there are extra parentheses around
      "a = b".
      
      Unfortunately, the tor_assert() macro and all of its kin have been
      passing their inputs through stuff like PREDICT_UNLIKELY(expr) or
      PREDICT_UNLIKELY(!(expr)), both of which expand to stuff with more
      parentheses around "expr", thus suppressing these warnings.
      
      To fix this, this patch introduces new macros that do not wrap
      expr.  They're only used when GCC or Clang is enabled (both define
      __GNUC__), since they require GCC's "({statement expression})"
      syntax extension.  They're only used when we're building the
      unit-test variant of the object files, since they suppress the
      branch-prediction hints.
      
      I've confirmed that tor_assert(), tor_assert_nonfatal(),
      tor_assert_nonfatal_once(), BUG(), and IF_BUG_ONCE() all now give
      compiler warnings when their argument is an assignment expression.
      
      Fixes bug 27709.
      
      Bugfix on 0.0.6, where we first introduced the "tor_assert()" macro.
      bb465be0
    • cypherpunks's avatar
      protover: reject invalid protocol names · e24195c7
      cypherpunks authored
      The spec only allows the characters [A-Za-z0-9-].
      
      Fix on b2b2e1c7.
      Fixes #27316; bugfix on 0.2.9.4-alpha.
      e24195c7
  10. 13 Sep, 2018 1 commit
  11. 12 Sep, 2018 1 commit
  12. 11 Sep, 2018 2 commits
  13. 10 Sep, 2018 1 commit
  14. 07 Sep, 2018 8 commits
  15. 05 Sep, 2018 3 commits
  16. 29 Aug, 2018 2 commits
  17. 23 Aug, 2018 5 commits
  18. 22 Aug, 2018 2 commits