Opened 15 years ago
Last modified 7 years ago
#8395 closed enhancement
restriction of contents of notifications (both, subject and body) — at Initial Version
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
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 für #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
Note:
See TracTickets
for help on using tickets.