1. 20 Jan, 2017 1 commit
  2. 16 Jan, 2017 1 commit
  3. 09 Jan, 2017 1 commit
  4. 02 Jan, 2017 2 commits
  5. 23 Dec, 2016 3 commits
  6. 15 Dec, 2016 1 commit
  7. 14 Dec, 2016 1 commit
  8. 10 Sep, 2016 1 commit
    • Kevin Darbyshire-Bryant's avatar
      Compile time option NO_ID · 7ac9ae11
      Kevin Darbyshire-Bryant authored
      Some consider it good practice to obscure software version numbers to
      clients.  Compiling with -DNO_ID removes the *.bind info structure.
      This includes: version, author, copyright, cachesize, cache insertions,
      evictions, misses & hits, auth & servers.
      7ac9ae11
  9. 01 Sep, 2016 1 commit
  10. 31 Aug, 2016 1 commit
  11. 29 Aug, 2016 4 commits
  12. 14 Aug, 2016 2 commits
  13. 12 Aug, 2016 1 commit
  14. 05 Aug, 2016 1 commit
  15. 24 Jul, 2016 1 commit
  16. 23 Jul, 2016 3 commits
  17. 17 Jul, 2016 2 commits
  18. 12 Jul, 2016 4 commits
    • Simon Kelley's avatar
      d6dce53e
    • Kevin Darbyshire-Bryant's avatar
      Fix problem with --dnssec-timestamp · 06093a9a
      Kevin Darbyshire-Bryant authored
      whereby receipt of SIGHUP would erroneously engage timestamp checking.
      06093a9a
    • Ivan Kokshaysky's avatar
      Fix logic error in Linux netlink code. · 1d07667a
      Ivan Kokshaysky authored
      This could cause dnsmasq to enter a tight loop on systems
      with a very large number of network interfaces.
      1d07667a
    • Simon Kelley's avatar
      Fix bad behaviour with some DHCP option arrangements. · 591ed1e9
      Simon Kelley authored
      The check that there's enough space to store the DHCP agent-id
      at the end of the packet could succeed when it should fail
      if the END option is in either of the oprion-overload areas.
      That could overwrite legit options in the request and cause
      bad behaviour. It's highly unlikely that any sane DHCP client
      would trigger this bug, and it's never been seen, but this
      fixes the problem.
      
      Also fix off-by-one in bounds checking of option processing.
      Worst case scenario on that is a read one byte beyond the
      end off a buffer with a crafted packet, and maybe therefore
      a SIGV crash if the memory after the buffer is not mapped.
      
      Thanks to Timothy Becker for spotting these.
      591ed1e9
  19. 11 Jul, 2016 3 commits
  20. 07 Jul, 2016 5 commits
  21. 18 May, 2016 1 commit