[rum-discuss] Security Policy

0 views
Skip to first unread message

Michael Brickenstein

unread,
Apr 27, 2010, 6:07:51 AM4/27/10
to rum-discuss
Hi!

I seperated the Alberto's ingenious security policy class from the RUM
project in a separate repository.

You can some use of the policy in RUM here:

http://hg.python-rum.org/TgRumDemo/file/f9bcdb0540c2/tgrumdemo/policy.py#l1

It allows per column and per row permissions, works flexible with
patterns.
You can choose, if you specify the Resource and or action...

I do not have the time to write much more. But it is really cool.
Of course, it is implemented in peak.rules, but that's just the fast
engine which deals with type implications and there is really no need
for average applications to go down to that level. It is really great
(design by Alberto), like ACLs but far more flexible.

The policy repository is on bitbucket.

http://bitbucket.org/brickenstein/rum-policy

Cheers,
Michael

--
You received this message because you are subscribed to the Google Groups "rum-discuss" group.
To post to this group, send email to rum-d...@googlegroups.com.
To unsubscribe from this group, send email to rum-discuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/rum-discuss?hl=en.

Alberto Valverde

unread,
Apr 28, 2010, 4:17:55 AM4/28/10
to rum-d...@googlegroups.com
Hi Michael,

Great stuff! Please feel free to modify Rum so it depends on these parts
you're extracting (if you haven't already) instead of the local
implementation so we don't have twice the maintenance work.

On 4/27/10 12:07 PM, Michael Brickenstein wrote:
> Hi!
>
> I seperated the Alberto's ingenious security policy class from the RUM
> project in a separate repository.
>
> You can some use of the policy in RUM here:
>
> http://hg.python-rum.org/TgRumDemo/file/f9bcdb0540c2/tgrumdemo/policy.py#l1
>
> It allows per column and per row permissions, works flexible with
> patterns.
> You can choose, if you specify the Resource and or action...
>
> I do not have the time to write much more. But it is really cool.
> Of course, it is implemented in peak.rules, but that's just the fast
> engine which deals with type implications and there is really no need
> for average applications to go down to that level. It is really great
> (design by Alberto), like ACLs but far more flexible.
>

To be fair, rum's dec. policy design is heavily inspired on (if not an
outright cheapo clone-of!) peak.security, so all compliments belong to it ;)

Thanks!

Alberto

Michael Brickenstein

unread,
Apr 28, 2010, 4:52:21 AM4/28/10
to rum-d...@googlegroups.com
Hi Alberto!

Thanks for your nice feedback.
Am 28.04.2010 um 10:17 schrieb Alberto Valverde:

> Hi Michael,
>
> Great stuff! Please feel free to modify Rum so it depends on these parts you're extracting (if you haven't already) instead of the local implementation so we don't have twice the maintenance work.

I already did so. My main intention is making our gems available to others :-), going the Zope, repoze way instead of the Django way.
Reply all
Reply to author
Forward
0 new messages