https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=292275
--- Comment #1 from John Baldwin <[email protected]> --- Looking at the timestamps in /var/unbound, it seemed I first enabled it at the end of November 2014, and the key files were apparently not regenerated when I ran `setup`: drwxr-xr-x 2 unbound unbound 2 Aug 16 2014 conf.d -rw-r--r-- 1 root unbound 193 Jan 7 21:17 control.conf drwxr-xr-x 2 root unbound 2 Jan 9 2014 dev -rw-r--r-- 1 root unbound 170 Jan 7 21:18 forward.conf -rw-r--r-- 1 root unbound 189 Jan 7 21:17 lan-zones.conf -rw-r--r-- 1 unbound unbound 25088 Jan 21 2014 log -rw-r--r-- 1 unbound unbound 761 Jan 7 21:41 root.key -rw-r--r-- 1 root unbound 403 Jan 7 21:17 unbound.conf -rw-r----- 1 unbound unbound 1277 Dec 22 2014 unbound_control.key -rw-r----- 1 unbound unbound 802 Dec 22 2014 unbound_control.pem -rw-r----- 1 unbound unbound 1281 Dec 22 2014 unbound_server.key -rw-r----- 1 unbound unbound 790 Dec 22 2014 unbound_server.pem Also, I believe the difference in unbound.conf after running the `/etc/rc.d/local_unbound setup` is this: Index: unbound.conf =================================================================== --- unbound.conf (revision 397) +++ unbound.conf (working copy) @@ -1,14 +1,14 @@ -# Generated by local-unbound-setup +# This file was generated by local-unbound-setup. +# Modifications will be overwritten. server: - username: unbound - directory: /var/unbound - chroot: /var/unbound - pidfile: /var/run/local_unbound.pid - #auto-trust-anchor-file: /var/unbound/root.key - #logfile: /var/unbound/log - #verbosity: 2 + username: unbound + directory: /var/unbound + chroot: /var/unbound + pidfile: /var/run/local_unbound.pid + auto-trust-anchor-file: /var/unbound/root.key + so-sndbuf: 0 -remote-control: - control-enable: "yes" - include: /var/unbound/forward.conf +include: /var/unbound/lan-zones.conf +include: /var/unbound/control.conf +include: /var/unbound/conf.d/*.conf (I had modified the original config generated by local-unbound-setup back in 2014 to add the `remote-control` clause which in the modern config is now handled in control.conf.) My best guess is that in late 2014 this host would have been running 10-STABLE. -- You are receiving this mail because: You are the assignee for the bug.
