1. 09 Mar, 2020 1 commit
  2. 13 Feb, 2020 1 commit
  3. 31 Jan, 2020 1 commit
  4. 26 Jan, 2020 2 commits
  5. 17 Jun, 2019 1 commit
    • teor's avatar
      relaylist: stop using the current time when a consensus is downloaded twice · 3a521cc5
      teor authored
      Instead:
      * use the consensus valid-after time, or
      * use the supplied timestamp, or
      * warn and use the current time.
      
      This should fix the occasional CI failure, when the current time is 1 second
      later than the test consensus time. (Or it should warn, and we can fix the
      test code.)
      
      Fixes bug 30909; bugfix on 1.1.0.
      3a521cc5
  6. 27 Mar, 2019 1 commit
  7. 21 Mar, 2019 2 commits
  8. 13 Mar, 2019 1 commit
  9. 09 Mar, 2019 1 commit
  10. 08 Mar, 2019 4 commits
  11. 18 Dec, 2018 1 commit
    • juga's avatar
      relaylist: remove assertions that fail measurement · ac9406a6
      juga authored
      When the descriptor or network status of a relay was not obtained,
      some attributes can't be obtained it can be return None instead
      of failing the measurement.
      Also, there's no need for hasattr when getattr can just return
      None as default.
      
      Closes #28870. Bugfix v0.4.0
      ac9406a6
  12. 03 Dec, 2018 2 commits
    • juga's avatar
      globals: remove unused resolve and can_exit_to functions · bad22915
      juga authored
      They were used to resolve the IP of the destination and check
      whether an exit policy allows to exit to that IP, but when the
      destination is a CDN, the IP locally resolved would be different
      to the IP resolved in the exit, and when the IP resolved to
      IPv6, it was possible that the scanner didn't have IPv6.
      The correct method to check whether an exit policy allows to exit
      to an IP, would be to resolve the domain via Tor itself using
      RESOLVE and ADDRMAP events with that exit.
      bad22915
    • juga's avatar
      relaylist: add property is_unmeasured · 9e089b72
      juga authored
      9e089b72
  13. 23 Nov, 2018 1 commit
  14. 22 Nov, 2018 4 commits
  15. 22 Oct, 2018 1 commit
    • Matt Traudt's avatar
      Don't assume we can resolve a domain name · a7dce5ce
      Matt Traudt authored
      Even for a valid domain that usually resolves, sometimes the local DNS
      resolver won't be able to resolve it (duh). Catch the exception that gets
      thrown in that instance and fail gracefully by returning an empty list.
      a7dce5ce
  16. 25 Sep, 2018 1 commit
  17. 13 Sep, 2018 1 commit
  18. 05 Jul, 2018 6 commits
  19. 02 Jul, 2018 2 commits
  20. 24 Jun, 2018 4 commits
  21. 13 Jun, 2018 2 commits