March 2021 - tor-commits - lists.torproject.org

[community/staging] Merge branch 'fedora-guide' of github.com:BunnyApocalypse/community into fedora-guide
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit ba29705a7f40bdde753895190d0706333d515ab9 Merge: 31fda16 58c72a4 Author: Philipp Winter <phw(a)nymity.ch> Date: Wed Sep 4 09:26:44 2019 -0700 Merge branch 'fedora-guide' of github.com:BunnyApocalypse/community into fedora-guide .../technical-setup/bridge/fedora/contents.lr | 106 +++++++++++++++++++++ 1 file changed, 106 insertions(+)

1 0

[community/staging] Update xml stream
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 84d9e3541181970a1ac41725e91d18906a72eacb Author: hiro <hiro(a)torproject.org> Date: Wed Sep 4 14:46:36 2019 +0200 Update xml stream --- lego | 2 +- templates/outreach.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lego b/lego index 4e07d49..62b25f1 160000 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 4e07d49bc08514376151c3a7c73dd3ed0b67583d +Subproject commit 62b25f1cba4a7af931ccd8f4420d0669812db09c diff --git a/templates/outreach.html b/templates/outreach.html index e35f896..a640059 100644 --- a/templates/outreach.html +++ b/templates/outreach.html @@ -35,7 +35,7 @@ <div class="row py-5 text-center mx-auto"> <h2 class="display-4 text-primary text-center mx-auto">{{ _('Upcoming Tor Events') }}</h2> <div class="col-12"> - {{ render_stream()|safe }} + {{ render_stream("https://blog.torproject.org/events.xml")|safe }} </div> </div> </div>

1 0

[community/staging] Swap order for consistency.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit ded0deb18c6f8e06e0e008578237ab644d799f79 Author: Philipp Winter <phw(a)nymity.ch> Date: Wed Sep 4 12:05:31 2019 -0700 Swap order for consistency. --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 2 +- 1 file changed, 1 insertion(+), 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 04b7b77..13b3119 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 @@ -82,7 +82,7 @@ Nickname PickANickname ### 4. Restart tor -* RHEL / CentOS: +* CentOS / RHEL: ``` sudo semanage port -a -t tor_port_t -p tcp [desired ORPort number set earlier]

1 0

[community/staging] Add some formatting and remove trailing spaces
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 5c943cbfc68a8c3d877e7df6fb4056315a273b51 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:14:28 2019 -0400 Add some formatting and remove trailing spaces --- .../community-resources/good-bad-isps/contents.lr | 14 +++++--------- 1 file changed, 5 insertions(+), 9 deletions(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index b56d7ce..4100d18 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -12,12 +12,12 @@ Since non-exits do not attract complaints, it should be fine to run them without For network diversity and stronger anonymity, you should avoid providers and countries that already attract a lot of Tor capacity. [Metrics](https://metrics.torproject.org/) is a great tool that allows you to group probabilities by country and AS (autonomous systems), so you can more easily identify networks you want to avoid. - **Try to avoid** the following hosters: +**Try to avoid** the following hosters: -* OVH SAS (AS16276) -* Online S.a.s. (AS12876) -* Hetzner Online GmbH (AS24940) -* DigitalOcean, LLC (AS14061) + * OVH SAS (AS16276) + * Online S.a.s. (AS12876) + * Hetzner Online GmbH (AS24940) + * DigitalOcean, LLC (AS14061) **Note**: This page is currently being revamped. If you would like to help out please see [#31063](https://trac.torproject.org/projects/tor/ticket/31063). @@ -306,10 +306,6 @@ For network diversity and stronger anonymity, you should avoid providers and cou | [Xmission](https://www.xmission.com/) | - | Yes | Yes | Yes | - | 01/28/15 | | [blackpulsehosting](https://www.blackpulsehosting.com) | - | Yes | Yes | No | - | 10/25/15 | | [MonkeyBrains](https://monkeybrains.net) | AS32329 | Yes | Yes | Yes | Only offers colocation, no cheap VPS option. | 1/14/19 | - - - - --- html: two-columns-page.html ---

1 0

[community/staging] Fix Tor Exit Guidelines link in GoodBadISPs page
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit f1f4a8677b8f50a304344b9f3aa98ceb8d33608b Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:11:41 2019 -0400 Fix Tor Exit Guidelines link in GoodBadISPs page --- content/relay-operations/community-resources/good-bad-isps/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index 0220596..b56d7ce 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -8,7 +8,7 @@ This page aims to list community experiences with Tor and various Internet Servi Be sure to provide useful information like how much bandwidth you pushed, whether you thought the deal was cheap or expensive, how hard you had to work to make them understand what's going on, how long your server has been running, and whether you'd recommend them to others. Also include dates. -Since non-exits do not attract complaints, it should be fine to run them without contacting the hoster first. Make sure you understand their policies regarding bandwidth, especially on "unlimited" (fair use) contracts. For exit relays, you should read the fine [Tor Exit Guidelines](tor-exit-guidelines) first. +Since non-exits do not attract complaints, it should be fine to run them without contacting the hoster first. Make sure you understand their policies regarding bandwidth, especially on "unlimited" (fair use) contracts. For exit relays, you should read the fine [Tor Exit Guidelines](/relay/community-resources/tor-exit-guidelines) first. For network diversity and stronger anonymity, you should avoid providers and countries that already attract a lot of Tor capacity. [Metrics](https://metrics.torproject.org/) is a great tool that allows you to group probabilities by country and AS (autonomous systems), so you can more easily identify networks you want to avoid.

1 0

[community/staging] Point bandwidth amount link to post-install and good practices section
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit f93876ed4cfa3cb4d560027de29de0546e5ade64 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:24:09 2019 -0400 Point bandwidth amount link to post-install and good practices section --- content/relay-operations/relays-requirements/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/relays-requirements/contents.lr b/content/relay-operations/relays-requirements/contents.lr index 6ae3581..0c1808e 100644 --- a/content/relay-operations/relays-requirements/contents.lr +++ b/content/relay-operations/relays-requirements/contents.lr @@ -36,7 +36,7 @@ It is required that a Tor relay be allowed to use a minimum of 100 GByte of outb Note: That is only about 1 day worth of traffic on a 10 Mbit/s (Mbps) connection. More (>2 TB/month) is better and recommended. **Ideally a relay runs on an unmetered plan** or includes 2 TB/month or more. -If you have a metered plan you might want to configure tor to only use a given amount of [bandwidth or monthly traffic](FIXME). +If you have a metered plan you might want to configure tor to only use a given amount of [bandwidth or monthly traffic](/relay/setup/post-install/). # Public IPv4 Address

1 0

[community/staging] Fix link to community legal resources in types of relays
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 06ad1318c7c1ead893d8a44a914be8bfbf1fe097 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:33:10 2019 -0400 Fix link to community legal resources in types of relays --- content/relay-operations/types-of-relays/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/types-of-relays/contents.lr b/content/relay-operations/types-of-relays/contents.lr index 509db57..c4ca5e8 100644 --- a/content/relay-operations/types-of-relays/contents.lr +++ b/content/relay-operations/types-of-relays/contents.lr @@ -50,7 +50,7 @@ Because of the legal exposure that comes with running an exit relay, you should Ideal exit relay operators are affiliated with some institution, like a university, a library, a hackerspace or a privacy related organization. An institution can not only provide greater bandwidth for the exit, but is better positioned to handle abuse complaints or the rare law enforcement inquiry. -If you are considering running an exit relay, please read the [section on legal considerations](community-resources) for exit relay operators. +If you are considering running an exit relay, please read the [section on legal considerations](/relay/community-resources) for exit relay operators. # Bridge

1 0

[community/staging] Remove torservers.net email from contact and redirect to tor-relays mailing list
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 72b28ab50ddc502d4fdc2516199392a7e07e6e8e Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:43:47 2019 -0400 Remove torservers.net email from contact and redirect to tor-relays mailing list --- .../community-resources/tor-exit-guidelines/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr index 120716f..3165b23 100644 --- a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr +++ b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr @@ -92,7 +92,7 @@ In your reply, state clearly that you are not liable for forwarded content passi One of the biggest reasons exit relays disappear is because the people answering the abuse address get nervous and ask you to stop. If you can get your own IP block, great. Even if not, many providers will still reassign subblocks to you if you ask. ARIN uses [SWIP](https://www.arin.net/resources/request/reassignments.html), and RIPE uses something similar. You can also add comments to your range, hinting at your usage as anonymization service ([Example](https://apps.db.ripe.net/search/query.html?searchtext=ZWIEBELFREUN…) -If you have questions about the process, please write an email to support(a)torservers.net and we will try to explain the process to you. +If you have questions about the process, please write an email to [tor-relays mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays) and we will try to explain the process to you. ### Register a phone number and a fax number as abuse contact.

1 0

[community/staging] Make comment consistent with Fedora instructions.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 59b8c7268ff5c50150ec45832f44798a677e7a0c Author: Philipp Winter <phw(a)nymity.ch> Date: Wed Sep 4 12:06:43 2019 -0700 Make comment consistent with Fedora instructions. --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 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 13b3119..949ab1a 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 @@ -85,8 +85,8 @@ Nickname PickANickname * CentOS / RHEL: ``` -sudo semanage port -a -t tor_port_t -p tcp [desired ORPort number set earlier] -sudo semanage port -a -t tor_port_t -p tcp [desired ServerTransportListenAddr port number set earlier] +sudo semanage port -a -t tor_port_t -p tcp [OR port set earlier, in TODO1] +sudo semanage port -a -t tor_port_t -p tcp [obfs4 port set earlier, in TODO2] ``` * CentOS / RHEL / OpenSUSE:

1 0

[community/staging] Improve formatting of instructions.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit fb0c82d4fd39886c3966a7b62b4c1f269bc99469 Author: Philipp Winter <phw(a)nymity.ch> Date: Wed Aug 7 12:25:01 2019 -0700 Improve formatting of instructions. --- .../technical-setup/bridge/docker/contents.lr | 30 ++++++++++------------ 1 file changed, 14 insertions(+), 16 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index 979c0e5..b68770c 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -10,22 +10,20 @@ We are maintaining a docker container that allows you to quickly set up an obfs4 Now, it's time to run the container. You have two options: - * We maintain a script that automatically determines a free OR and obfs4 port for you. The script only requires your email address as argument: - -``` - $ curl https://dip.torproject.org/anti-censorship/docker-obfs4-bridge/raw/master/d… > deploy-container.sh - $ bash deploy-container.sh address(a)email.com -``` - - * If you would rather provide your own ports, run the following command and replace XXX with your OR port, YYY with your obfs4 port, and address(a)email.com with your email address. Don't forget the semicolon after the environment variables. - -``` - OR_PORT=XXX PT_PORT=YYY EMAIL=address(a)email.com; \ - docker run -d \ - -e "OR_PORT=$OR_PORT" -e "PT_PORT=$PT_PORT" -e "EMAIL=$EMAIL" \ - -p "$OR_PORT":"$OR_PORT" -p "$PT_PORT":"$PT_PORT" \ - phwinter/obfs4-bridge:0.1 -``` +1. We maintain a script that automatically determines a free OR and obfs4 port for you. The script only requires your email address as argument: + ``` + $ curl https://dip.torproject.org/torproject/anti-censorship/docker-obfs4-bridge/r… > deploy-container.sh + $ bash deploy-container.sh address(a)email.com + ``` +2. If you would rather provide your own ports, run the following command and replace `XXX` with your OR port, `YYY` with your obfs4 port, and `address(a)example.com` with your email address. Don't forget the semicolon after the environment variables. + + ``` + OR_PORT=XXX PT_PORT=YYY EMAIL=address(a)example.com; \ + docker run -d \ + -e "OR_PORT=$OR_PORT" -e "PT_PORT=$PT_PORT" -e "EMAIL=$EMAIL" \ + -p "$OR_PORT":"$OR_PORT" -p "$PT_PORT":"$PT_PORT" \ + phwinter/obfs4-bridge:0.1 + ``` That's it! Your container should now be bootstrapping your new obfs4 Tor bridge. ---

1 0