[tor-commits] [community/develop] Turn bullet point into paragraph.
emmapeel at torproject.org
emmapeel at torproject.org
Sat Oct 5 07:39:30 UTC 2019
commit 3eb5e6f435b58ee43cd0afb921fc7605fd17cb52
Author: Philipp Winter <phw at nymity.ch>
Date: Mon Aug 26 17:24:46 2019 -0700
Turn bullet point into paragraph.
The bullet point wants to be a paragraph because it's not related to the
other two bullet points.
Thanks to Roger for pointing this out.
---
.../relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
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 16037a4..8273f8f 100644
--- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
+++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr
@@ -52,12 +52,12 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`,
`sudo setcap cap_net_bind_service=+ep /usr/bin/obfs4proxy`
-* 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))
-
* Note that both Tor's OR port and its obfs4 port must be reachable.
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))
+
### 4. Restart tor
`systemctl restart tor`
More information about the tor-commits
mailing list