1. 20 Jul, 2021 1 commit
  2. 01 Jul, 2021 1 commit
  3. 23 Mar, 2021 1 commit
  4. 17 Mar, 2021 1 commit
  5. 12 Mar, 2021 1 commit
  6. 22 Feb, 2021 1 commit
    • David Goulet's avatar
      relay: Remove dirport reachability self test · 38649b4f
      David Goulet authored
      
      
      Regular relays are about to get their DirPort removed so that reachability
      test is not useful anymore
      
      Authorities will still use the DirPort but because network reentry towards
      their DirPort is now denied network wide, this test is not useful anymore and
      so it should simply be considered reachable at all time.
      
      Part of #40282
      
      Signed-off-by: David Goulet's avatarDavid Goulet <dgoulet@torproject.org>
      38649b4f
  7. 19 Feb, 2021 1 commit
    • David Goulet's avatar
      hs-v2: Removal of service and relay support · 2c865542
      David Goulet authored
      
      
      This is unfortunately massive but both functionalities were extremely
      intertwined and it would have required us to actually change the HSv2 code in
      order to be able to split this into multiple commits.
      
      After this commit, there are still artefacts of v2 in the code but there is no
      more support for service, intro point and HSDir.
      
      The v2 support for rendezvous circuit is still available since that code is
      the same for the v3 and we will leave it in so if a client is able to
      rendezvous on v2 then it can still transfer traffic. Once the entire network
      has moved away from v2, we can remove v2 rendezvous point support.
      
      Related to #40266
      
      Signed-off-by: David Goulet's avatarDavid Goulet <dgoulet@torproject.org>
      2c865542
  8. 27 Jan, 2021 1 commit
  9. 12 Jan, 2021 1 commit
    • David Goulet's avatar
      hs-v3: Require reasonably live consensus · 04b02639
      David Goulet authored
      
      
      Some days before this commit, the network experienced a DDoS on the directory
      authorities that prevented them to generate a consensus for more than 5 hours
      straight.
      
      That in turn entirely disabled onion service v3, client and service side, due
      to the subsystem requiring a live consensus to function properly.
      
      We know require a reasonably live consensus which means that the HSv3
      subsystem will to its job for using the best consensus tor can find. If the
      entire network is using an old consensus, than this should be alright.
      
      If the service happens to use a live consensus while a client is not, it
      should still work because the client will use the current SRV it sees which
      might be the previous SRV for the service for which it still publish
      descriptors for.
      
      If the service is using an old one and somehow can't get a new one while
      clients are on a new one, then reachability issues might arise. However, this
      is a situation we already have at the moment since the service will simply not
      work if it doesn't have a live consensus while a client has one.
      
      Fixes #40237
      
      Signed-off-by: David Goulet's avatarDavid Goulet <dgoulet@torproject.org>
      04b02639
  10. 12 Nov, 2020 1 commit
    • Samanta Navarro's avatar
      Fix typos. · 4a0cd795
      Samanta Navarro authored and David Goulet's avatar David Goulet committed
      Typos found with codespell.
      
      Please keep in mind that this should have impact on actual code
      and must be carefully evaluated:
      
      src/core/or/lttng_circuit.inc
      -    ctf_enum_value("CONTROLER", CIRCUIT_PURPOSE_CONTROLLER)
      +    ctf_enum_value("CONTROLLER", CIRCUIT_PURPOSE_CONTROLLER)
      4a0cd795
  11. 03 Nov, 2020 2 commits
  12. 02 Nov, 2020 1 commit
  13. 04 Aug, 2020 1 commit
  14. 29 Jul, 2020 1 commit
  15. 10 Jul, 2020 2 commits
  16. 19 Feb, 2020 1 commit
  17. 29 Jan, 2020 1 commit
    • teor's avatar
      mainloop: Simplify ip_address_changed() · c8ba2c47
      teor authored
      Simplify ip_address_changed() by removing redundant checks
      (all exits are relays, and need to rebuild their descriptor when their
      IP addresses change).
      
      Rewrite the function comment, and rename the argument, so the function
      is easier to understand and use.
      
      Closes 33091.
      c8ba2c47
  18. 16 Jan, 2020 2 commits
    • Nick Mathewson's avatar
      Rename dirclient_modes.h identifiers to start with dirclient_ · 6ba4b5e5
      Nick Mathewson authored
      This is an automated commit, generated by this command:
      
      ./scripts/maint/rename_c_identifier.py \
              directory_must_use_begindir dirclient_must_use_begindir \
              directory_fetches_from_authorities dirclient_fetches_from_authorities \
              directory_fetches_dir_info_early dirclient_fetches_dir_info_early \
              directory_fetches_dir_info_later dirclient_fetches_dir_info_later \
              directory_too_idle_to_fetch_descriptors dirclient_too_idle_to_fetch_descriptors
      6ba4b5e5
    • Nick Mathewson's avatar
      Move dirclient-related functions out of dirserv, and reenable them · 773bcf56
      Nick Mathewson authored
      I had incorrectly identified these functions as dircache-only, when
      in fact they apply to everyone who acts a directory client.
      773bcf56
  19. 08 Jan, 2020 1 commit
  20. 06 Nov, 2019 1 commit
  21. 22 Oct, 2019 3 commits
  22. 21 Oct, 2019 1 commit
    • Roger Dingledine's avatar
      respect accountingmax during soft hibernation · a7ccd9a9
      Roger Dingledine authored
      Relays now respect their AccountingMax bandwidth again. When relays
      entered "soft" hibernation (which typically starts when we've hit
      90% of our AccountingMax), we had stopped checking whether we should
      enter hard hibernation. Soft hibernation refuses new connections and
      new circuits, but the existing circuits can continue, meaning that
      relays could have exceeded their configured AccountingMax.
      
      This commit rolls back some of the cpu-saving fixes, where we tried
      to avoid calling so many of our events while we're off the network.
      
      That's because PERIODIC_EVENT_FLAG_NEED_NET checks net_is_disabled(),
      which returns true even if we're only in soft hibernation.
      
      Fixes bug 32108; bugfix on 0.4.0.1-alpha.
      a7ccd9a9
  23. 20 Oct, 2019 1 commit
  24. 09 Oct, 2019 1 commit
  25. 05 Sep, 2019 1 commit
  26. 05 Jun, 2019 1 commit
  27. 06 May, 2019 1 commit
  28. 02 May, 2019 2 commits
  29. 30 Apr, 2019 4 commits
  30. 25 Apr, 2019 2 commits