From 3c7581217cf92fdbcd3b889236e1af66b6a9c52d Mon Sep 17 00:00:00 2001
From: Felix Baumann <felix.bau@gmx.de>
Date: Sun, 9 Jun 2024 12:28:53 +0200
Subject: [PATCH] docs: site: pubkey_privacy works for wireguard (#3254)

(cherry picked from commit 068c12b5261e330d8bd4785334db34be772b109a)
---
 docs/user/site.rst | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/user/site.rst b/docs/user/site.rst
index 1861c6de..048d778a 100644
--- a/docs/user/site.rst
+++ b/docs/user/site.rst
@@ -297,7 +297,7 @@ mesh_vpn
   data; this prevents malicious ISPs from correlating VPN sessions with specific mesh
   nodes via public respondd data. If this is of no concern in your threat model,
   this behaviour can be disabled (and thus announcing the public key be enabled) by
-  setting `pubkey_privacy` to `false`. At the moment, this option only affects fastd.
+  setting `pubkey_privacy` to `false`.
 
   The `fastd` section configures settings specific to the *fastd* VPN
   implementation.
-- 
GitLab