The verification of the Stable Release Update for apparmor has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.
-- 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/2110624 Title: apparmor fusermount3 profile blocks mounts to /cvmfs/ subdirectories 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: SRU Justification: [ Impact ] fusermount3 lacked permissions to mount to /cvmfs subdirectories, breaking usage of the CernVM FS. [ Test Plan ] * Run `sudo aa-status` and verify that a fusermount3 profile is loaded * The following instructions are adapted from https://cvmfs.readthedocs.io/en/stable/cpt-quickstart.html - Install the cvmfs packages + `wget https://cvmrepo.s3.cern.ch/cvmrepo/apt/cvmfs-release-latest_all.deb` + `sudo dpkg -i cvmfs-release-latest_all.deb` + `sudo apt-get -y update` + `sudo apt-get -y install cvmfs` - Set up autofs configs by running `sudo cvmfs_config setup` and `sudo systemctl restart autofs` - Create `/etc/cvmfs/default.local` and add the lines "CVMFS_REPOSITORIES=cvmfs-config.cern.ch", "CVMFS_CLIENT_PROFILE=single" to it - Attempt to mount by running `cvmfs_config probe` * Without the fix: - The mount step fails with a permission denial error - AppArmor generates denial logs for fusermount3 denying the mount syscall * With the fix: the mount should succeed with no AppArmor logs being generated [ Where problems could occur ] Adding a rule to allow mounting to /cvmfs subdirectories loosens confinement on a profile. However, if a user manually modified the installed profiles, then the package upgrade would cause conflicts, and rejection of the incoming changes (either by hand during an interactive upgrade or automatically during an batch unattended upgrade) would result in end users not getting the packaged fix. [ Other Info ] This bug was originally reported at https://gitlab.com/apparmor/apparmor/-/merge_requests/1587. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2110624/+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
