1. 09 Jul, 2017 2 commits
  2. 08 Jul, 2017 23 commits
  3. 07 Jul, 2017 2 commits
    • Merge pull request #1682 from brauner/2017-07-07/enable_apparmor_namespaces · 996b20c4
      Stéphane Graber authored
      Allow containers to start in AppArmor namespaces
    • Allow containers to start in AppArmor namespaces · d680929b
      Frédéric Dalleau authored
      This patch allows users to start containers in AppArmor namespaces.
      Users can define their own profiles for their containers, but
      lxc-start must be allowed to change to a namespace.
      
      A container configuration file can wrap a container in an AppArmor
      profile using lxc.aa_profile.
      
      A process in an AppArmor namespace is restricted to view
      or manage only the profiles belonging to this namespace, as if no
      other profiles existed. A namespace can be created as follow:
      sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/$NAMESPACE
      
      AppArmor can stack profiles so that the contained process is bound
      by the intersection of all profiles of the stack. This is achieved
      using the '//&' operator as follow:
      
      lxc.aa_profile = $PROFILE//&:$NAMESPACE://unconfined
      
      In this case, even the guest process appears unconfined in the
      namespace, it is still confined by $PROFILE.
      
      A guest allowed to access "/sys/kernel/security/apparmor/** rwklix,"
      will be able to manage its own profile set, while still being
      enclosed in the topmost profile $PROFILE:
      
      Different guests can be assigned the same namespace or different
      namespaces. In the first case, they will share their profiles.
      In the second case, they will have distinct sets of profiles.
      
      This is validated on privileged containers.
      Signed-off-by: 's avatarFrédéric Dalleau <frederic.dalleau@collabora.com>
  4. 06 Jul, 2017 1 commit
  5. 05 Jul, 2017 12 commits