-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 21/01/2004, at 12:54 PM, Stuart Bishop wrote:
I think I've tracked down a minimal example, the trigger being my use of __allow_access_to_unprotected_subobjects__ = None. I'm thinking this recent change is incompatible if a parent object tightens security in this way or uses security.setDefaultAccess('deny'). The work around is to explicity grant access to the name '' as I've done in the attached example.
Should policy.validate(name='') be changed to cope with this
situation, or shall I update CHANGES.txt and
ClassSecurityInfo.setDefaultAccess attempting to explain the situation and
the fix?
I've opened this up as an issue on the collector: http://collector.zope.org/Zope/1202
I've so far seen one other report on the main Zope mailing list.
- -- Stuart Bishop <[EMAIL PROTECTED]>
http://www.stuartbishop.net/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)
iD8DBQFAEb/5AfqZj7rGN0oRAt/IAKCMG8wXYX3niyJ24phTqHOIm21qyQCdEdSN /SxsrihaAm7Yn6pog+exdN0= =wjUk -----END PGP SIGNATURE-----
_______________________________________________
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
