Le jeudi 27 novembre 2014 à 10:18 +0100, Rafał Krypa a écrit :
> On 2014-11-26 14:09, Manuel Bachmann wrote:
> 
> > Hi folks,
> > 
> > 
> > This RFC is about bug TC-1691, TC-159...
> > 
> > 
> > 
> > (The problem happens with Crosswalk today, but it could happen with
> > any other application)
> > 
> > 
> > AUL provide somes function calls, like  "aul_app_get_pkgname_bypid
> > ()", which permit to get the application package name associated
> > with a running PID.
> > 
> > 
> > Under IVI, the ICO Homescreen (profile/ivi/ico-uxf-homescreen) uses
> > these calls to determine if it should show a window, by getting the
> > PID of its process, and then comparing it will the package name. If
> > if does not match, the window stays hidden.
> > 
> 
> Hi Manuel,
> Please clarify one thing: do you need to retrieve package name (a.k.a.
> pkgId) or application name (appId)? What if there are multiple
> applications in a package?

aul is also in progress so Manuel is investigating using the current
state. It may explain.

> During last security workshop in Vannes in October, a requirement was
> formulated that AUL needs to identify application processes by
> fetching appId from a running process. I'd like to know if this
> requirement is still valid. To implement it, I had to redesign Smack
> labeling for applications in security-manager to be based on appId
> instead of pkgId. This is still work in progress and it complicates
> matters for security-manager. If for any reason this is not needed
> anymore, I would be happy to go back to the old labeling scheme.

I'm not aware that decision taken in October is reverted. So I can not
answer. Do you want to reopen the discussion on the topic "how to label
applications by there package id or by their application id?".

Best regards
José

> 
> 
> Best regards,
> Rafal Krypa
> _______________________________________________
> Dev mailing list
> [email protected]
> https://lists.tizen.org/listinfo/dev


_______________________________________________
Dev mailing list
[email protected]
https://lists.tizen.org/listinfo/dev

Reply via email to