[Zope-Checkins] CVS: Zope3/lib/python/Zope/App/OFS/Folder - folder.zcml:1.1.2.9.4.1

[Jim Fulton]

Update of /cvs-repository/Zope3/lib/python/Zope/App/OFS/Folder
In directory cvs.zope.org:/tmp/cvs-serv26931/lib/python/Zope/App/OFS/Folder

Modified Files:
      Tag: SecurityProxy-branch
	folder.zcml 
Log Message:
Moved security management modules to Zope.Security.

Added like_unto attribute to protect class so you can say that a class
has the same protections as another class::

  <security:protectClass name=".RootFolder." like_unto=".Folder." />

Added some additional calls to removeAllProxies in some component
lookup code while debugging integration of new security model.

Added protections for BTree types.


=== Zope3/lib/python/Zope/App/OFS/Folder/folder.zcml 1.1.2.9 => 1.1.2.9.4.1 ===
   <security:protectClass name=".Folder."
                          permission_id="Zope.View">
-    <security:instances permission_id="Zope.View" />
     <security:protect 
               interface="Zope.ComponentArchitecture.IServiceManagerContainer." 
   	      permission_id="Zope.ManageServices" />
+    <security:protect
+              interface="Zope.App.OFS.Container.IContainer.IReadContainer"
+              permission_id="Zope.View" />
+    <security:protect
+              interface="Zope.App.OFS.Container.IContainer.IWriteContainer"
+              permission_id="Zope.ManageContent" />
   </security:protectClass>
 
+  <!-- XXX Do we really need RootFolder? -->
+  <security:protectClass name=".RootFolder." like_unto=".Folder." /> 
+
   <zmi:tabs for=".Folder.IFolder.">
     <zmi:tab label="Contents" action="contents;view"/>
     <zmi:tab label="Role Permissions" 
@@ -37,7 +45,6 @@
 
   <security:protectClass name=".LoadedFolder."
                          permission_id="Zope.View">
-    <security:instances permission_id="Zope.View" />
   </security:protectClass>
 
   <zmi:tabs for="Zope.App.OFS.Container.IContainerLimit.">