1. 17 Oct, 2016 1 commit
    • Nick Mathewson's avatar
      Write a bunch of module documentation. · aae034d1
      Nick Mathewson authored
      This commit adds or improves the module-level documenation for:
      
        buffers.c circuitstats.c command.c connection_edge.c control.c
        cpuworker.c crypto_curve25519.c crypto_curve25519.h
        crypto_ed25519.c crypto_format.c dircollate.c dirserv.c dns.c
        dns_structs.h fp_pair.c geoip.c hibernate.c keypin.c ntmain.c
        onion.c onion_fast.c onion_ntor.c onion_tap.c periodic.c
        protover.c protover.h reasons.c rephist.c replaycache.c
        routerlist.c routerparse.c routerset.c statefile.c status.c
        tor_main.c workqueue.c
      
      In particular, I've tried to explain (for each documented module)
      what each module does, what's in it, what the big idea is, why it
      belongs in Tor, and who calls it.  In a few cases, I've added TODO
      notes about refactoring opportunities.
      
      I've also renamed an argument, and fixed a few DOCDOC comments.
      aae034d1
  2. 13 Sep, 2016 1 commit
  3. 02 Aug, 2016 2 commits
  4. 19 Jul, 2016 1 commit
  5. 14 Jul, 2016 1 commit
  6. 30 May, 2016 1 commit
    • Nick Mathewson's avatar
      Replace nearly all XXX0vv comments with smarter ones · 4f1a04ff
      Nick Mathewson authored
      So, back long ago, XXX012 meant, "before Tor 0.1.2 is released, we
      had better revisit this comment and fix it!"
      
      But we have a huge pile of such comments accumulated for a large
      number of released versions!  Not cool.
      
      So, here's what I tried to do:
      
        * 0.2.9 and 0.2.8 are retained, since those are not yet released.
      
        * XXX+ or XXX++ or XXX++++ or whatever means, "This one looks
          quite important!"
      
        * The others, after one-by-one examination, are downgraded to
          plain old XXX.  Which doesn't mean they aren't a problem -- just
          that they cannot possibly be a release-blocking problem.
      4f1a04ff
  7. 15 Apr, 2016 1 commit
  8. 27 Feb, 2016 2 commits
  9. 12 Jan, 2016 1 commit
  10. 15 Dec, 2015 1 commit
  11. 02 Sep, 2015 1 commit
  12. 01 Sep, 2015 1 commit
  13. 25 Aug, 2015 1 commit
  14. 07 May, 2015 1 commit
  15. 14 Mar, 2015 1 commit
  16. 03 Mar, 2015 2 commits
  17. 11 Feb, 2015 1 commit
    • Nick Mathewson's avatar
      Remove mempools and buf freelists · 6f331645
      Nick Mathewson authored
      They have been off-by-default since 0.2.5 and nobody has complained. :)
      
      Also remove the buf_shrink() function, which hasn't done anything
      since we first stopped using contiguous memory to store buffers.
      
      Closes ticket 14848.
      6f331645
  18. 02 Jan, 2015 1 commit
  19. 30 Dec, 2014 1 commit
    • Yawning Angel's avatar
      Allow IPv4 and IPv6 addresses in SOCKS5 FQDN requests. · d87d4183
      Yawning Angel authored
      Supposedly there are a decent number of applications that "support"
      IPv6 and SOCKS5 using the FQDN address type.  While said applications
      should be using the IPv6 address type, allow the connection if
      SafeSocks is not set.
      
      Bug not in any released version.
      d87d4183
  20. 04 Nov, 2014 3 commits
  21. 28 Oct, 2014 1 commit
  22. 22 Oct, 2014 1 commit
  23. 01 Oct, 2014 2 commits
  24. 29 Sep, 2014 2 commits
  25. 08 May, 2014 1 commit
  26. 29 Apr, 2014 1 commit
  27. 19 Apr, 2014 1 commit
  28. 05 Mar, 2014 1 commit
  29. 26 Feb, 2014 1 commit
    • Nick Mathewson's avatar
      Monotonize the OOM-killer data timers · 833d0277
      Nick Mathewson authored
      In a couple of places, to implement the OOM-circuit-killer defense
      against sniper attacks, we have counters to remember the age of
      cells or data chunks.  These timers were based on wall clock time,
      which can move backwards, thus giving roll-over results for our age
      calculation.  This commit creates a low-budget monotonic time, based
      on ratcheting gettimeofday(), so that even in the event of a time
      rollback, we don't do anything _really_ stupid.
      
      A future version of Tor should update this function to do something
      even less stupid here, like employ clock_gettime() or its kin.
      833d0277
  30. 12 Feb, 2014 4 commits