1. 04 Sep, 2018 4 commits
  2. 17 Aug, 2018 2 commits
  3. 16 Aug, 2018 2 commits
  4. 13 Aug, 2018 1 commit
  5. 08 Aug, 2018 1 commit
  6. 03 Aug, 2018 1 commit
  7. 02 Aug, 2018 2 commits
  8. 30 Jul, 2018 1 commit
  9. 29 Jul, 2018 3 commits
  10. 24 Jul, 2018 1 commit
  11. 16 Jul, 2018 1 commit
  12. 13 Jul, 2018 1 commit
  13. 11 Jul, 2018 1 commit
  14. 10 Jul, 2018 1 commit
  15. 09 Jul, 2018 1 commit
    • Iain R. Learmonth's avatar
      Provides more accurate DNS results · 48e5ff84
      Iain R. Learmonth authored
      This commit adds two new fields: {un,}verified_host_names.
      
      Whereas previously InetAddress was used to resolve reverse domain
      names, this instead changes the lookup mechanism to use JNDI allowing
      for a deeper view into the DNS. It also accounts for the fact that
      multiple PTR records are not forbidden in the DNS specification and are
      often used in shared hosting scenarios.
      
      A host name is considered verified if it has a matching forward record.
      If a PTR value is found to have multiple A records, it will be
      considered verified if any one of the A records matches the original
      address. If no matching record is found, it will be reported as an
      unverified host name.
      
      Previously, unverified host names were discarded internally by the
      InetAddress lookup mechanism and so this data could not be used.
      
      To maintain "bug compatibility" with the previous implementation of the
      "host_name" field, which will now be deprecated, the IP address is
      returned when a lookup fails.
      
      The host_name field continues to be used, but now will consider all
      verified and unverified host names. If finer grained filtering is
      needed, then a seperate ticket could be filed for that, but it is
      unclear that it is useful enough to justify the work.
      
      Fixes: #18342
      48e5ff84
  16. 29 May, 2018 2 commits
  17. 17 Apr, 2018 2 commits
  18. 16 Apr, 2018 1 commit
  19. 06 Apr, 2018 1 commit
  20. 05 Apr, 2018 1 commit
  21. 04 Apr, 2018 1 commit
  22. 27 Mar, 2018 1 commit
    • iwakeh's avatar
      Only unescape valid UTF. · 532ef347
      iwakeh authored
      Add a utility method for only un-escaping valid utf and supply a test
      as well as test data for this issue.
      
      Fixes task-22594.
      532ef347
  23. 13 Mar, 2018 3 commits
  24. 08 Mar, 2018 1 commit
  25. 07 Feb, 2018 3 commits
    • Karsten Loesing's avatar
      Prepare for 5.0-1.10.1 release. · a66bfd14
      Karsten Loesing authored
      a66bfd14
    • Karsten Loesing's avatar
      Prepare for 5.0-1.10.0 release. · 9830f7ae
      Karsten Loesing authored
      9830f7ae
    • Karsten Loesing's avatar
      Don't rely on system time for writing histories. · a7418b7c
      Karsten Loesing authored
      Rather than on system time we're now depending on the last time a
      relay or bridge was seen in a consensus or status to determine when
      history ends for this relay.
      
      This has the advantage of making the write step deterministic, and it
      produces the exact same graph intervals for the different documents of
      a given relay or bridge.
      
      A minor downside is that we're now depending on node statuses _and_
      another status file in order to produce a history document. Should be
      okay.
      
      Define graph end as last full data point before the relay/bridge was
      last seen.
      
      Also make sure that graphs end at that defined graph end and do not
      continue just because there's more history available. This is mostly
      to exclude falsely-reported statistics.
      
      Implements #16513.
      a7418b7c
  26. 20 Dec, 2017 1 commit