Changes between Version 17 and Version 18 of SensitiveTicketsPlugin


Ignore:
Timestamp:
Feb 20, 2012, 7:54:13 AM (3 years ago)
Author:
dkgdkg
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SensitiveTicketsPlugin

    v17 v18  
    88
    99''Beware:'' Hooks that send mail on ticket changes will still send mail for sensitive tickets; this may not be what you want.
     10
     11''Beware:'' [ticket:5784 if the plugin is removed, disabled, or fails to load, trac will opt to display sensitive tickets ("failing open" instead of "failing closed")]
    1012
    1113=== Examples ===
     
    2325== Configuration ==
    2426
    25 '''To use this plugin you will have to edit your `trac.ini` file to use the new !SenstiveTicketsPolicy permission policy, e.g.:
    26 '''
    27     {{{
    28     #!ini
    29     [components]
    30     sensitivetickets.* = enabled
     27Once this plugin is enabled, you'll have to insert it at the appropriate
     28place in your list of permission policies, e.g.
     29{{{
     30[trac]
     31permission_policies = SensitiveTicketsPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
     32}}}
    3133
    32     [trac]
    33     permission_policies = SensitiveTicketsPolicy, DefaultPermissionPolicy, LegacyAttachmentPolicy
    34     }}}
     34Users with SENSITIVE_VIEW privileges will be able to see and act on tickets marked sensitive, as will any user configured to be able to bypass the sensitive marker (e.g. if the user is the ticket owner or reporter, or is in the CC field, and the associated flags are set in `[sensitivetickets]` section of `trac.ini`.
    3535
    36 Needs an environment upgrade after enabling.
     36This plugin also adds the REDACTED_SENSITIVE_ACTIVITY_VIEW
     37permission.  Accounts with this permission will be able to see
     38activity on sensitive material in the timeline, but will only be
     39able to identify it by ticket number, comment number, and
     40timestamp.
     41   
     42REDACTED_SENSITIVE_ACTIVITY_VIEW can be useful (for example) for
     43providing a notification daemon the ability to tell that some
     44activity happened without leaking the content of that activity.
    3745
    38 (TODO: explain what !LegacyAttachmentPolicy is, and why one should or should not include it.)
     46
     47Needs an environment upgrade (or just adding the appropriate stanza to `[ticket-custom]` in `trac.ini` after enabling.
    3948
    4049== Bugs/Feature Requests ==
     
    5867== Author/Contributors ==
    5968
    60 '''Author:''' [wiki:sbenthall] [[BR]]
     69'''Author:''' [wiki:dkgdkg] [[BR]]
    6170'''Maintainer:''' [wiki:dkgdkg] [[BR]]
    62 '''Contributors:''' [wiki:k0s], [wiki:obs] [[BR]]
     71'''Contributors:''' [wiki:sbenthall], [wiki:k0s], [wiki:obs] [[BR]]