On Thu, Jun 10, 2010 at 5:41 PM, Janne Karhunen <[email protected]>wrote:
> On Thu, Jun 10, 2010 at 3:24 PM, Shaz <[email protected]> wrote: > > >> Effective bits in access control are quite simple and similar to > >> SMACK. Check the linux-security-module discussion for starters. > >> The 'real' difference between smack and this is that we support > >> multiple task labels and the fact that we don't allow the task to > >> change it's own security context. > > > > Multiple task labels for multiple role assignment I guess ...? > > In our case label does not really identify a task, it identifies > a function task is allowed to perform on remote server. Each > task can have any number of detailed rights assigned. > > A use-case/example will help because it is not making sense to me. Do you maintain the rights on the client platform? Or you let the server side handle it in a distributed way among more than one server sides in the context of a resource on the client platform? -- Shaz
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
