-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jim Fulton wrote:
> Julien Anguenot wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> Regarding the #373 :
>> http://www.zope.org/Collectors/Zope3-dev/373/
>>
>> and the original discussion :
>>  http://mail.zope.org/pipermail/zope3-checkins/2005-February/024307.html
>>
>> Objections to revert to the original solution ?
>> (i.e : *not* allowing DC annotations if the principal doesn't have the
>> 'zope.app.dublincore.change' permission)
> 
> 
> I thought the original soution was to use removeSecurityProxy.

nope this is the current one.

> It is the system that wants to track modification times.  

It's not only about modification time but about creator information as
well in our case and I guess all DC annotations under the same context
would behave the same way.

It's like using the UnrestrictedUser on Zope2 to bypass the security
policy in a way, isn't it ?

> It is the system,
> not the user, that is initiating the DC data change, so the user's
> permissions
> shouldn't really have anything to do with it.  The system can do whatever
> it wants, which we represent via removeSecurityProxy or trusted adapters.

ok I get your point.

If the current solution is fine to you just close the bug.

        J.
- --
Julien Anguenot | Nuxeo R&D (Paris, France)
CPS Platform : http://www.cps-project.org
Zope3 / ECM   : http://www.z3lab.org
mail: anguenot at nuxeo.com; tel: +33 (0) 6 72 57 57 66
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFCuFIRGhoG8MxZ/pIRAtmGAJ9EznZldVkJ2BaUnvWWs287fIPPMACfe5CO
JbAHM5CwH7Ur+MFBh6BtqnA=
=3gR9
-----END PGP SIGNATURE-----
_______________________________________________
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailman/options/zope3-dev/archive%40mail-archive.com

Reply via email to