September 2019 - tor-commits - lists.torproject.org

[community/develop] Link to post-install notes at the end.
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 44666a8f263051f27559699e1cc0902c30d7f8a7 Author: Philipp Winter <phw(a)nymity.ch> Date: Mon Aug 26 18:02:53 2019 -0700 Link to post-install notes at the end. Once somebody is done following the instructions, we should explicitly point them to our post-install notes because they are otherwise easy to miss. Thanks to Roger for pointing this out. --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 7 +++++++ .../technical-setup/bridge/debian-ubuntu/contents.lr | 8 ++++++++ .../relay-operations/technical-setup/bridge/docker/contents.lr | 7 ++++++- .../relay-operations/technical-setup/bridge/freebsd/contents.lr | 7 +++++++ .../relay-operations/technical-setup/bridge/openbsd/contents.lr | 8 ++++++++ 5 files changed, 36 insertions(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr index f142d56..5fba1a6 100644 --- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr @@ -92,6 +92,13 @@ 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 + +If you are having troubles setting up your bridge, have a look at [our help +section](https://community.torproject.org/relay/setup/bridge/getting-help/). If +your bridge is now running, check out the [post-install +notes](https://community.torproject.org/relay/setup/bridge/post-install/). + --- html: two-columns-page.html --- 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 8273f8f..d1eeb17 100644 --- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr @@ -76,6 +76,14 @@ To confirm your bridge is running with no issues, you should see something like [notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. ``` + +### 6. Final notes + +If you are having troubles setting up your bridge, have a look at [our help +section](https://community.torproject.org/relay/setup/bridge/getting-help/). If +your bridge is now running, check out the [post-install +notes](https://community.torproject.org/relay/setup/bridge/post-install/). + --- key: 1 --- diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index ca3d7f7..1c36012 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -14,7 +14,12 @@ Now, it's time to run the container. We maintain a script that automatically de $ bash deploy-container.sh address(a)email.com ``` -That's it! Your container should now be bootstrapping your new obfs4 Tor bridge. +That's it! Your container should now be bootstrapping your new obfs4 Tor bridge. +Make sure to check out the [post-install +notes](https://community.torproject.org/relay/setup/bridge/post-install/). If +you are having troubles setting up your bridge, have a look at [our help +section](https://community.torproject.org/relay/setup/bridge/getting-help/). + --- html: two-columns-page.html --- diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index 78373df..0741c8c 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -103,6 +103,13 @@ FreeBSDlatest: { } ``` +### 7. Final notes + +If you are having troubles setting up your bridge, have a look at [our help +section](https://community.torproject.org/relay/setup/bridge/getting-help/). If +your bridge is now running, check out the [post-install +notes](https://community.torproject.org/relay/setup/bridge/post-install/). + --- subtitle: How to deploy an obfs4 bridge on FreeBSD --- diff --git a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr index 0a02f9e..1c95aaa 100644 --- a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr @@ -72,6 +72,14 @@ To confirm your bridge is running with no issues, you should see something like [notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. ``` + +### 5. Final notes + +If you are having troubles setting up your bridge, have a look at [our help +section](https://community.torproject.org/relay/setup/bridge/getting-help/). If +your bridge is now running, check out the [post-install +notes](https://community.torproject.org/relay/setup/bridge/post-install/). + --- subtitle: How to deploy an obfs4 bridge on OpenBSD ---

1 0

[community/develop] Partially revert commit 404d5ca.
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 7de04df2ab6c61a51e11a2d9329d1418a4f7f8fd Author: Philipp Winter <phw(a)nymity.ch> Date: Tue Aug 27 10:02:01 2019 -0700 Partially revert commit 404d5ca. Only Debian is known to set RunAsDaemon to 1 by default. We don't know about the other tor distributions. Let's keep 'RunAsDaemon 1' for the other distributions. --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 1 + content/relay-operations/technical-setup/bridge/freebsd/contents.lr | 1 + content/relay-operations/technical-setup/bridge/openbsd/contents.lr | 1 + 3 files changed, 3 insertions(+) diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr index 5fba1a6..091dbb5 100644 --- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr @@ -43,6 +43,7 @@ sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/ ### 3. Edit your Tor config file, usually located at `/etc/tor/torrc` and replace its content with: ``` +RunAsDaemon 1 BridgeRelay 1 # Replace "TODO" with a Tor port of your choice. This port must be externally diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index 0741c8c..d4bb28e 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -17,6 +17,7 @@ pkg install obfs4proxy-tor tor ca_root_nss ### 2. Edit your Tor config file, usually located at `/usr/local/etc/tor` and replace its content with: ``` +RunAsDaemon 1 BridgeRelay 1 # Replace "TODO" with a Tor port of your choice. This port must be externally diff --git a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr index 1c95aaa..d2e05a8 100644 --- a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr @@ -18,6 +18,7 @@ pkg_add tor obfs4proxy Usually located at `/etc/tor/torrc`, and replace its content with: ``` +RunAsDaemon 1 BridgeRelay 1 # Replace "TODO" with a Tor port of your choice. This port must be externally

1 0

[community/develop] Add instructions to automatically update your Debian or Ubuntu relay, include post-install link
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit f91f9786c4e950cd6b522b15e089969c0e996f30 Author: gus <gus(a)torproject.org> Date: Thu Aug 29 05:17:15 2019 -0400 Add instructions to automatically update your Debian or Ubuntu relay, include post-install link --- .../technical-setup/guard/debianubuntu/contents.lr | 16 ++++-- .../guard/debianubuntu/updates/contents.lr | 61 ++++++++++++++++++++++ 2 files changed, 73 insertions(+), 4 deletions(-) diff --git a/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr b/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr index f7992dd..2a8bedb 100644 --- a/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr +++ b/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr @@ -4,17 +4,21 @@ title: Debian/Ubuntu --- body: -# 1. Configure Tor Package Repository +# 1. Enable Automatic Software Updates + +One of the most imported things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. + +# 2. Configure Tor Package Repository Enable the Torproject package repository by following the instructions **[here](https://2019.www.torproject.org/docs/debian.html.en#ubuntu)**. -# 2. Package Installation +# 3. Package Installation Install the `tor` package: `apt update && apt install tor` -# 3. Configuration File +# 4. Configuration File Put the configuration file `/etc/tor/torrc` in place: @@ -29,11 +33,15 @@ ControlSocket 0 ContactInfo tor-operator@your-emailaddress-domain ``` -# 4. Restart the Service +# 5. Restart the Service Restart the tor daemon so your configuration changes take effect: `systemctl restart tor@default` + +# 6. Final notes + +If you are having troubles setting up your relay, have a look at our [help section](FIXME). If your relay is now running, check out the [post-install](/relay/setup/post-install/) notes. --- html: two-columns-page.html --- diff --git a/content/relay-operations/technical-setup/guard/debianubuntu/updates/contents.lr b/content/relay-operations/technical-setup/guard/debianubuntu/updates/contents.lr new file mode 100644 index 0000000..05da34b --- /dev/null +++ b/content/relay-operations/technical-setup/guard/debianubuntu/updates/contents.lr @@ -0,0 +1,61 @@ +_model: page +--- +title: Debian Ubuntu Updates +--- +_discoverable: yes +--- +_hidden: yes +--- +body: + +# 1. Install the required packages + +``` +apt-get install unattended-upgrades apt-listchanges +``` + +# 2. Edit the configuration file + +Put the lines below into the configuration file /etc/apt/apt.conf.d/50unattended-upgrades, everything that was originally inside the generated file can be removed before you add the lines below. + +``` + Unattended-Upgrade::Origins-Pattern { + "origin=Debian,codename=${distro_codename},label=Debian-Security"; + "origin=TorProject"; + }; + Unattended-Upgrade::Package-Blacklist { + }; +``` + +#3. Automatically reboot + +If you want to automatically reboot add the following at the the end of the file `/etc/apt/apt.conf.d/50unattended-upgrades`: + +``` + Unattended-Upgrade::Automatic-Reboot "true"; + + Create the file /etc/apt/apt.conf.d/20auto-upgrades with the following content + + APT::Periodic::Update-Package-Lists "1"; + APT::Periodic::AutocleanInterval "5"; + APT::Periodic::Unattended-Upgrade "1"; + APT::Periodic::Verbose "1"; +``` + +# 4. Test + +You can test your unattended-upgrades setup with the following command: + +``` + sudo unattended-upgrade -d +``` +--- +html: two-columns-page.html +--- +key: 1 +--- +section: Relays Operations +--- +section_id: relays-operations +--- +_slug: updates

1 0

[community/develop] Make the updates page discoverable
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 601e1a519f3ebb971e7a5c9bbbd0dcf223bd0e39 Author: gus <gus(a)torproject.org> Date: Thu Aug 29 06:59:29 2019 -0400 Make the updates page discoverable --- .../relay-operations/technical-setup/guard/fedora/updates/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/guard/fedora/updates/contents.lr b/content/relay-operations/technical-setup/guard/fedora/updates/contents.lr index 03ad164..f8ee3f7 100644 --- a/content/relay-operations/technical-setup/guard/fedora/updates/contents.lr +++ b/content/relay-operations/technical-setup/guard/fedora/updates/contents.lr @@ -30,4 +30,4 @@ _hidden: yes --- _slug: updates --- -_discoverable: no +_discoverable: yes

1 0

[community/develop] Replace node to relay so our documentation stay more consistent
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit f091687672cdd32262bf79329bc14460763fcf39 Author: gus <gus(a)torproject.org> Date: Thu Aug 29 07:16:41 2019 -0400 Replace node to relay so our documentation stay more consistent --- content/relay-operations/technical-setup/guard/centosrhel/contents.lr | 2 +- content/relay-operations/technical-setup/guard/debianubuntu/contents.lr | 2 +- content/relay-operations/technical-setup/guard/fedora/contents.lr | 2 +- content/relay-operations/technical-setup/guard/freebsd/contents.lr | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-) diff --git a/content/relay-operations/technical-setup/guard/centosrhel/contents.lr b/content/relay-operations/technical-setup/guard/centosrhel/contents.lr index 9ab6048..47ee38c 100644 --- a/content/relay-operations/technical-setup/guard/centosrhel/contents.lr +++ b/content/relay-operations/technical-setup/guard/centosrhel/contents.lr @@ -61,4 +61,4 @@ section: relay operations --- section_id: relay-operations --- -subtitle: How to deploy a middle/Guard node on CentOS/RHEL +subtitle: How to deploy a middle/Guard relay on CentOS/RHEL diff --git a/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr b/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr index 2a8bedb..c3e1f15 100644 --- a/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr +++ b/content/relay-operations/technical-setup/guard/debianubuntu/contents.lr @@ -51,4 +51,4 @@ section: relay operations --- section_id: relay-operations --- -subtitle: How to deploy a middle/Guard node on Debian/Ubuntu +subtitle: How to deploy a middle/Guard relay on Debian/Ubuntu diff --git a/content/relay-operations/technical-setup/guard/fedora/contents.lr b/content/relay-operations/technical-setup/guard/fedora/contents.lr index 5cfcf23..b89a8ce 100644 --- a/content/relay-operations/technical-setup/guard/fedora/contents.lr +++ b/content/relay-operations/technical-setup/guard/fedora/contents.lr @@ -42,4 +42,4 @@ section: relay operations --- section_id: relay-operations --- -subtitle: How to deploy a middle/Guard node on Fedora +subtitle: How to deploy a middle/Guard relay on Fedora diff --git a/content/relay-operations/technical-setup/guard/freebsd/contents.lr b/content/relay-operations/technical-setup/guard/freebsd/contents.lr index 01504ac..c86be07 100644 --- a/content/relay-operations/technical-setup/guard/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/guard/freebsd/contents.lr @@ -77,4 +77,4 @@ section: relay operations --- section_id: relay-operations --- -subtitle: How to deploy a middle/Guard node on FreeBSD +subtitle: How to deploy a middle/Guard relay on FreeBSD

1 0

[community/develop] Changed the page title to be consistent
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit c3c8c0908c1a860cba408f31672a03fb60c86a28 Author: gus <gus(a)torproject.org> Date: Thu Aug 29 06:28:38 2019 -0400 Changed the page title to be consistent --- .../technical-setup/guard/debianubuntu/updates/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/guard/debianubuntu/updates/contents.lr b/content/relay-operations/technical-setup/guard/debianubuntu/updates/contents.lr index 05da34b..39c6547 100644 --- a/content/relay-operations/technical-setup/guard/debianubuntu/updates/contents.lr +++ b/content/relay-operations/technical-setup/guard/debianubuntu/updates/contents.lr @@ -1,6 +1,6 @@ _model: page --- -title: Debian Ubuntu Updates +title: Automatic updates on Debian and Ubuntu --- _discoverable: yes ---

1 0

[community/develop] Create child page with BSD auto update instructions
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 4199fadb0719d57d6a752aae49d7504fb894c882 Author: gus <gus(a)torproject.org> Date: Thu Aug 29 07:12:44 2019 -0400 Create child page with BSD auto update instructions --- .../guard/freebsd/updates/contents.lr | 45 ++++++++++++++++++++++ 1 file changed, 45 insertions(+) diff --git a/content/relay-operations/technical-setup/guard/freebsd/updates/contents.lr b/content/relay-operations/technical-setup/guard/freebsd/updates/contents.lr new file mode 100644 index 0000000..bc1dd05 --- /dev/null +++ b/content/relay-operations/technical-setup/guard/freebsd/updates/contents.lr @@ -0,0 +1,45 @@ +_model: page +--- +title: Automatic Updates on BSD* +--- +_hidden: no +--- +_slug: updates +--- +body: + +# DragonFlyBSD / FreeBSD / HardenedBSD + +**NOTE:** _all steps documented on this page are considering that your machine/server/system only provides Tor relay services. please be aware that other services running might stop/restart during the upgrade._ + +#1. Create the script to perform the updates. + +Let's use `/root/pkg_upgrade.sh` + +``` +#!/usr/bin/env sh +PATH="/bin:/usr/bin:/sbin:/usr/sbin" +RAND=$(jot -r 1 300) +sleep ${RAND} +env AUTOCLEAN=YES ASSUME_ALWAYS_YES=YES HANDLE_RC_SCRIPTS=YES pkg upgrade +``` + +#2. Schedule the job to run. + +``` +# echo "0 0 * * * root /bin/sh /root/pkg_upgrade.sh >/dev/null" >> /etc/crontab +``` + +#3. Restart cron's service. + +``` +# service cron restart +``` +--- +html: two-columns-page.html +--- +section: relay operations +--- +section_id: relay-operations +--- +key: 1

1 0

[community/develop] Add RPM based distros instructions to automatically update, link to post-install
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit d51b40813138dcdd95525315f1e9554cb3c98bd7 Author: gus <gus(a)torproject.org> Date: Thu Aug 29 06:53:32 2019 -0400 Add RPM based distros instructions to automatically update, link to post-install --- .../technical-setup/guard/centosrhel/contents.lr | 16 +++-- .../guard/centosrhel/updates/contents.lr | 68 ++++++++++++++++++++++ 2 files changed, 80 insertions(+), 4 deletions(-) diff --git a/content/relay-operations/technical-setup/guard/centosrhel/contents.lr b/content/relay-operations/technical-setup/guard/centosrhel/contents.lr index 27b6031..9ab6048 100644 --- a/content/relay-operations/technical-setup/guard/centosrhel/contents.lr +++ b/content/relay-operations/technical-setup/guard/centosrhel/contents.lr @@ -4,19 +4,23 @@ title: CentOS/RHEL --- body: -# 1. Enable the EPEL repository +# 1. Enable Automatic Software Updates + +One of the most imported things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. + +# 2. Enable the EPEL repository To install `tor` package on CentOS/RHEL, you need to install the [EPEL](https://fedoraproject.org/wiki/EPEL) repository first: `yum install epel-release` -# 2. Install the tor package and verify the EPEL signing key +# 3. Install the tor package and verify the EPEL signing key `yum install tor` When you install the first package from the EPEL repository you will be asked about verifying the EPEL GPG signing key. Please ensure the key matches with the one available on the [Fedora Project website](https://getfedora.org/keys/). -# 3. Put the tor configuration file `/etc/tor/torrc` in place +# 4. Put the tor configuration file `/etc/tor/torrc` in place ``` #change the nickname "myNiceRelay" to a name that you like @@ -28,7 +32,7 @@ ExitRelay 0 ContactInfo tor-operator@your-emailaddress-domain ``` -# 4. Enable and start your Tor relay +# 5. Enable and start your Tor relay CentOS 7 / RHEL 7: @@ -44,6 +48,10 @@ service tor enable service tor start ``` +# 6. Final notes + +If you are having troubles setting up your relay, have a look at our [help section](FIXME). If your relay is now running, check out the [post-install](/relay/setup/post-install/) notes. + --- html: two-columns-page.html --- diff --git a/content/relay-operations/technical-setup/guard/centosrhel/updates/contents.lr b/content/relay-operations/technical-setup/guard/centosrhel/updates/contents.lr new file mode 100644 index 0000000..c452749 --- /dev/null +++ b/content/relay-operations/technical-setup/guard/centosrhel/updates/contents.lr @@ -0,0 +1,68 @@ +_model: page +--- +title: Automatic Updates on RPM Distributions +--- +_hidden: yes +--- +body: + +# CentOS and RHEL + +For CentOS and RHEL the yum-cron package is the preferred approach: + +``` +yum install yum-cron +``` + +In /etc/yum/yum-cron.conf set: + +``` +download_updates = yes +apply_updates = yes +``` + +Enable and start automatic updates via: + +``` +systemctl start yum-cron.service +``` + +# openSUSE + +First, you need to install the automatic update package + +``` +zypper install yast2-online-update-configuration +``` + +Then start the configuration tool (ncurses based) with: + +``` +yast2 online_update_configuration +``` + +Enable the following settings: + +``` + Automatic Online Update + Interval: Daily + Skip Interactive Patches + Agree with Licenses + Use delta rpms +``` + +Confirm your configuration with OK. + +The official openSUSE documentation can be found [here](https://doc.opensuse.org/documentation/leap/startup/html/book.opensus…. +--- +html: two-columns-page.html +--- +key: 1 +--- +section: Relay Operations +--- +section_id: relay-operations +--- +_slug: updates +--- +_discoverable: yes

1 0

[community/develop] Include BSD auto update instructions, link to post-install
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 26e64b72a4e4c2f0a55c919ac4acc446c8ad21a9 Author: gus <gus(a)torproject.org> Date: Thu Aug 29 07:05:06 2019 -0400 Include BSD auto update instructions, link to post-install --- .../technical-setup/guard/freebsd/contents.lr | 15 +++++++++++---- 1 file changed, 11 insertions(+), 4 deletions(-) diff --git a/content/relay-operations/technical-setup/guard/freebsd/contents.lr b/content/relay-operations/technical-setup/guard/freebsd/contents.lr index a47dfc8..01504ac 100644 --- a/content/relay-operations/technical-setup/guard/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/guard/freebsd/contents.lr @@ -4,7 +4,11 @@ title: FreeBSD --- body: -## 1. Install the tor package +# 1. Enable Automatic Software Updates + +One of the most imported things to keeps your relay secure is to install security updates timely and ideally automatically so you can not forget about it. Follow the instructions to enable [automatic software updates](updates) for your operating system. + +# 2. Install the tor package `pkg install tor ca_root_nss` @@ -12,7 +16,7 @@ or for alpha releases: `pkg install tor-devel ca_root_nss` -## 2. Put the configuration file `/usr/local/etc/tor/torrc` in place +# 3. Put the configuration file `/usr/local/etc/tor/torrc` in place ``` #change the nickname "myNiceRelay" to a name that you like @@ -25,14 +29,14 @@ ContactInfo tor-operator@your-emailaddress-domain Log notice syslog ``` -## 3. Ensure that the `random_id` sysctl setting is enabled: +# 4. Ensure that the `random_id` sysctl setting is enabled: ``` echo "net.inet.ip.random_id=1" >> /etc/sysctl.conf sysctl net.inet.ip.random_id=1 ``` -## 4. Start the tor daemon and make sure it starts at boot: +# 5. Start the tor daemon and make sure it starts at boot: ``` sysrc tor_enable=YES @@ -61,6 +65,9 @@ FreeBSDlatest: { } ``` +# 6. Final notes + +If you are having troubles setting up your relay, have a look at our [help section](FIXME). If your relay is now running, check out the [post-install](/relay/setup/post-install/) notes. --- html: two-columns-page.html ---

1 0

[community/develop] Update colors in relay guide
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 237a3c7ffb6c541e34c07364d7ba2c017a063884 Author: hiro <hiro(a)torproject.org> Date: Thu Aug 29 15:17:14 2019 +0200 Update colors in relay guide --- .../bridge/centos-rhel-opensuse/contents.lr | 14 ++++++++------ .../technical-setup/bridge/debian-ubuntu/contents.lr | 2 ++ .../technical-setup/bridge/docker/contents.lr | 2 ++ .../technical-setup/bridge/freebsd/contents.lr | 6 ++++-- .../technical-setup/bridge/getting-help/contents.lr | 2 ++ 5 files changed, 18 insertions(+), 8 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr index 091dbb5..2d232a7 100644 --- a/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr +++ b/content/relay-operations/technical-setup/bridge/centos-rhel-opensuse/contents.lr @@ -1,10 +1,12 @@ _model: page --- +color: primary +--- title: CentOS / RHEL / OpenSUSE --- body: -### 1. Install tor and dependencies +### 1. Install tor and dependencies * Redhat / RHEL: @@ -19,7 +21,7 @@ yum install git golang tor zypper install tor go git ``` -### 2. Build obfs4proxy and move it into place. +### 2. Build obfs4proxy and move it into place. Heavily outdated versions of git can make `go get` fail, so try upgrading to a more recent git version if you're running into this problem. @@ -71,7 +73,7 @@ ContactInfo <address(a)email.com> Nickname PickANickname ``` - Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options. + 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. @@ -83,7 +85,7 @@ Nickname PickANickname To confirm your bridge is running with no issues, you should see something like this: -``` +``` [notice] Your Tor server's identity key fingerprint is '<NICKNAME> <FINGERPRINT>' [notice] Your Tor bridge's hashed identity key fingerprint is '<NICKNAME> <HASHED FINGERPRINT>' [notice] Registered server transport 'obfs4' at '[::]:46396' @@ -91,7 +93,7 @@ To confirm your bridge is running with no issues, you should see something like [notice] Bootstrapped 100%: Done [notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. -``` +``` ### 6. Final notes @@ -105,7 +107,7 @@ html: two-columns-page.html --- key: -2 +2 --- color: primary --- 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 d1eeb17..41b4f76 100644 --- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr @@ -1,5 +1,7 @@ _model: page --- +color: primary +--- title: Debian / Ubuntu --- body: diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index 1c36012..f8925a1 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -1,5 +1,7 @@ _model: page --- +color: primary +--- title: Docker --- body: diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index d4bb28e..9088fa5 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -1,5 +1,7 @@ _model: page --- +color: primary +--- title: FreeBSD --- html: two-columns-page.html @@ -47,7 +49,7 @@ Nickname PickANickname Log notice file /var/log/tor/notices.log ``` -Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options. +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. @@ -67,7 +69,7 @@ sysrc tor_enable=YES service tor start ``` -### 5. Monitor your logs +### 5. Monitor your logs To confirm your bridge is running with no issues, you should see something like this in `/var/log/tor/notices.log`: diff --git a/content/relay-operations/technical-setup/bridge/getting-help/contents.lr b/content/relay-operations/technical-setup/bridge/getting-help/contents.lr index 828d351..cb72875 100644 --- a/content/relay-operations/technical-setup/bridge/getting-help/contents.lr +++ b/content/relay-operations/technical-setup/bridge/getting-help/contents.lr @@ -1,5 +1,7 @@ _model: page --- +color: primary +--- title: Getting help --- body:

1 0