Unbound file ownership

vario · 2023-04-06 08:01:54

I am just getting to grips with "unbound" and have found it necessary to change the installation file ownerships from root:root to unbound:unbound or I will get a permission denied error on the trust-anchor file when I start unbound, causing it to fail.
Apparently unbound will write to the trust-anchor file so it needs access. Have I missed something in the Arch setup?

Neil.

seth · 2023-04-06 08:42:55

Please don't paraphrase, https://bbs.archlinux.org/viewtopic.php?id=57855
What file has what restriting permissions and which "installation file" ownership do you change?

https://wiki.archlinux.org/title/Unboun … validation

/etc/unbound/trusted-key.key is copied from /etc/trusted-key.key

There's a hook and
https://github.com/archlinux/svntogit-c … files.conf
The default trusted-key.key according to https://github.com/archlinux/svntogit-p … k/PKGBUILD is 644 (root:root)
So you might have to alter the ownership of the copied tmpfile, https://wiki.archlinux.org/title/System … rary_files

vario · 2023-04-07 05:34:55

Sorry, it is to the installation directory /etc/unbound, and the file /etc/unbound/trusted-key.key (or whatever file you specify as your trust anchor), that the unbound process requires write access so it can overwrite it with a temporary file it creates in /etc/unbound.

seth · 2023-04-07 06:12:25

/etc/unbound/trusted-key.key is generated by the package supplied tmpfile or pacman hook, so you'd have to file a bug against the package, but you need to provide the actual error IO, not some random description (ie. what command and config triggers this - runtime write access to /etc by unprivileged users seems weird)

Arch Linux

#1 2023-04-06 08:01:54

Unbound file ownership

#2 2023-04-06 08:42:55

Re: Unbound file ownership

#3 2023-04-07 05:34:55

Re: Unbound file ownership

#4 2023-04-07 06:12:25

Re: Unbound file ownership

Board footer