On 02/03/2014 03:10 PM, Michał Sawicz wrote: > On 03.02.2014 17:44, Jamie Strandboge wrote: >> At this point, I think I would suggest just using aa-exec-click, but note by >> doing so it will not be under application lifecycle since it is isn't running >> under upstart. I'm not sure how much of a concern this is. It is conceivable >> app >> authors could abuse this to start long running processes, so this is perhaps >> not >> the best choice. Maybe upstart-app-launch should be adjusted to assist online >> accounts? I'll let others comment on that. > > The whole trusted session will be considered for a single lifecycle "group" > with > the original app, so yes it will be put under lifecycle management regardless > of > how it's launched. > Is this true? Doesn't the untrusted app call out to the trusted online accounts which is not part of this lifecycle group, and then online accounts calls the plugin? The unconfined app talks to online accounts over DBus; I'm not sure how online accounts would fall under the apps lifecycle group in this case.
> That said, having upstart manage those would definitely help, having to track > the PID is not something we'd like to do. I don't think you'll need more than > one instance of the plugin? In that case a simple .desktop file with > NoShow=True > (or whatever the right syntax is) would be enough to get it going under > upstart-app-launch. -- Jamie Strandboge http://www.ubuntu.com/
signature.asc
Description: OpenPGP digital signature
-- Mailing list: https://launchpad.net/~ubuntu-phone Post to : ubuntu-phone@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-phone More help : https://help.launchpad.net/ListHelp
