Skip to content
Snippets Groups Projects
  1. Apr 05, 2017
    • Daniel Kahn Gillmor's avatar
      Implement sensible default EDNS(0) padding policy. · 2dd9f406
      Daniel Kahn Gillmor authored and Daniel Salzman's avatar Daniel Salzman committed
      At NDSS 2017's DNS privacy workshop, I presented an empirical study of
      DNS padding policies:
      
      https://www.internetsociety.org/events/ndss-symposium/ndss-symposium-2017/dns-privacy-workshop-2017-programme#session3
      
      The slide deck is here:
      https://dns.cmrg.net/ndss2017-dprive-empirical-DNS-traffic-size.pdf
      
      The resulting recommendation from the research is that a simple
      padding policy is relatively cheap and still protective of metadata
      when DNS traffic is encrypted:
      
       * queries should be padded to a multiple of 128 octets
       * responses should be padded to a multiple of 468 octets
      
      Since future research could propose even better policies, and future
      DNS traffic characteristics might evolve, I've implemented this
      recommendation as a new function in libknot:
      knot_edns_default_padding_size()
      
      This changeset also modifies kdig to use this padding policy by
      default when doing queries over TLS, and defines +padding (with no
      argument) as a kdig option that forces the use of the default padding
      policy.
      
      With this changeset, any libknot user who wants to use "a sensible DNS
      padding policy" can just rely on the library; this means that if a
      better padding policy is determined in the future, it can be
      distributed to all users by upgrading libknot.
      2dd9f406
  2. Apr 04, 2017
  3. Apr 03, 2017
  4. Mar 30, 2017
  5. Mar 29, 2017
  6. Mar 27, 2017
  7. Mar 25, 2017
  8. Mar 24, 2017
  9. Mar 23, 2017
  10. Mar 21, 2017
  11. Mar 20, 2017
  12. Mar 17, 2017
  13. Mar 15, 2017
  14. Mar 14, 2017
  15. Mar 13, 2017