1. 21 Sep, 2009 1 commit
  2. 17 Sep, 2009 1 commit
  3. 16 Sep, 2009 1 commit
  4. 15 Sep, 2009 1 commit
    • Sebastian Hahn's avatar
      make some bug 1090 warnings go away · 113ba0e7
      Sebastian Hahn authored
      When we excluded some Exits, we were sometimes warning the user that we
      were going to use the node regardless. Many of those warnings were in
      fact bogus, because the relay in question was not used to connect to
      the outside world.
      Based on patch by Rotor, thanks!
  5. 14 Sep, 2009 1 commit
    • Sebastian Hahn's avatar
      Fix a memory leak when parsing a ns · b792afa9
      Sebastian Hahn authored
      Adding the same vote to a networkstatus consensus leads to a memory leak
      on the client side. Fix that by only using the first vote from any given
      voter, and ignoring the others.
      Problem found by Rotor, who also helped writing the patch. Thanks!
  6. 03 Sep, 2009 1 commit
    • Roger Dingledine's avatar
      Fix obscure 64-bit big-endian hidserv bug · fcacf224
      Roger Dingledine authored
      Fix an obscure bug where hidden services on 64-bit big-endian
      systems might mis-read the timestamp in v3 introduce cells, and
      refuse to connect back to the client. Discovered by "rotor".
      Bugfix on
  7. 02 Sep, 2009 1 commit
  8. 01 Sep, 2009 1 commit
  9. 31 Aug, 2009 2 commits
    • Roger Dingledine's avatar
      Add getinfo accepted-server-descriptor. Clean spec. · 075c0040
      Roger Dingledine authored
      Add a "getinfo status/accepted-server-descriptor" controller
      command, which is the recommended way for controllers to learn
      whether our server descriptor has been successfully received by at
      least on directory authority. Un-recommend good-server-descriptor
      getinfo and status events until we have a better design for them.
    • Roger Dingledine's avatar
      Only send reachability status events on overall success/failure · 4c297f74
      Roger Dingledine authored
      We were telling the controller about CHECKING_REACHABILITY and
      REACHABILITY_FAILED status events whenever we launch a testing
      circuit or notice that one has failed. Instead, only tell the
      controller when we want to inform the user of overall success or
      overall failure. Bugfix on Fixes bug 1075. Reported
      by SwissTorExit.
  10. 29 Aug, 2009 1 commit
  11. 28 Aug, 2009 2 commits
  12. 26 Aug, 2009 1 commit
  13. 20 Aug, 2009 1 commit
    • Nick Mathewson's avatar
      Fix a rare infinite-recursion bug when shutting down. · 9d118277
      Nick Mathewson authored
      Once we had called log_free_all(), anything that tried to log a
      message (like a failed tor_assert()) would fail like this:
         1. The logging call eventually invokes the _log() function.
         2. _log() calls tor_mutex_lock(log_mutex).
         3. tor_mutex_lock(m) calls tor_assert(m).
         4. Since we freed the log_mutex, tor_assert() fails, and tries to
            log its failure.
         5. GOTO 1.
      Now we allocate the mutex statically, and never destroy it on
      Bugfix on, which introduced the log mutex.
      This bug was found by Matt Edman.
  14. 11 Aug, 2009 1 commit
  15. 10 Aug, 2009 2 commits
  16. 29 Jul, 2009 1 commit
  17. 28 Jul, 2009 6 commits
  18. 24 Jul, 2009 2 commits
  19. 07 Jul, 2009 1 commit
  20. 02 Jul, 2009 2 commits
    • Roger Dingledine's avatar
      Revise changelog. · 4e8d2284
      Roger Dingledine authored and Nick Mathewson's avatar Nick Mathewson committed
    • Karsten Loesing's avatar
      Make an attempt to fix bug 1024. · 3e6bb050
      Karsten Loesing authored and Nick Mathewson's avatar Nick Mathewson committed
      The internal error "could not find intro key" occurs when we want to send
      an INTRODUCE1 cell over a recently finished introduction circuit and think
      we built the introduction circuit with a v2 hidden service descriptor, but
      cannot find the introduction key in our descriptor.
      My first guess how we can end up in this situation is that we are wrong in
      thinking that we built the introduction circuit based on a v2 hidden
      service descriptor. This patch checks if we have a v0 descriptor, too, and
      uses that instead.
  21. 30 Jun, 2009 1 commit
  22. 25 Jun, 2009 1 commit
  23. 24 Jun, 2009 1 commit
  24. 22 Jun, 2009 2 commits
  25. 20 Jun, 2009 1 commit
  26. 19 Jun, 2009 3 commits
  27. 18 Jun, 2009 1 commit
    • Nick Mathewson's avatar
      tor-resolve: Don't automatically refuse .onion addresses. · 298dc95d
      Nick Mathewson authored
      If the Tor is running with AutomapHostsOnResolve set, it _is_
      reasonable to do a DNS lookup on a .onion address.  So instead we make
      tor-resolve willing to try to resolve anything.  Only if Tor refuses
      to resolve it do we suggest to the user that resolving a .onion
      address may not work.
      Fix for bug 1005.