[tor-commits] [community/develop] Rephrase Debian-specific note to general note.
hiro at torproject.org
hiro at torproject.org
Thu Jan 23 16:44:42 UTC 2020
commit 4b3df13c6d26ec9c4b928ce8dd7c7d66c2af75ae
Author: Philipp Winter <phw at nymity.ch>
Date: Tue Nov 26 09:27:02 2019 -0800
Rephrase Debian-specific note to general note.
It doesn't just apply to Debian. It applies to Ubuntu as well. Thanks
to Micah for pointing this out!
---
.../relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
index 9596a38..7f302c6 100644
--- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
@@ -60,7 +60,7 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`,
If your bridge is behind a firewall or NAT, make sure to open both ports.
You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet.
-Under Debian, you will also need to set `NoNewPrivileges=no` in `/lib/systemd/system/tor at default.service` and `/lib/systemd/system/tor at .service` and then run `systemctl daemon-reload`. (see [bug #18356](https://trac.torproject.org/projects/tor/ticket/18356))
+You will also need to set `NoNewPrivileges=no` in `/lib/systemd/system/tor at default.service` and `/lib/systemd/system/tor at .service` and then run `systemctl daemon-reload`. (see [bug #18356](https://trac.torproject.org/projects/tor/ticket/18356))
### 4. Restart tor
More information about the tor-commits
mailing list