[Zope3-checkins] CVS: Zope3/src/zope/security - readme.txt:1.5

[Chris McDonough]

Update of /cvs-repository/Zope3/src/zope/security
In directory cvs.zope.org:/tmp/cvs-serv5558/src/zope/security

Modified Files:
	readme.txt 
Log Message:
Merge security policy refactoring:

 - Moved all role- and grant-related functionality into
   zope.products.securitypolicy (and out of zope.app.security.grant).
   The zope.products.securitypolicy implementation is exactly
   the same as the old implementation; no changes were made
   to the actual mechanics of role-permission or principal-permission
   grants.  The only real difference is that all functionality
   that is the purview of what we want a security policy to have
   control of is now in that one place.

 - Created new modulealias directive which can be used to provide
   aliases to older modules (to not break existing ZODBs when
   module locations change).

 - Added minor feature: "make debug" launches a debug session in the
   spirit of Zope 2's "zopectl debug".
   


=== Zope3/src/zope/security/readme.txt 1.4 => 1.5 ===
--- Zope3/src/zope/security/readme.txt:1.4	Thu Jul 31 12:50:56 2003
+++ Zope3/src/zope/security/readme.txt	Wed Jan 14 17:55:35 2004
@@ -12,8 +12,7 @@
 
     Principal
 
-     A generalization of a concept of a user.  A principal may be
-     associated with different roles and permissions.
+     A generalization of a concept of a user.
 
     Permission
 
@@ -21,12 +20,6 @@
      WRITE.  Fundamentally the whole security framework is organized
      around checking permissions on objects.
 
-    Roles
-
-     Represents a responsibility of a user in the context of an
-     object.  Roles are associated with the permissions necessary to
-     fulfill the user's responsibility.
-
   Purpose
 
     The security framework's primary purpose is to guard and check
@@ -303,11 +296,10 @@
 
       A Zope3 programmer will never commonly need to interact with the
       low level security framework.  Zope3 defines a second security
-      package over top the low level framework that implements concepts
-      of roles, and authentication sources and checkers are handled
-      via zcml registration.  Still those developing Zope3 will
-      hopefully find this useful as an introduction into the
-      underpinnings of the security framework.
+      package over top the low level framework and authentication
+      sources and checkers are handled via zcml registration.  Still
+      those developing Zope3 will hopefully find this useful as an
+      introduction into the underpinnings of the security framework.
 
     Code