Skip to content

AppArmor 3.0.4 was released 2022-02-09.

Introduction

AppArmor 3.0.4 fixes a build error in AppArmor 3.0.3 that could cause AppArmor builds to fail during tests in some build environments. It is a maintenance release of the user space components of the AppArmor security project. The kernel portion of the project is maintained and pushed separately.

This version of the userspace should work with all kernel versions from 2.6.15 and later (some earlier version of the kernel if they have the apparmor patches applied).

The kernel portion of the project is maintained and pushed separately.

Notes

  • while Link Time Optimization (LTO) has been fixed for some systems there are still some known issues which may result in build failures on some systems. See https://gitlab.com/apparmor/apparmor/-/issues/214

Obtaining the Release

There are two ways to obtain this release either through gitlab or a tarball in launchpad.

Important note: the gitlab release tarballs differ from the launchpad release tarballs. The launchpad release tarball has a couple processing steps already performed:

  • libapparmor autogen.sh is already done, meaning distros only need to use ./configure in their build setup
  • the docs for everything but libapparmor have already been built

gitlab

  • https://gitlab.com/apparmor/apparmor/-/releases/v3.0.4

Launchpad

Changes in this Release

These release notes cover all changes between 3.0.3 (1a6c042ac608a6fd2111bd3338d3dca1529a33f9) and 3.0.4 (939530b2b89ee26bef52ccfe3d271629f4da097d) apparmor-3.0 branch.

Init

  • make xargs invocation busybox-compatible (MR:828)

Library

Policy Compiler (a.k.a apparmor_parser)

  • Fix unknown state condition in RLIMIT rule parsing (MR:803)
  • Ensure new af_names are supported (MR:808, AABUG:195)
  • add support for mctp address family (MR:832)

Utils

  • add support for new and future python versions (MR:795, AABUG:193)

  • add support for mctp address family (MR:832)

  • aa-notify

  • Avoid aa-notify crash on log events without operation= (MR:797, Fixes: AABUG:194)
  • support reading s390x and aarch64 wtmp files (MR:809, BOO:1181155)
  • aa-unconfined
  • Improve fallback handling to attr/current (MR:801, AABUG:199)
  • aa-features-abi
  • Fix handling of -f option (MR:804)
  • Fix fd resource leak (MR:804)
  • aa-status
  • fix crash due to \n in profile name (MR:824, AABUG:211)

Policy

abstractions

profiles

  • avahi-daemon
  • Add missing /proc permissions (MR:811, AABUG:203)
  • chrome
  • fix opening links (https://gitlab.com/apparmor/apparmor/-/merge_requests/830)
  • dnsmasq
  • add support for podman dnsname plugin (MR:800, BOO:1190271)
  • samba
  • Add profile for samba-bgqd (BOO:1191532, MR:807)
  • samba-bgqd
  • fix mmap violation (MR:819)

Additional Note

There is a semantic change in the 4.8 kernel (commit 9f834ec18defc369d73ccf9e87a2790bfa05bf46) that affects apparmor policy enforcement. Specifically it affects when the m permission bit is checked for elf binary executables. Policy and tests within apparmor 2.12 and later have been updated to support running on pre 4.8 and 4.8+ kernels.