[Bug 1749931] [NEW] unbound-control local socket broken by apparmor

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Ubuntu Foundations Team Bug Bot (crichton):

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: Incomplete

** Affects: unbound (Debian)
     Importance: Unknown
         Status: Unknown


** Tags: patch
-- 
unbound-control local socket  broken by apparmor
https://bugs.launchpad.net/bugs/1749931
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.