commit da604a721ad208342c4e10d7c5b3bf1830973acb Author: emma peel emma.peel@riseup.net Date: Wed May 19 15:15:38 2021 +0200

update contents from master --- content/relay/setup/bridge/fedora/contents.lr | 28 +++++++++------------------ 1 file changed, 9 insertions(+), 19 deletions(-)

diff --git a/content/relay/setup/bridge/fedora/contents.lr b/content/relay/setup/bridge/fedora/contents.lr index 095bac2..11113ba 100644 --- a/content/relay/setup/bridge/fedora/contents.lr +++ b/content/relay/setup/bridge/fedora/contents.lr @@ -22,22 +22,10 @@ cost=100 Then install tor and the dependencies.

``` -dnf install git golang tor policycoreutils-python-utils +dnf install tor obfs4 policycoreutils-python-utils ```

-### 2. Build obfs4proxy and move it into place. - -``` -export GOPATH=`mktemp -d` -go get gitlab.com/yawning/obfs4.git/obfs4proxy -sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/ -``` -And tell selinux to allow Tor to use obfs4proxy: -``` -/sbin/restorecon -v /usr/local/bin/obfs4proxy -``` - -### 3. Edit your Tor config file, usually located at `/etc/tor/torrc` and replace its content with: +### 2. Edit your Tor config file, usually located at `/etc/tor/torrc` and replace its content with:

``` RunAsDaemon 1 @@ -48,7 +36,7 @@ BridgeRelay 1 # censors may be scanning the Internet for this port. ORPort TODO1

-ServerTransportPlugin obfs4 exec /usr/local/bin/obfs4proxy +ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy

# Replace "TODO2" with an obfs4 port of your choice. This port must be # externally reachable and must be different from the one specified for ORPort. @@ -71,9 +59,11 @@ Nickname PickANickname

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. +* 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.

-### 4. Restart tor +### 3. Restart tor

``` sudo semanage port -a -t tor_port_t -p tcp [OR port set earlier, in TODO1] @@ -81,7 +71,7 @@ sudo semanage port -a -t tor_port_t -p tcp [obfs4 port set earlier, in TODO2] systemctl restart tor ```

-### 5. Monitor your logs (usually in your syslog) +### 4. Monitor your logs (usually in your syslog)

To confirm your bridge is running with no issues, you should see something like this:

@@ -95,7 +85,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. ```

-### 6. Final notes +### 5. Final notes

If you are having trouble setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/).