1. 06 Dec, 2019 1 commit
  2. 03 Dec, 2019 1 commit
    • teor's avatar
      Travis: use -std=gnu99 in some jobs · 792c15fd
      teor authored
      Require C99 standards-conforming code in Travis CI, but allow GNU gcc
      extensions. Also activates clang's -Wtypedef-redefinition warnings.
      
      Builds some jobs with -std=gnu99, and some jobs without.
      
      Closes ticket 32500.
      792c15fd
  3. 09 Nov, 2019 1 commit
  4. 06 Nov, 2019 2 commits
  5. 28 Oct, 2019 1 commit
  6. 24 Oct, 2019 3 commits
  7. 22 Oct, 2019 3 commits
  8. 17 Oct, 2019 1 commit
  9. 02 Oct, 2019 1 commit
  10. 30 Sep, 2019 2 commits
    • teor's avatar
      Travis: Add a macOS chutney job, but don't wait for it to finish · 1e0e23c1
      teor authored
      Since Travis macOS has IPv6 support (and Travis Linux does not), chutney
      will now run its IPv6 networks as part of Travis CI.
      
      But since chutney is slow, don't wait for the macOS chutney to finish.
      (Travis have fixed the duplicate notification bug in fast_finish. So we
      can use fast_finish and allow_failure to finish early. Unfortunately,
      allow_failure also means we ignore failures in macOS chutney.)
      
      Also make sure that we have:
      * a compile on each platform, with each compiler,
      * a check on each platform, and
      * a check on each compiler.
      
      Finally, sort builds: allow fail last, macOS first, slowest first.
      
      Closes ticket 30860.
      Closes ticket 31859 for 0.2.9.
      1e0e23c1
    • teor's avatar
      Travis: Remove a redundant clang Linux job · 4e429783
      teor authored
      Part of 31859.
      4e429783
  11. 26 Sep, 2019 1 commit
  12. 23 Sep, 2019 1 commit
    • Nick Mathewson's avatar
      Try using make -k in Travis configuration · 6ed3d8db
      Nick Mathewson authored
      Frequently, when a patch fails, it has failures in several files.
      Using the "-k" flag will let us learn all the compilation errors,
      not just the first one that the compiler hits.
      
      Based on a patch by rl1987.
      6ed3d8db
  13. 18 Sep, 2019 2 commits
  14. 17 Sep, 2019 1 commit
    • Nick Mathewson's avatar
      Treat an unexpected constant-sized VERSIONS cell as a PROTOCOL_WARN. · 3c97ab3c
      Nick Mathewson authored
      We previously used tor_fragile_assert() to declare that this case
      could not happen: VERSIONS cells are always supposed to be
      variable-sized, right?
      
      This is incorrect, though.  On a v1 link protocol connection, all
      cells are fixed-sized.  There aren't supposed to be any VERSIONS
      cells with this version of the protocol, but apparently, somebody
      was messing up.  (The v1 link protocol is obsolete, so probably the
      implementer responsible didn't mean to be using it.)
      
      Fixes bug 31107.  Bugfix on 0.2.4.4-alpha, when we introduced a
      tor_fragile_assert() for this case.
      3c97ab3c
  15. 09 Sep, 2019 1 commit
  16. 15 Aug, 2019 1 commit
    • David Goulet's avatar
      dirauth: Change dizum IP address · 5a1c3e44
      David Goulet authored
      New IP address from 194.109.206.212 to 45.66.33.45.
      
      Signed request from Alex de Joode, operator of dizum:
      https://trac.torproject.org/projects/tor/ticket/31406
      
      
      
      Published descriptor by dizum on August 12th, 2019:
      
      --
      r dizum fqbq1v2DCDxTj0QDi7+gd1h911U GZmZtCLaPDQNxkhIFj8UcgTRAuA 2019-08-12 15:28:40 45.66.33.45 443 80
      s Authority Fast Running Stable V2Dir Valid
      v Tor 0.4.0.5
      pr Cons=1-2 Desc=1-2 DirCache=1-2 HSDir=1-2 HSIntro=3-4 HSRend=1-2 Link=1-5 LinkAuth=1,3 Microdesc=1-2 Relay=1-2 Padding=1
      w Bandwidth=20 Unmeasured=1
      p reject 1-65535
      --
      
      Finally, confirmed by DNS:
      
        $ dig +short tor.dizum.com
        45.66.33.45
      
      Closes #31406
      Signed-off-by: David Goulet's avatarDavid Goulet <dgoulet@torproject.org>
      5a1c3e44
  17. 09 Aug, 2019 7 commits
  18. 08 Aug, 2019 8 commits
  19. 06 Aug, 2019 1 commit
    • Nick Mathewson's avatar
      Avoid using labs() on time_t in channeltls.c · 0849d2a2
      Nick Mathewson authored
      On some windows builds, time_t is 64 bits but long is not.  This is
      causing appveyor builds to fail.
      
      Also, one of our uses of labs() on time_t was logically incorrect:
      it was telling us to accept NETINFO cells up to three minutes
      _before_ the message they were responding to, which doesn't make
      sense.
      
      This patch adds a time_abs() function that we should eventually move
      to intmath.h or something.  For now, though, it will make merges
      easier to have it file-local in channeltls.c.
      
      Fixes bug 31343; bugfix on 0.2.4.4-alpha.
      0849d2a2
  20. 19 Jul, 2019 1 commit