unbound (1.15.0-5) unstable; urgency=medium

  With this version we switched from the control interface on localhost
  port 8953 to a unix-domain socket /run/unbound.ctl. This interface
  does not use the keys/certificates (/etc/unbound/unbound_control.key,
  /etc/unbound/unbound_server.pem etc) which are set up by the
  unbound-control-setup utility.

  This change is done in the new config file fragment,
  /etc/unbound/unbound.conf.d/remote-control.conf

 -- Michael Tokarev <mjt@tls.msk.ru>  Thu, 28 Apr 2022 11:27:58 +0300

unbound (1.15.0-2) unstable; urgency=medium

  Starting with 1.15.0-2, we removed the debian-specific patch which
  flipped the default value for the remote-control: control-enable
  from "no" to "yes". Upstream default value for this parameter is "no"
  but since Debian version 1.9.6-1, the default value in Debian was
  set to "yes" (without mentioning this in NEWS and without fixing the
  manual page). This was unexpected and confusing, and differs from the
  upstream.  Starting 1.15.0-2, we're now back to the upstream default,
  which means unbound-control will not work unless explicitly enabled
  in the config file like this:

     remote-control:
       control-enable: yes

  New /etc/unbound/unbound.conf.d/remote-control.conf includes this
  change so with the default config it will be re-enabled automatically.

 -- Michael Tokarev <mjt@tls.msk.ru>  Mon, 18 Apr 2022 10:42:57 +0300

unbound (1.11.0-1) unstable; urgency=medium

  The default Debian config file shipped in the unbound package has changed
  from using the "include:" directive to using the "include-toplevel:"
  directive in order to include the config file fragments in
  /etc/unbound/unbound.conf.d/*.conf into the unbound configuration.

  The "include-toplevel:" directive has been newly introduced in unbound
  1.11.0 and it requires that any included config file fragment begin its own
  clause (e.g., "server:").

  The existing "include:" directive that was used in previous Debian releases
  of the unbound package only performed textual inclusion, and it was possible
  to construct a set of config file fragments that depended on the presence or
  ordering of specific config file fragments in order to parse correctly. For
  instance, a config file fragment could have specified an option that can
  only appear in the "server:" clause, and rely on a previously included
  config file fragment to begin that clause. This behavior is no longer
  allowed by the use of the "include-toplevel:" directive because it is not
  robust against config file fragments being added, removed, or reordered.

  If you are upgrading the unbound package and you have installed any config
  file fragments into /etc/unbound/unbound.conf.d/ you should check that each
  config file fragment begins its own clause (e.g., "server:") and update each
  config file fragment as necessary to be compatible with the behavior of the
  "include-toplevel:" directive.

  If needed, the previous behavior can be restored by changing the following
  line in /etc/unbound/unbound.conf:

      include-toplevel: "/etc/unbound/unbound.conf.d/*.conf"

  to its previous setting:

      include: "/etc/unbound/unbound.conf.d/*.conf"

 -- Robert Edmonds <edmonds@debian.org>  Sun, 09 Aug 2020 19:39:01 -0400
