Package: knot-resolver
Version: 1.0.0~beta3-1
Severity: normal
Dear Maintainer,
When calling:
trust_anchors.config('/etc/knot-resolver/yeti-root.key')
I discovered that Knot does not check that the file exists. If it
doesn't, there is no error and no warning, but Knot falls back to a
root anchor bootstrapped
-- System Information:
Debian Release: stretch/sid
APT prefers testing-updates
APT policy: (500, 'testing-updates'), (500, 'testing')
Architecture: amd64 (x86_64)
Kernel: Linux 4.1.5-x86_64-linode61 (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=fr_FR.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages knot-resolver depends on:
ii dns-root-data 2015052300+h+1
ii init-system-helpers 1.29
ii libc6 2.22-3
ii libdnssec0 2.1.1-1
ii libgeoip1 1.6.9-1
ii libhiredis0.13 0.13.3-2
ii libjs-d3 3.5.16-1
ii libjs-jquery 1.11.3+dfsg-4
ii libknot1 2.1.1-1
ii libluajit-5.1-2 2.0.4+dfsg-1
ii libmemcached11 1.0.18-4.1
ii libmemcachedutil2 1.0.18-4.1
ii libuv1 1.8.0-1
ii libzscanner0 2.1.1-1
ii lua-sec 0.5.1-1
ii lua-socket 3.0~rc1+git+321c0c9-1
knot-resolver recommends no packages.
knot-resolver suggests no packages.
-- Configuration Files:
/etc/knot-resolver/kresd.conf changed [not included]
-- no debconf information
