You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A prior test seems to have not been done careful: The Unbound daemon itself does NOT create the root trust anchors from internal data if missing. Only unbound-anchor does this.
There are several options to bootstrap it:
- Ship unbound-anchor and add "Provides" + "Conflicts" for Debian's unbound-anchor package.
- Bootstrap them from online data, though there is no DNSKEY format file with the exact needed data, but they would need to be extracted from https://www.internic.net/domain/root.zone (DNSKEY format, but large document) or https://data.iana.org/root-anchors/root-anchors.xml (exact needed keys, but XML format), and we'd again introduce the attack vector as of download with HTTPS authenticity only.
- Ship it, hardcoded in our build script.
- Use again the dns-root-data package from Debian. For now, since we do not distribute our package yet, hence need to assure dns-root-data is installed anyway on dietpi-software Unbound installs. Trusting Debian and the additional APT-side authenticity is probably easier in any case. We will go with this for now, aligning with the Debian package. Once we ship it with our own APT repository, we can again think about shipping the initial key with the package itself, for easier maintenance by running unbound-anchor within the build script. However, instead of updating the anchors on every service start, we bootstrap them only once on package install, if missing, generally verifying that Unbound can keep them updated even after long downtimes.
0 commit comments