commit bbcb1574fb69804863d33ac96129965269cedc21 Author: Nick Gnazzo <nickgnazzo@icloud.com> Date: Thu Sep 12 10:48:39 2019 -0400 Fix OpenBSD tor bridge instructions (data dir + logging perms) --- .../technical-setup/bridge/openbsd/contents.lr | 14 +++++++++++--- 1 file changed, 11 insertions(+), 3 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr index 50d1a26..55b8f60 100644 --- a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr @@ -49,19 +49,27 @@ Nickname PickANickname Log notice file /var/log/tor/notices.log User _tor +DataDirectory /var/tor ``` Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options. * 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. -### 3. Start the tor daemon and make sure it starts at boot: +### 3. Create the tor log directory and give it the correct permissions: + +``` +mkdir /var/log/tor +chown _tor /var/log/tor +``` + +### 4. Start the tor daemon and make sure it starts at boot: ``` rcctl enable tor rcctl start tor ``` -### 4. Monitor your logs +### 5. Monitor your logs To confirm your bridge is running with no issues, you should see something like this (`/var/log/tor/notices.log`): @@ -75,7 +83,7 @@ To confirm your bridge is running with no issues, you should see something like [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. ``` -### 5. Final notes +### 6. Final notes If you are having troubles setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). If