Right, that's what I was saying. The services expose specific endpoints, and the click package needs to specify the apparmor profile for that service; ie, the "accounts" profile.
On Fri, 2014-10-03 at 12:26 -0300, Roberto Alsina wrote: > Click apps can't ask for specific dbus endpoints. They request > specific "profiles". There needs to be a new profile that allows this > specific endpoint and it has to be shipped and it has to appear in the > sdk's list of profiles. > > On Fri, Oct 3, 2014 at 11:53 AM, Rodney Dawes > <rodney.da...@canonical.com> wrote: > On Fri, 2014-10-03 at 08:41 -0400, Chris Wayne wrote: > > > > > > > We can't do a D-Bus call from a click package scope anyway > can we? I > > think dbus was explictly denied by AppArmor > > > > If the API endpoint you're accessing is explicitly allowed, > and the > click package has the necessary value to state it wants to use > that API > in the apparmor.json for it, then I think it will work. That > was my > understanding of how dbus will be confined by apparmor anyway. > > > > > -- > 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 > > > -- 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
