Simon, thank you very much for taking over. I am very much with your proposal: Moving that script from unbound to unbound-anchor plus making unbound-anchor a dependency of libunbound2. That was my first thought as well.
However, there might be another approach: The package "dns-root-data" is not just in Universe but in Main and is one of the sources of that root.key already. Perhaps it is easier to update the package "dns-root-data" manually and then - simply symlink the root.keys or/and - change libunbound2 to use that root.key on default directly (set at compile time). With such an approach, no script and no timer would be needed. Nevertheless, I am not sure whether this approached is "allowed" security vise because an (additional) individual has control about the root.key – at least in Debian world, then. Andreas, yes that other report is about the very same symptom. I completely forgot to mention that report as I found this issue and that report already with Ubuntu 14.04 LTS. I was not able to investigate this issue until now. Thanks for adding it. My report is a bit broader because it affects all apps which rely on libunbound2 actually. But yes, the cause is the very same. By the way in that other report, to answer the section ‘PS’ asked by Thue-Janus: unbound-host must be invoked with parameter -D to trigger the expected error. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1771545 Title: root.key might be missing To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1771545/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
