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

[Ubuntu Foundations Team Bug Bot]

The attachment "18.04-lp1749931.debdiff" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1749931

Title:
  unbound-control local socket  broken by apparmor

Status in unbound package in Ubuntu:
  Incomplete
Status in unbound package in Debian:
  Unknown

Bug description:
  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).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unbound/+bug/1749931/+subscriptions