tor-commits October 2019

tor-commits@lists.torproject.org

22 participants
4141 discussions

[community/develop] Changed the page title to be consistent
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit 56f0ae2f1c3a8fd6db1320f8fb0341db01b2c41a 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] Make the updates page discoverable
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit e81de09e3e590cb0f35a7ae99fa586a9bbf11823 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] Include BSD auto update instructions, link to post-install
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit f5d506dcbb4451110225b8926255b3644cce4556 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] Add RPM based distros instructions to automatically update, link to post-install
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit aeb0731cc1b6d9e7c70724312c529646a020bc46 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] Add instructions to automatically update your Debian or Ubuntu relay, include post-install link
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit f99e8e40efe601ca7cb50deb9a981e7d6783ed76 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] Link to post-install notes at the end.
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit c1ec459a95cbcd4d6362fa67014d3820dc9e3b4a 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] Create child page with BSD auto update instructions
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit 3fc8f0efe60b71920863fe9d6ced516c2940110b 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] Replace node to relay so our documentation stay more consistent
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit 3b9712ce9bcedef350c4c51581b37c3012a0e2ae 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] Partially revert commit 404d5ca.
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit 34fb51d704d236736e4b85287775394c9ff1072a 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 Fedora instructions to automatically update relay, link to post-install instructions
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit cb3d88120d5c520a07fb9d41ca94f4488fcd2fe8 Author: gus <gus(a)torproject.org> Date: Thu Aug 29 06:27:44 2019 -0400 Add Fedora instructions to automatically update relay, link to post-install instructions --- .../technical-setup/guard/fedora/contents.lr | 14 +++++++-- .../guard/fedora/updates/contents.lr | 33 ++++++++++++++++++++++ 2 files changed, 44 insertions(+), 3 deletions(-) diff --git a/content/relay-operations/technical-setup/guard/fedora/contents.lr b/content/relay-operations/technical-setup/guard/fedora/contents.lr index cc984cc..5cfcf23 100644 --- a/content/relay-operations/technical-setup/guard/fedora/contents.lr +++ b/content/relay-operations/technical-setup/guard/fedora/contents.lr @@ -4,11 +4,15 @@ title: Fedora --- 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 `dnf install tor` -# 2. Put the tor configuration file `/etc/tor/torrc` in place: +# 3. Put the tor configuration file `/etc/tor/torrc` in place ``` #change the nickname "myNiceRelay" to a name that you like @@ -19,12 +23,16 @@ ExitRelay 0 ContactInfo tor-operator@your-emailaddress-domain ``` -# 3. Start the tor daemon and make sure it starts at boot: +# 4. Start the tor daemon and make sure it starts at boot ``` systemctl enable tor systemctl start tor ``` + +# 5. 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/fedora/updates/contents.lr b/content/relay-operations/technical-setup/guard/fedora/updates/contents.lr new file mode 100644 index 0000000..03ad164 --- /dev/null +++ b/content/relay-operations/technical-setup/guard/fedora/updates/contents.lr @@ -0,0 +1,33 @@ +_model: page +--- +title: Automatic Updates on Fedora +--- +body: + +On Fedora you enable automatic updates via: + +``` +dnf install dnf-automatic +``` + +Now enable and start automatic updates via: + +``` +systemctl enable --now dnf-automatic-install.timer +``` +--- +html: two-columns-page.html +--- +key: 1 +--- +section: Relay operations +--- +section_id: relay-operations +--- +subtitle: +--- +_hidden: yes +--- +_slug: updates +--- +_discoverable: no

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits October 2019