Public bug reported:
When trying to setup unbound to use local socket for unbound-control,
the resulting socket has the wrong owner and the wrong permission, which
make it useless as it requires a root process to use it.
The first issue is that apparmor denies chown to unbound, which result
in a failure to set the socket owner/group to unbound/unbound.
The second issue is that the chmod of the socket fails, which result in
a socket that can be write to only by the unbound user, and so make it
useless for any process that is added to the unbound group (which is the
recommended way to access the unbound-control socket).
** Affects: unbound (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1749931
Title:
unbound-control local socket broken by apparmor
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1749931/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
