Opened 15 years ago
Last modified 7 years ago
#8395 closed enhancement
restriction of contents of notifications (both, subject and body) — at Version 1
Reported by: | xyanipheia | Owned by: | Emmanuel Blot |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | notification | Version: | 0.10.3.1 |
Severity: | normal | Keywords: | confidentiality |
Cc: | Branch: | ||
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description (last modified by )
In #8294 GPG encoded notifications were mentioned. An easy workaround is to restrict the content of notifications. In this case no critical content is sent to the recipients, only a ticket number and the project link. Of course, encrypted notification is more preferable, but maybe this approach may be implemented earlier than milestone 2.0 for #8294? This approach allows to use TRAC in restricted environments if additionally:
- the server is protected (https with client certificates, …
- the project names are chosen to be simple, e.g. only project-numbers
Change History (1)
comment:1 by , 15 years ago
Description: | modified (diff) |
---|---|
Keywords: | confidentiality added |
Milestone: | → 0.13 |
Note:
See TracTickets
for help on using tickets.
Replying to xyanipheia:
Well, this mainly depends of someone implementing that feature, see TracDev/SubmittingPatches.
As here it's mainly a matter of adding a boolean config option and checking for the flag before writing the content of the notification mail, this should be a pretty easy task. See TracNotification to get some ideas about the config option name. I'd suggest
ticket_omit_content
, or if you want more control,ticket_omit_fields
,ticket_omit_changes
andticket_omit_comment
. All defaulting toFalse
for compatibility with current behavior.Also the already ticket_subject_template can be used to restrict the information shown in the mail summary.