29 Mar
2010
29 Mar
'10
11:57 a.m.
each securityDecoration owner: self kernel users
anyOne.
each securityDecoration group: self kernel groups anyOne ].
The code above uses #anyOne under the assumption that there is only a
single user, as soon as you have more users this doesn't work anymore.
each securityDecoration owner: self kernel users
anyOne.
each securityDecoration group: self kernel groups anyOne.
each securityDecoration group: self kernel registeredUserGroup.
each securityDecoration group: self kernel projectUserGroup.
each securityDecoration group: self kernel adminUserGroup.
PUSecurity only has one group and one owner, if you call it multiple
times you override the previous setting.
Clearly I've a misunderstanding about how Pier
security is designed to
function. Any pointers gratefully received.
PUSecurity works like file-permissions in Unix. A structure has a
single owner and a single group assigned. Furthermore the allowed
commands can be assigned for each structure to the owner of the
structure, the group of the structure and all other users (anybody
that is not the owner and not within the group). Finally there is a
user-specific flag called 'superuser' that gives all the permissions
in all contexts and avoids any security checks.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch