touch-packages team mailing list archive

[Martin Pitt <martin.pitt@xxxxxxxxxx>]

So at the moment, apparmor starts After=local-fs.target and
Before=sysinit.target.

network-interface-security.conf does:

    start on (starting network-interface or starting network-manager or
starting networking)

network-interface corresponds to ifup@.service, networking is just the
ifupdown init.d script; these two need an  After=apparmor.service.
NetworkManager.service has DefaultDependencies=yes (the default), thus
the ordering there is fine already.

It seems to me that adding these two ordering constraints is simpler and
potentially also more efficient than running /sbin/apparmor_parser
manually?

** Also affects: systemd (Ubuntu)
   Importance: Undecided
       Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ifupdown in Ubuntu.
https://bugs.launchpad.net/bugs/1438249

Title:
  /sbin/dhclient is unconfined after switch to systemd (aka, equivalent
  of upstart's network-interface-security.conf not implemented)

Status in ifupdown package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  dhclient is starting before the apparmor profile for it is loaded
  which results in the following output from aa-status:

  $ sudo aa-status
  ...
  4 profiles are in enforce mode.
     /sbin/dhclient
  ...
  1 processes are unconfined but have a profile defined.
     /sbin/dhclient (634)

  Upstart had the network-interface-security.conf job to make sure this
  didn't happen. We wanted the cache loading library to be implemented
  in time (bug #1385414), but it still hasn't landed. Having the cache
  loading library in place would mean that this bug would also be fixed,
  but now we need to fix this bug differently for 15.04 and it must be
  fixed by release.

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