From df24c3151f8f395659f685311ebf13b5a8c083f0 Mon Sep 17 00:00:00 2001 From: Dominik Jain Date: Wed, 5 Aug 2026 21:31:03 +0200 Subject: [PATCH] Clarify responsibilities when exposing network services --- docs/02-usage/070_security.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/02-usage/070_security.md b/docs/02-usage/070_security.md index c3a06a0a..249409cf 100644 --- a/docs/02-usage/070_security.md +++ b/docs/02-usage/070_security.md @@ -111,7 +111,9 @@ By default, these services accept connections from localhost only, which is a se These services can be reconfigured to listen on other addresses, but doing so may have security implications. If you need to allow connections from other machines, we recommend that you set up a secure networking environment -(e.g. using a VPN or SSH tunnels) and ensure that only trusted machines can connect to these services. +and ensure that only trusted machines can connect to these services. +It is the responsibility of the user to restrict access appropriately, e.g. by placing the service behind a reverse +proxy (adding authentication) or firewall. ## Supply Chain Security