Hello Ryan, or anyone else affected, Accepted apparmor into plucky-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/apparmor/4.1.0~beta5-0ubuntu14.1 in a few hours, and then in the -proposed repository.
Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- plucky to verification-done-plucky. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-plucky. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: apparmor (Ubuntu Plucky) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-plucky -- 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 Committed 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
