Changes between Version 18 and Version 19 of SensitiveTicketsPlugin


Ignore:
Timestamp:
Feb 21, 2012, 5:52:28 AM (12 years ago)
Author:
Daniel Kahn Gillmor
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • SensitiveTicketsPlugin

    v18 v19  
    3434Users 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 This plugin also adds the REDACTED_SENSITIVE_ACTIVITY_VIEW
    37 permission.  Accounts with this permission will be able to see
    38 activity on sensitive material in the timeline, but will only be
    39 able to identify it by ticket number, comment number, and
    40 timestamp.
     36This plugin also adds the SENSITIVE_ACTIVITY_VIEW permission,
     37which is narrower in scope than SENSITIVE_VIEW.  Accounts with
     38SENSITIVE_ACTIVITY_VIEW will be able to see activity on sensitive
     39material in the timeline, but will only be able to identify it by
     40ticket number, comment number, and timestamp.  All other content
     41will be redacted.
    4142   
    42 REDACTED_SENSITIVE_ACTIVITY_VIEW can be useful (for example) for
     43SENSITIVE_ACTIVITY_VIEW can be useful (for example) for
    4344providing a notification daemon the ability to tell that some
    4445activity happened without leaking the content of that activity.