AW: Recursive operations and authz

Hi, Daniel,

> Von: Daniel Shahaf [mailto:d.s_at_daniel.shahaf.name]
> Stefan Fuhrmann wrote on Wed, May 13, 2015 at 08:21:37 +0200:
> > Hi devs,
> >
> > [...]
> >
> > (1) Is there something fundamentally wrong with this
> > approach, e.g. braking major use-cases?
>
> How about inventing a 'c' permission, in addition to the existing 'r'
> and 'rw', with the following semantics: if the authz file contains
> '[/tags] alice=c', then alice is authorized to create immediate
> children of /tags, possibly as adds-with-history, without needing
> recursive write access to the copy destination. Would this address
> your use-case?

I like the general suggestion, but 'c' made me immediately think 'copy',
which could be the right to copy the tree to somewhere else.

Thus, I suggest 'a' for 'add', the right to add children (including their subtrees).

If this right is non-recursive, people may add files, directories or whole trees (in the same transaction), but not modify them later.
 

Best regards

Markus Schaber

CODESYS(r) a trademark of 3S-Smart Software Solutions GmbH

Inspiring Automation Solutions

3S-Smart Software Solutions GmbH
Dipl.-Inf. Markus Schaber | Product Development Core Technology
Memminger Str. 151 | 87439 Kempten | Germany
Tel. +49-831-54031-979 | Fax +49-831-54031-50

E-Mail: m.schaber@codesys.com | Web: http://www.codesys.com | CODESYS store: http://store.codesys.com
CODESYS forum: http://forum.codesys.com

Managing Directors: Dipl.Inf. Dieter Hess, Dipl.Inf. Manfred Werner | Trade register: Kempten HRB 6186 | Tax ID No.: DE 167014915

This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received
this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure
or distribution of the material in this e-mail is strictly forbidden.
Received on 2015-05-13 12:19:42 CEST