Security Sandbox

This sandbox aims at adding a finer grained control for the TracPermissions system.

• Some related tickets: #654, #834, #948, #1316

The permission policy system has been rewritten on top of the Context objects.

The Wiki system, a significant part of the Ticket system and the attachment subsystem are now using the new permission policy engine.

• View the revision log
• See differences for Trac 0.11dev
• See patch for Trac 0.10dev (initial implementation)

Testing the features

You can check the source out from ​here using Subversion.

An example policy based on an Authz-style system has been added: see sandbox/pycon/security/sample-plugins/authz_policy.py.

• copy this file in your plugins directory
• install genshi
• plonk(sic) a ​authzpolicy.conf file somewhere
• update your trac.ini:

  [trac]
  ...
  permission_policies = AuthzPolicy
  
  [authz_policy]
  authz_file = /some/trac/env/conf/authzpolicy.conf
  
  [components]
  ...
  authz_policy = enabled
  

• Finally, restart your web server.

Note that the order in which permission policies are specified is quite critical, as policies will be examined in the given sequence. A policy will return either True, False or None for a givein permission check. Only if the return value is None will the next permission policy be consulted. If no policy explicitly grants the permission, the final result will be False (i.e. no permission).

For example, if the authz_file contains:

[wiki:WikiStart]
* = VIEW

[wiki:PrivatePage]
john = VIEW
* =

and the default permissions are set like this:

john           WIKI_VIEW
jack           WIKI_VIEW
# anonymous has no WIKI_VIEW

Then:

• WikiStart will be viewable by all (including anonymous)
• PrivatePage will be viewable only by john
• other pages will be viewable only by john and jack

---

See also: WikiContext