1. 02 Aug, 2018 2 commits
    • Karsten Loesing's avatar
      Add change log entry for #26963. · ed6d7dfd
      Karsten Loesing authored
      ed6d7dfd
    • Iain R. Learmonth's avatar
      Stop sharing the JNDI DirContext · 2b6916bd
      Iain R. Learmonth authored
      In the implementation of more accurate DNS resolution, the DirContext
      used by JNDI lookups was shared in a utility class. It turns out that
      InitialDirContext, the implementation we used, is very not thread-safe
      and so as a result lookups would often fail to complete.
      
      This commit creates a new DirContext for every lookup. The overhead in
      doing so is minimal and ensures that we do not have thread safety
      issues.
      
      This commit also increases RDNS_LOOKUP_WORKERS_NUM to 30 (from 5). The
      majority of time in these threads is spent waiting for replies and so
      there are gains to be had in increasing the number of requests in
      flight.
      
      Fixes: #26963
      2b6916bd
  2. 30 Jul, 2018 1 commit
  3. 29 Jul, 2018 4 commits
  4. 24 Jul, 2018 1 commit
  5. 19 Jul, 2018 2 commits
  6. 16 Jul, 2018 2 commits
  7. 13 Jul, 2018 1 commit
  8. 11 Jul, 2018 1 commit
  9. 10 Jul, 2018 1 commit
  10. 09 Jul, 2018 2 commits
    • 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
    • Iain R. Learmonth's avatar
      Adds a DomainNameSystem utility class · 5ba56c85
      Iain R. Learmonth authored
      This class uses JNDI to look up resource record values from the Domain
      Name System using the system configured resolver.
      
      See: #18342
      5ba56c85
  11. 04 Jul, 2018 1 commit
  12. 30 May, 2018 1 commit
  13. 29 May, 2018 2 commits
  14. 18 Apr, 2018 1 commit
  15. 17 Apr, 2018 2 commits
  16. 16 Apr, 2018 1 commit
  17. 06 Apr, 2018 4 commits
  18. 05 Apr, 2018 1 commit
  19. 04 Apr, 2018 1 commit
  20. 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
  21. 15 Mar, 2018 1 commit
  22. 13 Mar, 2018 4 commits
  23. 08 Mar, 2018 1 commit
  24. 08 Feb, 2018 1 commit
  25. 07 Feb, 2018 1 commit