1. 18 Sep, 2019 1 commit
    • Nick Mathewson's avatar
      Add a rate-limit to our warning about the disabled .exit notation · f0e41209
      Nick Mathewson authored
      This warning would previously be given every time we tried to open a
      connection to a foo.exit address, which could potentially be used to
      flood the logs.  Now, we don't allow this warning to appear more
      than once every 15 minutes.
      
      Fixes bug 31466; bugfix on 0.2.2.1-alpha, when .exit was first
      deprecated.
      f0e41209
  2. 22 Aug, 2018 1 commit
  3. 11 Sep, 2017 1 commit
  4. 15 May, 2017 1 commit
  5. 02 Mar, 2017 1 commit
  6. 09 Dec, 2016 1 commit
  7. 01 Nov, 2016 1 commit
  8. 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
  9. 14 Oct, 2016 1 commit
  10. 05 Oct, 2016 1 commit
  11. 02 Oct, 2016 1 commit
  12. 13 Sep, 2016 1 commit
    • teor (Tim Wilson-Brown)'s avatar
      Implement Prop #260: Single Onion Services · b560f852
      teor (Tim Wilson-Brown) authored and Nick Mathewson's avatar Nick Mathewson committed
      Add experimental OnionServiceSingleHopMode and
      OnionServiceNonAnonymousMode options. When both are set to 1, every
      hidden service on a tor instance becomes a non-anonymous Single Onion
      Service. Single Onions make one-hop (direct) connections to their
      introduction and renzedvous points. One-hop circuits make Single Onion
      servers easily locatable, but clients remain location-anonymous.
      This is compatible with the existing hidden service implementation, and
      works on the current tor network without any changes to older relays or
      clients.
      
      Implements proposal #260, completes ticket #17178. Patch by teor & asn.
      
      squash! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! fixup! Implement Prop #260: Single Onion Services
      
      Redesign single onion service poisoning.
      
      When in OnionServiceSingleHopMode, each hidden service key is poisoned
      (marked as non-anonymous) on creation by creating a poison file in the
      hidden service directory.
      
      Existing keys are considered non-anonymous if this file exists, and
      anonymous if it does not.
      
      Tor refuses to launch in OnionServiceSingleHopMode if any existing keys
      are anonymous. Similarly, it refuses to launch in anonymous client mode
      if any existing keys are non-anonymous.
      
      Rewrite the unit tests to match and be more comprehensive.
      Adds a bonus unit test for rend_service_load_all_keys().
      b560f852
  13. 24 Aug, 2016 4 commits
  14. 02 Aug, 2016 3 commits
  15. 28 Jul, 2016 2 commits
  16. 09 Jun, 2016 1 commit
  17. 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
  18. 09 May, 2016 1 commit
  19. 28 Mar, 2016 1 commit
  20. 26 Mar, 2016 1 commit
  21. 27 Feb, 2016 1 commit
  22. 27 Jan, 2016 1 commit
  23. 17 Dec, 2015 2 commits
  24. 16 Dec, 2015 4 commits
  25. 08 Dec, 2015 1 commit
  26. 27 Nov, 2015 3 commits
  27. 26 Nov, 2015 1 commit
  28. 20 Nov, 2015 1 commit