Hello Serrano, 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/2111807 Title: Plucky broke fstab sshfs mounts, which depend on fusermount 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: [ Impact ] sshfs mounts specified in /etc/fstab would fail to mount when a mount of all filesystems specified in the fstab was attempted with mount -a. This was due to a missing noexec mount flag specification in the mount rules of fusermount3's profile. [ Test Plan ] * The setup instructions assume no access to an existing SSH client-server pair. - Spin up two Ubuntu Plucky VMs, one of which will be referred to as sshfs-client and the other of which will be referred to as sshfs-server - Run `sudo aa-status` on each machine and verify that a fusermount3 profile is loaded - Install openssh-server on the server and sshfs on the client - Ensure that the two machines are able to ping each other using a [machine hostname].local address - Generate an SSH key on the client and copy it into the ~/.ssh/authorized_keys directory on the server - Ensure that the client can SSH into the server without a password prompt (using the key) - Uncomment the "user_allow_other" line in sshfs-client's /etc/fuse.conf - Create a mountpoint directory somewhere inside sshfs-client's home directory - Verify that a manual sshfs mount using `sshfs -o _netdev,user,idmap=user,transform_symlinks,allow_other,default_permissions,uid=1000,gid=1000 username@sshfs-server:/path/to/directory /home/username/mountpoint` works, and then unmount the newly created mount - Add the entry `username@sshfs-server:/path/to/directory /home/username/mountpoint fuse.sshfs _netdev,user,idmap=user,transform_symlinks,allow_other,default_permissions,uid=1000,gid=1000 0 0` to sshfs-client's /etc/fstab - Attempt to mount the new fstab mount entry with `mount -a` - Without the fix: the mount will fail with a permission denied error and generate an AppArmor log with "failed flags match" - With the fix: the mount should succeed [ Where problems could occur ] Adding the mount flag to the mount rules 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 ] --------Original bug report: My sshfs mounts from /etc/fstab stopped working after upgrading to Plucky. This is the line from my fstab: ``` [email protected]:/datastore/media /media/Media fuse.sshfs _netdev,user,idmap=user,transform_symlinks,port=22,allow_other,default_permissions,uid=1000,gid=1000 0 0 ``` And I uncommented `user_allow_other` in `/etc/fuse.conf`. Usually I'm able to mount this with `mount -a`, or by simply clicking the mount in Gnome Files (Nautilus). But now I get: ``` mount -a fusermount3: mount failed: Permission denied ``` If I add `sudo` to the mount command, I get: ``` sudo mount -a read: Connection reset by peer ``` But strangely, the mount works just fine if I mount using `sshfs`: ``` sshfs -o _netdev,user,idmap=user,transform_symlinks,port=22,allow_other,default_permissions,uid=1000,gid=1000 [email protected]:/datastore/media /media/Media ``` I suspect it has something to do with apparmor, because the following log appears when I attempt a mount via Nautilus: ``` sudo journalctl -xe | grep DENIED mei 27 13:58:51 saibot kernel: audit: type=1400 audit(1748347131.297:5484): apparmor="DENIED" operation="mount" class="mount" info="failed flags match" error=-13 profile="fusermount3" name="/media/Media/" pid=69641 comm="fusermount3" fstype="fuse" srcname="[email protected]:/datastore/media" flags="rw, nosuid, nodev, noexec" ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2111807/+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
