Public bug reported: On Ubuntu Plucky, apparmor utils tools such as aa-notify, aa-logprof, aa-cleanprof cannot parse fusermount3 profile.
$ aa-notify -p skipping unparseable profile /etc/apparmor.d/fusermount3 (Can't parse mount rule mount fstype=fuse options=(nosuid,nodev,rw) revokefs-fuse -> /var/tmp/flatpak-cache-*/**/,) This bug happens because mount rules may include labels as sources, but the existing regex did not permit hyphens, incorrectly marking valid labels like 'revokefs-fuse' as invalid. This bug is fixed in upstream by https://gitlab.com/apparmor/apparmor/-/merge_requests/1565 apparmor-utils version: 4.1.0~beta5-0ubuntu6 ** Affects: apparmor (Ubuntu) Importance: Undecided Status: New -- 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/2101869 Title: apparmor utils tools cannot parse fusermount3 profile Status in apparmor package in Ubuntu: New Bug description: On Ubuntu Plucky, apparmor utils tools such as aa-notify, aa-logprof, aa-cleanprof cannot parse fusermount3 profile. $ aa-notify -p skipping unparseable profile /etc/apparmor.d/fusermount3 (Can't parse mount rule mount fstype=fuse options=(nosuid,nodev,rw) revokefs-fuse -> /var/tmp/flatpak-cache-*/**/,) This bug happens because mount rules may include labels as sources, but the existing regex did not permit hyphens, incorrectly marking valid labels like 'revokefs-fuse' as invalid. This bug is fixed in upstream by https://gitlab.com/apparmor/apparmor/-/merge_requests/1565 apparmor-utils version: 4.1.0~beta5-0ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/2101869/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
