This bug was fixed in the package apparmor - 4.1.0~beta5-0ubuntu14.1
---------------
apparmor (4.1.0~beta5-0ubuntu14.1) plucky; urgency=medium
* This is an SRU from Questing to Plucky, tracked in LP: #2110236
* Add patch to allow unprivileged_userns access to root dir
(LP: #2110616):
- d/p/u/unprivileged_userns_rootdir.patch
* Add patch to fix lsblk accesses on IBM System Z systems (LP: #2107402)
and execution from a confined context (LP: #2107455):
- d/p/u/lsblk-s390-fixes.patch
* Add patch to fix execution of various commands from confined contexts
(LP: #2110628):
- d/p/u/profiles_ensure_access_to_attach_path.patch
* Add patch to include new QtWebEngineProcess execution path in
plasmashell profile (LP: #2107723):
- d/p/u/plasmashell-QtWebEngineProcess-new-path.patch
* Add patch to allow /cvmfs fusermounts (LP: #2110624):
- d/p/u/fusermount3_cvmfs.patch
* Add patch to grant OpenVPN DNS accesses (LP: #2107596, LP: #2109029):
- d/p/u/openvpn_dnsfix.patch
* Add patch to expand allowed fusermount3 flags for fuse_overlayfs and
sshfs via fstab (LP: #2110626, LP: #2111807):
- d/p/u/fusermount3_allow_more_flags.patch
* Add patch to fix permission denials for iotop-c (LP: #2107727):
- d/p/u/profiles-give-iotop-c-additional-accesses.patch
* Add patch to fix parser handling of norelatime mount flag
(LP: #2110688):
- d/p/u/parser-fix-handling-of-norelatime-mount-rule-flag.patch
* Add patch to fix incorrect mount rule documentation in the apparmor.d
man page (LP: #2110630):
- d/p/u/fix-incorrect-mount-flag-apparmor.d-docs.patch
* Add patch to add regression tests for the above two patches:
- d/p/u/regression-verify-documented-mount-flag-behavior.patch
* d/p/u/remmina_mr_1348.patch, d/p/u/remmina-dbus-describeall.patch:
move the remmina profile to profiles/apparmor/profiles/extras to
disable it by default (LP: #2102033)
* debian/apparmor.install: remove the remmina profile entry
* debian/apparmor-profiles.install: add an entry for the remmina profile
* debian/apparmor.maintscript: remove the remmina profile upon upgrade
-- Ryan Lee <[email protected]> Wed, 27 May 2025 11:29:02 -0700
** Changed in: apparmor (Ubuntu Plucky)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/2110688
Title:
apparmor parser incorrectly treats norelatime mount flag as a no-op
Status in apparmor package in Ubuntu:
Fix Released
Status in apparmor source package in Plucky:
Fix Released
Status in apparmor source package in Questing:
Fix Released
Bug description:
[ Impact ]
The parser did not handle the norelatime mount flag correctly,
essentially treating its addition to a list of mount flags as a no-op.
A test should also be included to ensure that the behavior is fixed
and not broken again.
[ Test Plan ]
This bug is caught by an addition to AppArmor's regression test suite,
which is also invoked via its QRT test suite via
`ApparmorTestsuites.test_regression_testsuite`.
* To prepare the QRT test suite (can be done on any machine):
- `git clone https://git.launchpad.net/qa-regression-testing`
- `./scripts/make-test-tarball ./scripts/test-apparmor.py`
* To run the QRT test suite:
- Copy the tarball onto the machine with the new AppArmor installed and
extract it
- `sudo ./install-packages test-apparmor.py`
- Reboot the machine
- `sudo ./test-apparmor.py -v`
Unfortunately, the regression testsuite itself has no way of printing
the full list of tests it successfully executed. Below are
instructions for running the regression test suite by hand, including
the modified mount test:
* `apt install dpkg-dev pkg-config libapparmor-dev`
* `apt-get source apparmor`
* Verify that the downloaded version is 4.1.0~beta5-0ubuntu14.1 or greater
* Verify that patch
debian/patches/ubuntu/regression-verify-documented-mount-flag-behavior.patch
was applied upon download
* cd [source]/tests/regression/apparmor
* Ensure that all the parent directories of the regression test folder are
world-readable and world-executable, and 'chmod o+rx' any that are not
* USE_SYSTEM=1 make -j[num]
* If running the whole regression testsuite, the `make` command might print
out warnings about skipped tests due to missing packages. Install any packages
that it says are missing
* If running the whole regression testsuite, 'sudo USE_SYSTEM=1 make tests'
* If running just the mount tests, 'sudo USE_SYSTEM=1 bash mount.sh' and
manually 'echo $?' afterwards to check that it exited with a status of 0
[ Where problems could occur ]
This parser fix changes the behavior of mount rules that explicitly
specify the norelatime flag. In particular, a custom profile
containing `mount options in (norelatime)` will have different, more
permissive behavior than before (reducing regression risk as compared
to tightening behavior). However, this flag is not used in any of the
commonly used profiles (including the ones in our repo and the profile
fragments used by snapd), so this will not change the behavior of
existing packaged profiles being used.
[ Other Info ]
This bug was originally reported at
https://gitlab.com/apparmor/apparmor/-/merge_requests/1679.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110688/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
