Zope-security

==================

- Corresponds to the verison of the ``zope.security`` package shipped as part
of the Zope 3.2.0 release.

- Remove deprecated helper functions, ``proxy.trustedRemoveSecurityProxy``
and ``proxy.getProxiedObject``.

- Make handling of ``management.{end,restore}Interaction`` more careful w.r.t.
edge cases.

- Make behavior of ``canWrite`` consistent with ``canAccess``:
if ``canAccess`` does not raise ``ForbiddenAttribute``, then neither will
``canWrite``. See: http://www.zope.org/Collectors/Zope3-dev/506

- Code style / documentation / test fixes.

==================

- Add support for use of the new Python 2.4 datatypes, ``set`` and
``frozenset``, within checked code.

- Make the C security proxy depend on the ``proxy.h`` header from the
``zope.proxy`` package.

- XXX: the spelling of the ``include`` is bizarre! It seems to be related to
``zpkg``-based builds, and should likely be revisited. For the moment, I have
linked in the ``zope.proxy`` package into our own ``include`` directory. See
the subversion checkin: http://svn.zope.org/Zope3/?rev=37882&view=rev

- Update checker to avoid re-proxying objects which have and explicit
``__Security_checker__`` assigned.

- Corresponds to the verison of the ``zope.security`` package shipped as part of
the Zope 3.1.0 release.

- Clarify contract of ``IChecker`` to indicate that its ``check*`` methods may
raise only ``Forbidden`` or ``Unauthorized`` exceptions.

- Add interfaces, (``IPrincipal``, ``IGroupAwarePrincipal``, ``IGroup``, and
``IPermission``) specifying contracts of components in the security framework.

- Code style / documentation / test fixes.

==================

- Corresponds to the version of the ``zope.security`` package shipped as part
of the Zope X3.0.0 release.