1. 12 Jan, 2021 1 commit
    • David Goulet's avatar
      hs-v3: Require reasonably live consensus · 04b02639
      David Goulet authored
      
      
      Some days before this commit, the network experienced a DDoS on the directory
      authorities that prevented them to generate a consensus for more than 5 hours
      straight.
      
      That in turn entirely disabled onion service v3, client and service side, due
      to the subsystem requiring a live consensus to function properly.
      
      We know require a reasonably live consensus which means that the HSv3
      subsystem will to its job for using the best consensus tor can find. If the
      entire network is using an old consensus, than this should be alright.
      
      If the service happens to use a live consensus while a client is not, it
      should still work because the client will use the current SRV it sees which
      might be the previous SRV for the service for which it still publish
      descriptors for.
      
      If the service is using an old one and somehow can't get a new one while
      clients are on a new one, then reachability issues might arise. However, this
      is a situation we already have at the moment since the service will simply not
      work if it doesn't have a live consensus while a client has one.
      
      Fixes #40237
      
      Signed-off-by: David Goulet's avatarDavid Goulet <dgoulet@torproject.org>
      04b02639
  2. 11 Jan, 2021 2 commits
  3. 17 Nov, 2020 1 commit
  4. 12 Nov, 2020 1 commit
  5. 09 Nov, 2020 2 commits
  6. 05 Nov, 2020 1 commit
  7. 14 Oct, 2020 1 commit
    • Nick Mathewson's avatar
      Implement proposal 318: Limit protovers to 0..63 · dd63b972
      Nick Mathewson authored
      In brief: we go through a lot of gymnastics to handle huge protover
      numbers, but after years of development we're not even close to 10
      for any of our current versions.  We also have a convenient
      workaround available in case we ever run out of protocols: if (for
      example) we someday need Link=64, we can just add Link2=0 or
      something.
      
      This patch is a minimal patch to change tor's behavior; it doesn't
      take advantage of the new restrictions.
      
      Implements #40133 and proposal 318.
      dd63b972
  8. 07 Oct, 2020 10 commits
  9. 22 Sep, 2020 1 commit
  10. 21 Sep, 2020 5 commits
  11. 18 Sep, 2020 3 commits
  12. 17 Sep, 2020 2 commits
  13. 01 Sep, 2020 1 commit
    • David Goulet's avatar
      conn: Remove assert on new listener connection when retrying · ea339227
      David Goulet authored
      
      
      Opening a new listener connection can fail in many ways like a bind()
      permission denied on a low port for instance.
      
      And thus, we should expect to handle an error when creating a new one instead
      of assert() on it.
      
      To hit the removed assert:
      
        ORPort 80
        KeepBindCapabilities 0
      
      Start tor. Then edit torrc:
      
        ORPort <some-IP>:80
      
      HUP tor and the assert is hit.
      
      Fixes #40073
      
      Signed-off-by: David Goulet's avatarDavid Goulet <dgoulet@torproject.org>
      ea339227
  14. 13 Aug, 2020 3 commits
  15. 12 Aug, 2020 5 commits
  16. 11 Aug, 2020 1 commit