Hello Christian, 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/2107455 Title: segfault of lsblk s390x in containers due to apparmor Status in Ubuntu on IBM z Systems: In Progress 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 ] lsblk would segfault when run from a confined context due to missing permissions on the binary execution path, and the lsblk profile need rules to give m+r permissions for the binaries themselves. One example of where this would occur is if lsblk was run inside a confined container. [ Test Plan ] * Check if apparmor is enabled and the profile active: sudo aa-status --enabled sudo aa-status --show=all | grep lsblk * Add the following to /tmp/allow_all and use `apparmor_parser /tmp/allow_all` to load it as a profile: abi <abi/4.0>, include <tunables/global> profile allow_all { allow all, priority=1 audit /** px, } * Run `aa-exec -p allow_all -- sh -c 'lsblk'` * If a profile for lsblk is not loaded, sh will report a permission denial on the exec transition when attempting to execute lsblk. If this occurs, report verification test failure * Verify that an apparmor="AUDIT" operation="exec" log is generated with the target field showing a transition to an lsblk profile * Verify that the application does not segfault on launch * If application segfaults on launch only when run under confinement, check for apparmor="DENIED" log entry denying read or mmap operations on the binary path, and report verification test failure [ Where problems could occur ] The lsblk profile update loosens confinement on a profile. However, if a user manually modified the installed profile, 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 ] __________ Hey, while debugging bug 2107402 we found that there is more to fix. Running lsblk in a container on s390x hits this: [12064869.934674] audit: type=1400 audit(1744791155.353:111962): apparmor="DENIED" operation="file_mmap" class="file" namespace="root//lxd-p_<var-snap-lxd-common-lxd>" profile="lsblk" name="/usr/bin/lsblk" pid=3286747 comm="lsblk" requested_mask="rm" denied_mask="rm" fsuid=1000000 ouid=1000000 To the user it just segfaults. root@p:~# lsblk Segmentation fault root@p:~# aa-disable lsblk Disabling /usr/bin/lsblk. root@p:~# lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS loop0 7:0 0 93.8M 1 loop loop1 7:1 0 94M 1 l ... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/2107455/+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
