1. 22 Dec, 2017 1 commit
    • teor's avatar
      Make the default DirAuthorityFallbackRate 0.1 · 30e13716
      teor authored
      This makes clients on the public tor network prefer to bootstrap off fallback
      directory mirrors.
      
      This is a follow-up to 24679, which removed weights from the default fallbacks.
      
      Implements ticket 24681.
      30e13716
  2. 21 Dec, 2017 4 commits
  3. 20 Dec, 2017 2 commits
  4. 11 Dec, 2017 4 commits
  5. 01 Dec, 2017 5 commits
  6. 30 Nov, 2017 8 commits
  7. 29 Nov, 2017 1 commit
    • David Goulet's avatar
      Use local descriptor object to exclude self in path selection · 6ab07419
      David Goulet authored and Nick Mathewson's avatar Nick Mathewson committed
      TROVE-2017-12. Severity: Medium
      
      When choosing a random node for a circuit, directly use our router
      descriptor to exclude ourself instead of the one in the global
      descriptor list. That list could be empty because tor could be
      downloading them which could lead to not excluding ourself.
      
      Closes #21534
      6ab07419
  8. 28 Nov, 2017 1 commit
    • David Goulet's avatar
      hs-v2: Remove any expiring intro from the retry list · 3030741b
      David Goulet authored and Nick Mathewson's avatar Nick Mathewson committed
      TROVE-2017-13. Severity: High.
      
      In the unlikely case that a hidden service could be missing intro circuit(s),
      that it didn't have enough directory information to open new circuits and that
      an intro point was about to expire, a use-after-free is possible because of
      the intro point object being both in the retry list and expiring list at the
      same time.
      
      The intro object would get freed after the circuit failed to open and then
      access a second time when cleaned up from the expiring list.
      
      Fixes #24313
      3030741b
  9. 27 Nov, 2017 4 commits
  10. 18 Nov, 2017 2 commits
  11. 16 Nov, 2017 1 commit
    • Nick Mathewson's avatar
      Fix a traceback when closing a blocked connection "immediately". · 95238eb9
      Nick Mathewson authored
      When we close a connection via connection_close_immediately, we kill
      its events immediately. But if it had been blocked on bandwidth
      read/write, we could try to re-add its (nonexistent) events later
      from connection_bucket_refill -- if we got to that callback before
      we swept the marked connections.
      
      Fixes bug 24167.  Fortunately, this hasn't been a crash bug since we
      introduced connection_check_event in 0.2.9.10, and backported it.
      
      This is a bugfix on commit 89d42291, I believe, which
      appeared in Tor 0.1.0.1-rc.
      95238eb9
  12. 14 Nov, 2017 1 commit
  13. 13 Nov, 2017 1 commit
  14. 11 Nov, 2017 1 commit
  15. 10 Nov, 2017 1 commit
  16. 25 Oct, 2017 3 commits