debcrafters-packages team mailing list archive

[Andreas Hasenack <2123821@xxxxxxxxxxxxxxxxxx>]

> Worse yet, don't know what to add to the rsyslog policy to allow this
access.

I was stracing rsyslog, and it didn't get any DENIED error. But when I
straced systemd-journald, the DAEMON, that's what was denied access. And
by the rsyslog profile. This is what I cannot understand. It's another
process. How can I add rules to the rsyslog profile about what another
process should be able to do or not. There is something else going on
here. systemd-journald is unconfined from the POV of the container, but
it's definitely confined from the POV of the host. Maybe this is similar
to LP: #2121552?

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/2123821

Title:
  bad restriction: apparmor="DENIED" [...] namespace="root//lxd-n_<var-
  snap-lxd-common-lxd>" profile="rsyslogd"
  name="/run/systemd/journal/dev-log"

Status in apparmor package in Ubuntu:
  New
Status in rsyslog package in Ubuntu:
  Confirmed

Bug description:
  On my Questing system running LXD containers, my kernel log is full of
  messages like:

  [  129.551382] audit: type=1400 audit(1757925628.229:1005):
  apparmor="DENIED" operation="sendmsg" class="file"
  namespace="root//lxd-q_<var-snap-lxd-common-lxd>" profile="rsyslogd"
  name="/run/systemd/journal/dev-log" pid=5370 comm="systemd-journal"
  requested_mask="r" denied_mask="r" fsuid=1000000 ouid=1000000

  One of my containers is named "q", hence the "root//lxd-q...". Some
  actual functionality is likely broken in the container.

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