paulmataruso/zulip
1
0
Fork 0
mirror of https://github.com/zulip/zulip.git synced 2025-11-02 21:13:36 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: Explicitly list possible outgoing HTTP connections.

Browse Source
This commit is contained in:
Alex Vandiver
2021-03-03 22:36:36 -08:00
committed by Tim Abbott
parent 6777660e02
commit 653c67a2b6
1 changed files with 13 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

17
docs/production/security-model.md
View File

@@ -244,10 +244,19 @@ strength allowed is controlled by two settings in
messages when a message contains a link to an image. You can
control this using the `INLINE_IMAGE_PREVIEW` setting.
* A Zulip server can make outgoing HTTP requests through features like
outgoing webhooks and embedded video previews. End users have
(limited) control the content of these HTTP requests. As a result,
Zulip supports routing these outgoing requests [through
* Zulip may make outgoing HTTP connections to other servers in a
number of cases:
* Outgoing webhook bots (creation of which can be restricted)
* Inline image previews in messages (enabled by default, but can be disabled)
* Inline webpage previews and embeds (must be configured to be enabled)
* Twitter message previews (must be configured to be enabled)
* BigBlueButton and Zoom API requests (must be configured to be enabled)
* Mobile push notifications (must be configured to be enabled)
* Notably, these first 3 features give end users (limited) control to cause
the Zulip server to make HTTP requests on their behalf. As a result,
Zulip supports routing all outgoing outgoing HTTP requests [through
Smokescreen][smokescreen-setup] to ensure that Zulip cannot be
used to execute [SSRF attacks][SSRF] against other systems on an
internal corporate network. The default Smokescreen configuration