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/2110630
Title:
apparmor.d man page contains incorrect information about mount flag
combinations
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 apparmor.d man page contained incorrect information about the
combination of mount options=(list) options in (list), so this
documentation should be fixed, and a test included to ensure that the
documented behavior matches the actual behavior.
[ Test Plan ]
Checking the contents of the man page:
* Open the apparmor.d man page with `man apparmor.d` and scroll down to the
example that starts with `mount options=(ro, atime) options in (nodev, user)`
* Verify that the mount commands listed as matching the rule all include ro
and atime
* The regression test that checks that the behavior is as documented will
run as part of the QRT test suite described below
Verification that the documentation matches the current behavior can be done
via the QRT test suite, which includes execution of the AppArmor test suite via
`ApparmorTestsuites`.
* 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`
[ Where problems could occur ]
The man page update is a documentation-only change. The risk exists
that the new packaged man page could be malformed, but this is
unlikely since the man page is generated by pod2man, and such issues
can be caught during testing by attempting to open the man page after
installation of the new version. The test suite update, which does not
affect the final packaged build, will help ensure that the updated
documentation matches the actual behavior.
[ Other Info ]
This bug was originally reported at
https://gitlab.com/apparmor/apparmor/-/merge_requests/1674.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110630/+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
