Up to 1.19.3

[packages/unbound.git] / unbound-default_trust_anchor.patch

diff --git a/unbound-default_trust_anchor.patch b/unbound-default_trust_anchor.patch
index 7ffede3678da10fad8a4106dd477ad63e5143213..1d7fd649f4887a393bb29ab9414a09f9b87789d1 100644 (file)
--- a/unbound-default_trust_anchor.patch
+++ b/unbound-default_trust_anchor.patch
@@ -2,11 +2,11 @@ diff -dur unbound-1.4.22.orig/doc/example.conf.in unbound-1.4.22/doc/example.con
 --- unbound-1.4.22.orig/doc/example.conf.in    2014-03-12 13:31:42.000000000 +0100
 +++ unbound-1.4.22/doc/example.conf.in 2014-04-25 11:14:14.000000000 +0200
 @@ -342,7 +342,7 @@
-       # you start unbound (i.e. in the system boot scripts).  And enable:
+       # And then enable the auto-trust-anchor-file config item.
        # Please note usage of unbound-anchor root anchor is at your own risk
        # and under the terms of our LICENSE (see that file in the source).
 -      # auto-trust-anchor-file: "@UNBOUND_ROOTKEY_FILE@"
 +      auto-trust-anchor-file: "@UNBOUND_ROOTKEY_FILE@"
  
-       # File with DLV trusted keys. Same format as trust-anchor-file.
-       # There can be only one DLV configured, it is trusted from root down.
+       # trust anchor signaling sends a RFC8145 key tag query after priming.
+       # trust-anchor-signaling: yes