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

Simon Déziel 1749931 at bugs.launchpad.net
Wed Feb 28 19:37:00 UTC 2018


Thanks Christian!

-- 
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:
  In Progress
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



More information about the Ubuntu-sponsors mailing list