Regarding the /tmp access-- I'm guessing that TMPDIR is not being set by
the process launching the confined plugin. It can be set to one of the
writable directories in the 1.3.4 policy; I suggest /run/user/$USER
/online-accounts-ui/@{APP_PKGNAME}_@{APP_APPNAME}/ since it is in /run
and will be cleaned on reboot. If you pick this, I'll adjust the policy.-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor-easyprof-ubuntu in Ubuntu. https://bugs.launchpad.net/bugs/1219644 Title: Account plugins should be made confinable by apparmor Status in tools to review click packages: Confirmed Status in Online Accounts setup for Ubuntu Touch: Confirmed Status in apparmor-easyprof-ubuntu package in Ubuntu: Fix Released Status in ubuntu-system-settings-online-accounts package in Ubuntu: Confirmed Bug description: With the current implementation, the QML files for account plugins are executed by the Online Accounts QML applet which in turn is executed within the System Settings process, which probably means that malicious account plugins could control everything that the System Settings process can (like entering/exiting the flight mode). Account plugins (or the Online Accounts applet itself) should probably be run in a separate process, which could then be assigned a stricter confinement with apparmor. To manage notifications about this bug go to: https://bugs.launchpad.net/click-reviewers-tools/+bug/1219644/+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
