Skip to content

Conversation

TomasKorbar
Copy link

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

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: NLnetLabs#1260
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[FR] Allow Unbound to reload CA bundle

1 participant