paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-10-30 19:43:47 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Document PUSH_NOTIFICATION_REDACT_CONTENT changes.

Browse Source 
This needs explanation both in upgrade notes and in the main
documentation for mobile push notifications.

Co-authored-by: Prakhar Pratyush <prakhar@zulip.com>
This commit is contained in:
Tim Abbott
2025-07-28 16:40:07 -07:00
parent d972bb1ca9
commit afdf20c67e
2 changed files with 33 additions and 11 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
docs/overview/changelog.md
View File

@@ -182,9 +182,23 @@ _Released 2025-07-17_
enabling the new `unique_account_id` setting for automatically
handling [email address
changes](../production/authentication-methods.md#synchronizing-email-addresses).
- The `PUSH_NOTIFICATION_REDACT_CONTENT` server setting has been
replaced by an organization-level setting in the "Notifications
security" subsection of "organization settings". The new
organization-level setting's initial value is copied from
`PUSH_NOTIFICATION_REDACT_CONTENT`, so you should delete the setting
from `/etc/zulip/settings.py` **after** completing the upgrade.
The replacement setting is designed and labeled with future mobile
client support for end-to-end encrypted (E2EE) mobile notifications
in mind: it will only redact message content for mobile clients
using the legacy non-E2EE protocol.
- Zulip's incoming email integration was simplified to no longer use
`postfix`. Installations using the integration will automatically
uninstall `postfix` when upgraded.
uninstall `postfix` when upgraded. If your Zulip server was using
`postfix` for another purpose as well, you'll need to manually
presenve and update your `postfix` configuration.
- The `SOCIAL_AUTH_SYNC_CUSTOM_ATTRS_DICT` setting has been removed.
It was deprecated in favor of `SOCIAL_AUTH_SYNC_ATTRS_DICT` in 10.0.

28
docs/production/mobile-push-notifications.md
View File

@@ -188,6 +188,13 @@ to these terms.
We've designed this push notification bouncer service with security
and privacy in mind:
- Zulip Server 11.0+ supports a new end-to-end encrypted (E2EE)
protocol for mobile push notifications. Because mobile app support
for that protocol is not yet available, this documentation details
the legacy protocol. This documentation will be updated to reflect
on the new protocol's better privacy guarantees once [official
mobile app support][e2ee-flutter-issue] for the new protocol is
generally available.
- A central design goal of the Push Notification Service is to
avoid any message content being stored or logged by the service,
even in error cases.
@@ -215,17 +222,16 @@ and privacy in mind:
- A timestamp.
- The message's content.
There's a `PUSH_NOTIFICATION_REDACT_CONTENT` setting available to
disable any message content being sent via the push notification
bouncer (i.e., message content will be replaced with
`New message`). Note that this setting makes push notifications
significantly less usable.
Zulip 11.0+ has an organization-level setting available to disable
message content being sent via the push notification bouncer (i.e.,
message content will be replaced with `New message`), for clients
that don't support the new end-to-end encrypted notifications
protocol. As of July 2025, this setting makes push notifications
significantly less usable, since mobile client support for
end-to-end encrypted push notifications is not yet available.
We plan to
[replace that setting with end-to-end encryption](https://github.com/zulip/zulip/issues/6954)
which would eliminate that usability tradeoff and additionally allow
us to not have any access to the other details mentioned in this
section.
(Prior to Zulip 11.0, this functionality was available via the
`PUSH_NOTIFICATION_REDACT_CONTENT` server-level setting).
- All of the network requests (both from Zulip servers to the Push
Notification Service and from the Push Notification Service to the
@@ -241,6 +247,8 @@ and privacy in mind:
If you have any questions about the security model, [contact Zulip
support](https://zulip.com/help/contact-support).
[e2ee-flutter-issue]: https://github.com/zulip/zulip-flutter/issues/1764
### Uploading basic metadata
All Zulip installations running Zulip 8.0 or greater that are