Metadata-Version: 1.0
Name: z3c.securitytool
Version: 0.4.1
Summary: A security audit tool and demo for Zope3 views
Home-page: UNKNOWN
Author: Daniel Blackburn, Stephan Richter, Randy Crafton
Author-email: zope-dev@zope.org
License: ZPL 2.1
Description: ================
        z3c.securitytool
        ================
        
        z3c.securitytool is a Zope3 package aimed at providing component level
        security information to assist in analyzing security problems and to
        potentially expose weaknesses. The goal of the security tool is to
        provide a matrix of users and their effective permissions for all available
        views for any given component and context. We also provide two further
        levels of detail. You can view the details of how a user came to have
        the permission on a given view, by clicking on the permission in the matrix.
        
        .. image::
        http://farm3.static.flickr.com/2318/2521732872_81a709e3db_m.jpg
        :height: 200
        :width: 400
        :target: http://flickr.com/photos/blackburnd/
        
        =================
        Demo Instructions
        =================
        
        You can run the demo by downloading just the securitytool package
        
        - ``# svn co svn://svn.zope.org/repos/main/z3c.securitytool/trunk securitytool``
        - ``# cd securitytool``
        - ``# python bootstrap.py``
        - ``# ./bin/buildout``
        - ``# ./bin/demo fg``
        
        Then access the demo site using:
        
        - http://localhost:8080/++skin++SecurityTool/securityMatrix.html
        - user: admin
        - password: admin
        
        There are some folders added with permissions and roles applied to show
        the settings in the demo.
        
        - http://localhost:8080/++skin++SecurityTool/Folder1/securityMatrix.html
        - http://localhost:8080/++skin++SecurityTool/Folder1/Folder2/securityMatrix.html
        
        These permissions should mirror what you see in the @@grant.html views
        
        - http://localhost:8080/Folder1/Folder2/@@grant.html
        - http://localhost:8080/Folder1/@@grant.html
        
        ``(These settings are  added when the database is first opened``
        ``You can find these settings in demoSetup.py)``
        
        
        ==============================================
        How to use the securityTool with your project:
        ==============================================
        Remember this is a work in progress.
        
        1. Add the z3c.securitytool to your install_requires in your
        setup.py.
        2. Add the &lt;include package="z3c.securitytool"/&gt; to your site.zcml
        3. Use the skin `++skin++SecurityTool` to access securityTool pages
        4. Append @@securityMatrix.html view to any context to view the permission
        matrix for that context using the security tool skin.
        
        For example:
        http://localhost:8080/++skin++SecurityTool/Folder1/@@securityMatrix.html
        
        
        
        
        
        ======================
        Detailed Documentation
        ======================
        
        On the main  page of the securityTool you will be able to select
        the desired skin from all the available skins on the system.
        On initial load of the securitytool you will only see permissions
        for IBrowserRequest and your current context. The interesting
        information is when you select the skins. A future release of
        this tool will offer a selection to view  all information for all
        skins as well as each skin individually. You can also truncate the
        results by selecting the permission from the filter select box.
        When you click on the "Allow" or "Deny" security tool will explain
        where these permissions were specified whether by role, group, or
        in local context.
        
        When you click on a user-name all the permissions inherited from
        roles, groups or specifically assigned permissions will be displayed.
        
        &gt;&gt;&gt; import zope
        &gt;&gt;&gt; from zope.app import zapi
        &gt;&gt;&gt; from pprint import pprint
        &gt;&gt;&gt; from zope.interface import providedBy
        &gt;&gt;&gt; from z3c.securitytool.securitytool import *
        &gt;&gt;&gt; from z3c.securitytool.interfaces import ISecurityChecker
        &gt;&gt;&gt; from z3c.securitytool.interfaces import IPrincipalDetails
        &gt;&gt;&gt; from z3c.securitytool.interfaces import IPermissionDetails
        &gt;&gt;&gt; from z3c.securitytool.browser import ISecurityToolSkin
        &gt;&gt;&gt; root = getRootFolder()
        
        Several things are added to the database on the IDatabaseOpenedEvent when
        starting the demo or running the tests. These settings are used to test
        the functionality in the tests as well as populate a matrix for the demo.
        Lets make sure the items were added with demoSetup.py, We will assume
        that if Folder1 exists in the root folder then demoSetup.py was executed.
        
        &gt;&gt;&gt; sorted(root.keys())
        [u'Folder1']
        
        To retrieve the permission settings for the folder we must first adapt the
        context to a SecurityChecker Object.
        
        &gt;&gt;&gt; folder1 = ISecurityChecker(root['Folder1'])
        
        &gt;&gt;&gt; print folder1.__class__.__name__
        SecurityChecker
        
        Lets introspect the object.
        
        &gt;&gt;&gt; pprint(dir(folder1))
        ['__class__',
        '__component_adapts__',
        ...
        'aggregateMatrices',
        'context',
        'getPermissionSettingsForAllViews',
        'getReadPerm',
        'populateMatrix',
        'populatePermissionMatrix',
        'populateViewRoleMatrix']
        
        
        To get all the security settings for particular context level the
        getPermissionSettingsForAllViews is called with a tuple of interfaces.
        All the views registered for the interfaces passed will be inspected.
        
        Since nothing should be registered for only zope.interface.Interface we
        should receive an empty set, of permissions, roles and groups.
        
        &gt;&gt;&gt; folder1.getPermissionSettingsForAllViews(zope.interface.Interface)
        [{}, {}, set([])]
        
        A realistic test would be to get all the interfaces provided by a specific
        context level like `Folder1`. Being a folder these are the interfaces as you
        might expect.
        
        &gt;&gt;&gt; ifaces = tuple(providedBy(root['Folder1']))
        &gt;&gt;&gt; pprint(ifaces)
        (&lt;InterfaceClass zope.app.folder.interfaces.IFolder&gt;,
        &lt;InterfaceClass persistent.interfaces.IPersistent&gt;,
        &lt;InterfaceClass zope.location.interfaces.IPossibleSite&gt;,
        &lt;InterfaceClass zope.app.container.interfaces.IContained&gt;)
        
        The next step to determine security levels is the getViews function.
        `getViews` gets all the registered views for this interface. This
        is refined later to the views that are only accessible in this context.
        
        &gt;&gt;&gt; pprint(sorted([x for x in getViews(ifaces[0])]))
        [AdapterRegistration... ITraversable, u'acquire', ...
        AdapterRegistration... ITraversable, u'adapter', ...
        AdapterRegistration... ITraversable, u'attribute', ...
        AdapterRegistration... ITraversable, u'etc', ...
        AdapterRegistration... ITraversable, u'item', ...
        AdapterRegistration... ITraversable, u'lang', ...
        AdapterRegistration... ITraversable, u'resource', ...
        AdapterRegistration... ITraversable, u'skin', ...
        AdapterRegistration... ITraversable, u'vh', ...
        AdapterRegistration... ITraversable, u'view', ...
        
        
        Since this is a large result set returned we will only test enough
        pieces of the results to inform of the desired behavior and to make sure
        the results are sane.
        
        &gt;&gt;&gt; permDetails = folder1.getPermissionSettingsForAllViews(ifaces,
        ...                                                     ISecurityToolSkin)
        
        By using the ISecurityToolSkin we can see the actual securityTool
        views. The securityTool views are only registered for the
        ISecurityToolSkin layer.
        
        &gt;&gt;&gt; pprint(permDetails)
        [...
        'zope.globalmgr': {u'&lt;i&gt;no name&lt;/i&gt;': 'Allow',
        u'DELETE': 'Allow',
        u'OPTIONS': 'Allow',
        u'PUT': 'Allow',
        u'absolute_url': 'Allow',
        u'permissionDetails.html': 'Allow',
        u'principalDetails.html': 'Allow',
        u'securityMatrix.html': 'Allow'},
        ...]
        
        As you can see below the `zope.anybody` has the 'Allow' permission
        for the four views listed below. The securitytool views are not listed
        here because they are neither specifically denied or allowed for
        this principal.
        
        &gt;&gt;&gt; pprint(permDetails)
        ...
        [{'zope.anybody': {u'&lt;i&gt;no name&lt;/i&gt;': 'Allow',
        u'DELETE': 'Allow',
        u'OPTIONS': 'Allow',
        u'PUT': 'Allow',
        u'absolute_url': 'Allow'},
        ...
        
        Another section of the result set shows all valid views for this
        context and skin, along with the permission required for access to
        the view.
        
        &gt;&gt;&gt; pprint(permDetails)
        [...
        {u'&lt;i&gt;no name&lt;/i&gt;': 'zope.Public',
        u'DELETE': 'zope.Public',
        u'OPTIONS': 'zope.Public',
        u'PUT': 'zope.Public',
        u'absolute_url': 'zope.Public',
        u'permissionDetails.html': 'zope.ManageContent',
        u'principalDetails.html': 'zope.ManageContent',
        u'securityMatrix.html': 'zope.ManageContent'},
        ...]
        
        All the principals in the system  are in this data structure.
        Here we just print a subset of the structure, to make sure the
        data is sane.
        
        &gt;&gt;&gt; pprint(sorted(permDetails[0].keys()))
        ['zope.anybody',
        'zope.daniel',
        'zope.globalmgr',
        'zope.group1',
        'zope.markus',
        'zope.martin',
        'zope.mgr',
        'zope.randy',
        'zope.sample_manager',
        'zope.stephan']
        
        This of course should be identical to the users on the system from
        zapi.getPrincipals() without (zope.anybody)
        
        &gt;&gt;&gt; from zope.app import zapi
        &gt;&gt;&gt; sysPrincipals = zapi.principals()
        &gt;&gt;&gt; principals = [x.id for x in sysPrincipals.getPrincipals('')]
        &gt;&gt;&gt; pprint(sorted(principals))
        ['zope.daniel',
        'zope.globalmgr',
        'zope.group1',
        'zope.group2',
        'zope.markus',
        'zope.martin',
        'zope.mgr',
        'zope.randy',
        'zope.sample_manager',
        'zope.stephan']
        
        ========================================
        Using securitytool to inspect principals
        ========================================
        
        Lets see what the principalDetails look like for the principal Daniel
        and the context of 'Folder1'.
        
        First we retrieve the principalDetails for Folder1:
        
        &gt;&gt;&gt; prinDetails = PrincipalDetails(root[u'Folder1'])
        
        Then we filter out the uninteresting information for the user
        being inspected.
        
        &gt;&gt;&gt; matrix = prinDetails('zope.daniel')
        
        The principal details structure contains five interesting pieces of data.
        
        &gt;&gt;&gt; pprint(sorted(matrix.keys()))
        ['groups', 'permissionTree', 'permissions', 'roleTree', 'roles']
        
        Below we check to make sure the groups data structure from the user daniel
        is returned as expected. This is the data used to populate the groups
        section on the User Details page.
        
        &gt;&gt;&gt; pprint(matrix['groups'].keys())
        ['zope.randy']
        
        The permission tree is used to display the levels of inheritance that were
        traversed to attain the permission displayed. The permission is
        stored as a list so the order is maintained. (yes I know there are
        better ways to accomplish this)
        
        &gt;&gt;&gt; pprint(matrix['permissionTree'][0])
        {u'Folder1_2': {'name': None,
        'parentList': [u'Folder1', 'Root Folder'],
        'permissions': [{'permission': 'concord.CreateArticle',
        'principal': 'zope.daniel',
        'setting': PermissionSetting: Allow},
        {'permission': 'concord.ReadIssue',
        'principal': 'zope.daniel',
        'setting': PermissionSetting: Deny},
        {'permission': 'concord.DeleteIssue',
        'principal': 'zope.daniel',
        'setting': PermissionSetting: Allow}]}}
        
        
        &gt;&gt;&gt; pprint(matrix['permissionTree'][1])
        {'Root Folder': {'name': 'Root Folder',
        'parentList': ['Root Folder'],
        'permissions': [{'permission': 'concord.DeleteArticle',
        'principal': 'zope.daniel',
        'setting': PermissionSetting: Deny},
        {'permission': 'concord.CreateArticle',
        'principal': 'zope.daniel',
        'setting': PermissionSetting: Deny},
        {'permission': 'concord.ReadIssue',
        'principal': 'zope.daniel',
        'setting': PermissionSetting: Allow}]}}
        
        
        The permissions section of the matrix displays the final say on
        whether or not the user has permissions at this context level.
        
        &gt;&gt;&gt; pprint(matrix['permissions'])
        [{'setting': PermissionSetting: Allow, 'permission': 'concord.CreateArticle'},
        {'setting': PermissionSetting: Deny, 'permission': 'concord.ReadIssue'},
        {'setting': PermissionSetting: Allow, 'permission': 'concord.DeleteIssue'},
        {'setting': PermissionSetting: Deny, 'permission': 'concord.DeleteArticle'},
        {'setting': PermissionSetting: Allow, 'permission': 'concord.CreateIssue'},
        {'setting': PermissionSetting: Allow, 'permission': 'concord.PublishIssue'}]
        
        The roleTree structure is used to display the roles attained at
        each level of traversal. The roleTree is stored as a list so to
        consistently test the data properly we will create a dictionary
        out of it and is similar in function to the permissionTree.
        
        &gt;&gt;&gt; tmpDict = {}
        &gt;&gt;&gt; keys = matrix['roleTree']
        &gt;&gt;&gt; for item in matrix['roleTree']:
        ...     tmpDict.update(item)
        
        &gt;&gt;&gt; pprint(tmpDict['Root Folder'])
        {'name': 'Root Folder',
        'parentList': ['Root Folder'],
        'roles': [{'principal': 'zope.daniel',
        'role': 'zope.Writer',
        'setting': PermissionSetting: Allow}]}
        
        &gt;&gt;&gt; pprint(tmpDict['Folder1_2'])
        {'name': None,
        'parentList': [u'Folder1', 'Root Folder'],
        'roles': [{'principal': 'zope.daniel',
        'role': 'zope.Writer',
        'setting': PermissionSetting: Allow}]}
        
        &gt;&gt;&gt; pprint(tmpDict['global settings'])
        {'name': None,
        'parentList': ['global settings'],
        'roles': [{'principal': 'zope.daniel',
        'role': 'zope.Janitor',
        'setting': PermissionSetting: Allow}]}
        
        The roles section of the matrix displays the final say on whether or
        not the user has the role assigned at this context level.
        
        &gt;&gt;&gt; pprint(matrix['roles'])
        {'zope.Janitor': [{'setting': 'Allow', 'permission': 'concord.ReadIssue'}],
        'zope.Writer':  [{'setting': 'Allow', 'permission': 'concord.DeleteArticle'},
        {'setting': 'Allow', 'permission': 'concord.CreateArticle'},
        {'setting': 'Allow', 'permission': 'concord.ReadIssue'}]}
        
        
        Now lets see what the permission details returns
        
        &gt;&gt;&gt; from zope.publisher.interfaces.browser import IBrowserRequest
        &gt;&gt;&gt; from z3c.securitytool.interfaces import IPermissionDetails
        &gt;&gt;&gt; permAdapter = zapi.getMultiAdapter((root[u'Folder1'],
        ...                             ),IPermissionDetails)
        &gt;&gt;&gt; prinPerms  = permAdapter('zope.daniel',
        ...                          'ReadIssue.html',
        ...                           )
        
        &gt;&gt;&gt; print permAdapter.skin
        &lt;InterfaceClass zope.publisher.interfaces.browser.IBrowserRequest&gt;
        
        &gt;&gt;&gt; print permAdapter.read_perm
        zope.Public
        
        &gt;&gt;&gt; print permAdapter.view_name
        ReadIssue.html
        
        &gt;&gt;&gt; pprint(prinPerms)
        {'groups': {'zope.randy': {'groups': {'zope.group1': {'groups': {},
        'permissionTree': [],
        'permissions': [],
        'roleTree': [],
        'roles': {}},
        'zope.group2': {'groups': {},
        'permissionTree': [],
        'permissions': [],
        'roleTree': [],
        'roles': {}}},
        'permissionTree': [],
        'permissions': [],
        'roleTree': [],
        'roles': {}}},
        'permissionTree': [],
        'permissions': [],
        'roleTree': [],
        'roles': {}}
        
        Following are the helper functions used within the securitytool, These
        contain a set of common functionality that is used in many places.
        Lets see if the 'hasPermissionSetting' method returns True if there is
        a permission or role and False if there is not.
        
        &gt;&gt;&gt; hasPermissionSetting({'permissions':'Allow'})
        True
        
        We need to make some dummy objects to test the 'hasPermissionSetting' method
        
        &gt;&gt;&gt; emptySettings = {'permissions': [],
        ...                  'roles': {},
        ...                  'groups': {}}
        
        &gt;&gt;&gt; fullSettings = {'permissions': 'Allow',
        ...                  'roles': {},
        ...                  'groups': {}}
        
        We also need to make sure the recursive functionality works for this method
        
        &gt;&gt;&gt; hasPermissionSetting({'permissions':{},'roles':{},
        ...                                 'groups':{'group1':emptySettings,
        ...                                           'group2':fullSettings}})
        True
        
        &gt;&gt;&gt; from zope.securitypolicy.interfaces import Allow, Unset, Deny
        &gt;&gt;&gt; prinPermMap = ({'principal':'daniel',
        ...                 'permission':'takeOverTheWORLD',
        ...                 'setting':  Allow})
        
        &gt;&gt;&gt; rolePermMap = ({'role':'Janitor',
        ...                 'permission':'takeOverTheWORLD',
        ...                 'setting':  Allow})
        
        &gt;&gt;&gt; prinRoleMap = ({'principal':'daniel',
        ...                 'role':'Janitor',
        ...                 'setting':  Allow})
        
        
        Lets test the method with our new dummy data
        &gt;&gt;&gt; principalDirectlyProvidesPermission([prinPermMap],'daniel',
        ...                                          'takeOverTheWORLD')
        'Allow'
        
        And we also need to test the roleProvidesPermission
        &gt;&gt;&gt; roleProvidesPermission([rolePermMap], 'Janitor', 'takeOverTheWORLD')
        'Allow'
        
        And we also need to test the roleProvidesPermission
        &gt;&gt;&gt; principalRoleProvidesPermission([prinRoleMap],
        ...                                 [rolePermMap],
        ...                                 'daniel',
        ...                                 'takeOverTheWORLD')
        ('Janitor', 'Allow')
        
        See janitors CAN take over the world!!!!!
        
        And of course the rendered name to display on the page template
        If we do not receive a name that means we are on the root level.
        
        &gt;&gt;&gt; renderedName(None)
        u'Root Folder'
        
        &gt;&gt;&gt; renderedName('Daniel')
        'Daniel'
        
        &gt;&gt;&gt; folder1.populatePermissionMatrix('takeOverTheWORLD',[prinPermMap])
        
        
        TestBrowser Smoke Tests
        -----------------------
        
        Lets make sure all the views work properly. Just a simple smoke test
        
        &gt;&gt;&gt; from zope.testbrowser.testing import Browser
        &gt;&gt;&gt; manager = Browser()
        &gt;&gt;&gt; authHeader = 'Basic mgr:mgrpw'
        &gt;&gt;&gt; manager.addHeader('Authorization', authHeader)
        &gt;&gt;&gt; manager.handleErrors = False
        
        &gt;&gt;&gt; server = 'http://localhost:8080/++skin++SecurityTool'
        
        &gt;&gt;&gt; manager.open(server + '/@@securityMatrix.html')
        
        First we will check if the main page is available
        
        &gt;&gt;&gt; manager.open(server + '/@@securityMatrix.html')
        
        &gt;&gt;&gt; manager.open(server + '/Folder1/@@securityMatrix.html')
        
        &gt;&gt;&gt; manager.open(server + '/Folder1/Folder2/Folder3/@@securityMatrix.html')
        
        Now lets send the filter variable so our test is complete
        
        &gt;&gt;&gt; manager.open(server + '/@@securityMatrix.html?'
        ...              'FILTER=None&amp;selectedSkin=ConcordTimes')
        
        
        And with the selected permission
        
        &gt;&gt;&gt; manager.open(server + '/@@securityMatrix.html?'
        ...              'FILTER=None&amp;selectedSkin=ConcordTimes&amp;'
        ...              'selectedPermission=zope.Public')
        
        
        Here we send an invalid selectedPermisson ( just for coverage ) ;)
        
        &gt;&gt;&gt; manager.open(server + '/@@securityMatrix.html?'
        ...              'FILTER=None&amp;selectedSkin=ConcordTimes&amp;'
        ...              'selectedPermission=zope.dummy')
        
        And with the None permission
        
        &gt;&gt;&gt; manager.open(server + '/@@securityMatrix.html?'
        ...              'FILTER=None&amp;selectedSkin=ConcordTimes&amp;'
        ...              'selectedPermission=None')
        
        This is the principal detail page, you can get to by clicking on the
        principals name at the top of the form
        
        &gt;&gt;&gt; manager.open(server +
        ...              '/@@principalDetails.html?principal=zope.daniel')
        
        &gt;&gt;&gt; manager.open(server +
        ...              '/Folder1/Folder2/Folder3/'
        ...              '@@principalDetails.html?principal=zope.daniel')
        
        
        &gt;&gt;&gt; 'Permission settings' in manager.contents
        True
        
        
        And lets call the view without a principal
        
        &gt;&gt;&gt; manager.open(server + '/@@principalDetails.html')
        Traceback (most recent call last):
        ...
        PrincipalLookupError: no principal specified
        
        Here is the view you will see if you click on the actual permission
        value in the matrix intersecting the view to the user on a public view.
        
        &gt;&gt;&gt; manager.open(server + '/@@permissionDetails.html?'
        ...              'principal=zope.daniel&amp;view=PUT')
        
        Ok lets send the command without the principal
        
        &gt;&gt;&gt; manager.open(server + '/@@permissionDetails.html?view=PUT')
        Traceback (most recent call last):
        ...
        PrincipalLookupError: no user specified
        
        
        And now we will test it without the view name
        
        &gt;&gt;&gt; manager.open(server + '/@@permissionDetails.html?'
        ...                        'principal=zope.daniel')
        
        And now with a view name that does not exist
        
        &gt;&gt;&gt; manager.open(server + '/@@permissionDetails.html?'
        ...              'principal=zope.daniel&amp;view=garbage')
        
        Lets also test with a different context level
        
        &gt;&gt;&gt; manager.open(server +
        ...              '/Folder1/Folder2/Folder3/'
        ...              '@@permissionDetails.html'
        ...              '?principal=zope.daniel&amp;view=ReadIssue.html')
        
        
        =======
        CHANGES
        =======
        
        Version 0.4.1 (2008-06-12)
        ---------------------------
        - Fixed issue with inheritance display on the securityMatrix.html page
        - Added links to the views listed on the securityMatrix.html page
        - Refactored out the PrincipalDetails and the PermissionDetails to
        their own files
        - Added the ZPL text to the tops of all the py files
        - Refactored out the shared global functions to globalFunctions.py
        - Refactored out the MatrixDetails superclass to its own file.
        
        pant, pant, pant
        
        Version 0.4.0b (2008-06-09)
        ---------------------------
        - Updated page template for principal details
        - Sorting issue fixed on viewMatrix page
        
        Version 0.4.0 (2008-06-09)
        ---------------------------
        - Updated page template for principal details
        - Releasing as Beta
        
        Version 0.3.6b (2008-06-02)
        ---------------------------
        - Misc fixes to group permission inheritance.
        - Misc verbiage and layout updates to page templates.
        
        Version 0.3.6 (2008-05-25)
        ---------------------------
        - Security tool now inherits properly from groups.
        
        Version 0.3.5c (2008-05-24)
        ---------------------------
        - Mainly fixed documentation and DocTests
        
        Version 0.3.5b (2008-03-03)
        ---------------------------
        - Fixed issue where stylesheets would not display in skin
        - Added z3c.macro namespace to configure.zcml
        
        Version 0.3.5 (2008-03-02)
        --------------------------
        - Fixed issue where SecurityTool skin was only declared for the demo,
        skin is now declared in the configure.zcml.
        
        Version 0.3.4 (2008-02-26)
        --------------------------
        - Fixed issue with groups on permDetails and principalDetails pages
        - Fixed issue where securitytool views were declared as zope.Public
        - Added SecurityTool skin to register securitytool views against
        
        Version 0.3.3 (2008-02-21)
        --------------------------
        - Updated css and styles
        - Cleanup of page templates
        - Fixed permission details page
        
        Version 0.3.2 (2008-02-18)
        --------------------------
        - Updated css and styles
        - Cleanup of page templates
        - Updtated principalDetails with sorting
        - Fixed bug where some permissions were not being removed appropriately
        
        Version 0.3.1 (2008-02-07)
        --------------------------
        - Updated interfaces and views
        - Updated css and styles
        - Cleanup of page templates
        - Updtated principalDetails to show all data
        - Various bug fixes
        - Added some more roles and permissions for the demo.
        
        Version 0.3.0 (2008-02-07)
        --------------------------
        - Updated interfaces and views
        - Cleanup of page templates
        - Storing selected skin in session
        - Various bug fixes
        - Better project description
        
        Version 0.2.4 (2008-02-06)
        --------------------------
        - Fixed bug in permDetails
        - Updated interface and views
        - Added some more content to the demo
        
        
        Version 0.2.3 (2008-01-29)
        --------------------------
        - Fixed issue where all the permissions associated with a principal
        were not populating properly
        
        Version 0.2.2 (2008-01-28)
        --------------------------
        - Some enhancements on the page templates and css classes
        - Better test coverage and "Smoke" tests for all the available views
        
        Version 0.2.1 (2008-01-27)
        --------------------------
        - Fixed bug with Permission Details
        
        Version 0.2.0 (2008-01-26)
        --------------------------
        - Initial release of fully functional z3c.securitytool
        
        Version 0.2.1 (2008-01-26)
        --------------------------
        - Fixed bug with Principal Details page
        
        
        
        
        
        
        
Keywords: zope3 securitytool security
Platform: UNKNOWN
Classifier: Development Status :: 4 - Beta
Classifier: Environment :: Web Environment
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: Zope Public License
Classifier: Programming Language :: Python
Classifier: Natural Language :: English
Classifier: Operating System :: OS Independent
Classifier: Topic :: Internet :: WWW/HTTP
Classifier: Framework :: Zope3
