1. 27 Jun, 2017 3 commits
  2. 26 Jun, 2017 1 commit
  3. 23 Jun, 2017 5 commits
  4. 21 Jun, 2017 1 commit
  5. 19 Jun, 2017 6 commits
  6. 16 Jun, 2017 2 commits
  7. 15 Jun, 2017 4 commits
  8. 14 Jun, 2017 2 commits
  9. 13 Jun, 2017 4 commits
  10. 12 Jun, 2017 3 commits
  11. 09 Jun, 2017 2 commits
    • Vladimír Čunát's avatar
    • Vladimír Čunát's avatar
      validate: work around some SERVFAILs (iterating mode) · fe77cee9
      Vladimír Čunát authored
      - This affects the iterating mode only (except for a verbose message).
      - The problem was introduced when implementing forwarding in 651c5aad.
      - Example that was affected: *.org.ru.
      
      When the same server is authoritative for multiple consecutive zones,
      with a higher one being signed and a lower one being unsigned, we may
      get an unsigned answer even in case we *think* we're currently in a
      signed zone.
      
      In particular, DS (sub-)queries are important because of being used to
      prove the insecurity of zones - in that case the iterator can correctly
      determine the (unexpected) zone name from which the answer came, due to
      seeing the SOA record, but that is too late for zone_cut_check() to try
      getting a trust chain to it, so we need to YIELD for it to do it.
      fe77cee9
  12. 08 Jun, 2017 2 commits
  13. 07 Jun, 2017 3 commits
  14. 05 Jun, 2017 2 commits