On 2014-11-20 11:07, José Bollo wrote: > Le jeudi 20 novembre 2014 à 10:12 +0100, Tomasz Swierczek a écrit : >> Okay, so if this is the usecase, then we need to have, like I mentioned, the >> mv_chmod_chown() API in security-server PLUS some way of authorizing this >> action (ie. guard it with http://tizen.org/privilege/system like it was >> proposed or some other, more precise privilege, allowed only for >> system-level things). > Hi all, > > Tomasz, you wrote mv_chmod_chown but it should be > copy_remove_move_create_chmod_chown_chsmack. > > I agreed that the use of this interface have to be authorized. Using > privilege is good. A more precise privilege that > http://tizen.org/privilege/system would be better but there is a > compromise to found to not increase the count of privileges. However, > I'm thinking that the chosen privilege should be of level partner.
We could introduce an internal privilegeto guard this functionality of security-manager. However you should remember that all services run with the same Smack label, so the privilege would have to begranted based on bluetooth service uid. _______________________________________________ Dev mailing list [email protected] https://lists.tizen.org/listinfo/dev
