Reload CA bundle on server configuration reload #1261
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
While opening private keys indeed makes sense only while Unbound has root privileges, because they
should be readable only by root, right to read public keys should pose no threat. Thus it makes sense for administrator to allow CA bundle to be read by any user and Unbound should be able to refresh it on reload.
Unfortunately there is no way of telling whether the bundle will be accessible after chroot, thus CA
bundle can not be refreshed if chroot is used.
Fix: #1260