1. 20 Jun, 2009 1 commit
  2. 19 Jun, 2009 3 commits
  3. 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.
  4. 16 Jun, 2009 2 commits
  5. 12 Jun, 2009 1 commit
  6. 08 Jun, 2009 2 commits
  7. 07 Jun, 2009 1 commit
  8. 05 Jun, 2009 1 commit
  9. 03 Jun, 2009 3 commits
    • Karsten Loesing's avatar
      Update the rest of the geoip file. · 48bf1d97
      Karsten Loesing authored
    • Nick Mathewson's avatar
      Update the geoip file · 0b23035e
      Nick Mathewson authored
    • Nick Mathewson's avatar
      Fix gprof bottlenecks on exit nodes found by Jacob. · b262e765
      Nick Mathewson authored
      Apparently all the stuff that does a linear scan over all the DNS
      cache entries can get really expensive when your DNS cache is very
      large.  It's hard to say how much this will help performance, since
      gprof doesn't count time spent in OpenSSL or zlib, but I'd guess 10%.
      Also, this patch removes calls to assert_connection_ok() from inside
      the read and write callbacks, which are similarly unneeded, and a
      little costlier than I'm happy with.
      This is probably worth backporting to 0.2.0.
  10. 31 May, 2009 2 commits
  11. 30 May, 2009 3 commits
  12. 28 May, 2009 2 commits
  13. 27 May, 2009 7 commits
  14. 25 May, 2009 5 commits
  15. 22 May, 2009 2 commits
  16. 18 May, 2009 1 commit
    • Nick Mathewson's avatar
      Possible fix for crash bug related to event timeouts. [Bug 957] · 34030a3d
      Nick Mathewson authored
      If we ever add an event, then set it, then add it again, there will be
      now two pointers to the event in the event base.  If we delete one and
      free it, the first pointer will still be there, and possibly cause a
      crash later.
      This patch adds detection for this case to the code paths in
      eventdns.c, and works around it.  If the warning message ever
      displays, then a cleverer fix is in order.
      {I am not too confident that this *is* the fix, since bug 957 is very
      tricky.  If it is, it is a bugfix on 0.2.0.}
  17. 17 May, 2009 3 commits