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

[community/develop] Add some style in Tor relay universities
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 5889522cab8c35a19a0e7a41e2026a06d9d797cb Author: gus <gus(a)torproject.org> Date: Tue Sep 3 10:59:33 2019 -0400 Add some style in Tor relay universities --- .../community-resources/tor-relay-universities/contents.lr | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/relay-operations/community-resources/tor-relay-universities/contents.lr b/content/relay-operations/community-resources/tor-relay-universities/contents.lr index d8250cc..913f0ce 100644 --- a/content/relay-operations/community-resources/tor-relay-universities/contents.lr +++ b/content/relay-operations/community-resources/tor-relay-universities/contents.lr @@ -85,6 +85,8 @@ This approach has the added benefit that you can draw in other faculty and stude The downside is that your Tor relay's existence is more fragile, since the terms of its demise are already negotiated. Note that in many cases you don't even need to be researching the exit node itself -- doing research on the Tor network requires that there be a Tor network, after all, and keeping it going is a community effort. +## Mailing list + Subscribe to [Tor Relays Universities](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-rel… mailing list (and other education institutions too). --- cta:

1 0

[community/develop] Add missing old FAQ link and oftc.net link
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 2c1979f1e63c9ef1d1411db55a97d2a7a9c2cf26 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:06:18 2019 -0400 Add missing old FAQ link and oftc.net link --- .../tor-relay-universities/contents.lr | 19 ++++++------------- 1 file changed, 6 insertions(+), 13 deletions(-) diff --git a/content/relay-operations/community-resources/tor-relay-universities/contents.lr b/content/relay-operations/community-resources/tor-relay-universities/contents.lr index 913f0ce..a3640bd 100644 --- a/content/relay-operations/community-resources/tor-relay-universities/contents.lr +++ b/content/relay-operations/community-resources/tor-relay-universities/contents.lr @@ -24,8 +24,8 @@ Of course, you need to understand that without actual clear precedent (and even In any case, the key here is to become familiar with the laws and their implications and uncertainties. * Third, learn about Tor's design. -Read the [design overview](https://2019.www.torproject.org/overview.html), the [design paper](https://www.torproject.org/svn/trunk/doc/design-paper/tor-design.htm…, and the [FAQ](FIXME). -Hang out on IRC (irc.oftc.net - #tor-relays) for a while and learn more. +Read the [design overview](https://2019.www.torproject.org/overview.html), the [design paper](https://www.torproject.org/svn/trunk/doc/design-paper/tor-design.htm…, and the [FAQ](https://2019.www.torproject.org/docs/faq.html.en). +Hang out on IRC ([irc.oftc.net](https://www.oftc.net) - #tor-relays) for a while and learn more. If possible, attend a talk by one of the Tor developers. Learn about the types of people and organizations who need secure communications on the Internet. Practice explaining Tor and its benefits and consequences to friends and neighbors -- the [abuse FAQ](https://2019.www.torproject.org/faq-abuse) may provide some helpful starting points. @@ -64,20 +64,13 @@ You might let them know that there are ways you can dial down the potential for You'll also want to learn if there are bandwidth limitations at your organization. (Tor can handle a variety of rate limiting approaches, so this isn't the end of the world). -In some cases, you should talk to the network security people before you talk to the lawyers; in some cases, there will be yet other groups that will be critical to educate and bring into the discussion. -You'll have to make it up as you go. +In some cases, you should talk to the network security people before you talk to the lawyers; in some cases, there will be yet other groups that will be critical to educate and bring into the discussion. You'll have to make it up as you go. If the authorities contact your university for logs, be pleasant and helpful. Tor's default log level doesn't provide much that's useful, so if they want copies of your logs, that's fine. -Be helpful and take the opportunity to explain to them about Tor and why it's useful to the world. -(If they contact you directly for logs, you should send them to -your university's lawyers -- acting on it yourself is [almost always a poor idea](/relay/community-resources/eff-tor-legal-faq/). - -If there are too many complaints coming in, there are several approaches you can take to reduce them. -First, you should follow the tips in the [Tor relay documentation](https://community.torproject.org/relay), such -as picking a descriptive hostname or getting your own IP address. -If that doesn't work, you can scale back the advertised speed of your relay, by using the Max``Advertised``Bandwidth to attract less traffic from the Tor network. -Lastly, you can scale back your exit policy. +Be helpful and take the opportunity to explain to them about Tor and why it's useful to the world. (If they contact you directly for logs, you should send them to your university's lawyers -- acting on it yourself is [almost always a poor idea](/relay/community-resources/eff-tor-legal-faq/). + +If there are too many complaints coming in, there are several approaches you can take to reduce them. First, you should follow the tips in the [Tor relay documentation](https://community.torproject.org/relay), such as picking a descriptive hostname or getting your own IP address. If that doesn't work, you can scale back the advertised speed of your relay, by using the `MaxAdvertisedBandwidth` to attract less traffic from the Tor network. Lastly, you can scale back your exit policy. Some people have found that their university only tolerates their Tor relay if they're involved in a research project around anonymity. So if you're interested, you might want to get that started early in the process -- see our [Research Portal](https://research.torproject.org/).

1 0

[community/develop] Point bandwidth amount link to post-install and good practices section
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit eec6f0c35f0f83f3a0f09aad4a57690d40cb5c17 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/develop] Contact us in frontdesk instead of tor-assistants
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit d872fcbfd054f26d995da52ce3e8c0d6e81c7966 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:58:52 2019 -0400 Contact us in frontdesk instead of tor-assistants --- .../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 3d31bf1..7529051 100644 --- a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr +++ b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr @@ -103,7 +103,7 @@ At least law enforcement in Germany regularly uses the fax and phone numbers pre The [Reduced Exit Policy](https://trac.torproject.org/projects/tor/wiki/doc/ReducedExitPolicy) is an alternative to the default exit policy. It allows many Internet services while still blocking the majority of TCP ports. This drastically reduces the odds that a Bittorrent user will select your node and thus reduces or even eliminates the number of [DMCA complaints](/relay/community-resources/eff-tor-legal-faq/tor-dmca-response/) you will receive. -If you have your own experience of abuse handling, just share it on our public mailing list or write us an email to tor-assistants(a)torproject.org. +If you have your own experience of abuse handling, just share it on our public mailing list or write us an email to frontdesk(a)torproject.org. ## Technical

1 0

[community/develop] Fix Bridge Guide link in relays-requirements
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 26ecc3e1906d5aa9faf11f748c3b660cfeb89440 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:20:02 2019 -0400 Fix Bridge Guide link in relays-requirements --- 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 4def53f..ccee8c3 100644 --- a/content/relay-operations/relays-requirements/contents.lr +++ b/content/relay-operations/relays-requirements/contents.lr @@ -27,7 +27,7 @@ Fast exit relays (>=100 Mbit/s) usually have to handle a lot more concurrent con It is recommended that a relay have at least 16 Mbit/s (Mbps) upload bandwidth and 16 Mbit/s (Mbps) download bandwidth available for Tor. More is better. The minimum requirements for a relay are 10 Mbit/s (Mbps). -If you have less than 10 Mbit/s but at least 1 Mbit/s we recommend you run a [bridge with obfs4 support](relay/bridge). +If you have less than 10 Mbit/s but at least 1 Mbit/s we recommend you run a [bridge with obfs4 support](relay/setup/bridge). If you do not know your bandwidth you can use http://beta.speedtest.net to measure it. # Monthly Outbound Traffic

1 0

[community/develop] Remove torservers.net email from contact and redirect to tor-relays mailing list
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 0e646488eba511745059651387c04b19c3f41db3 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/develop] Use TODO1 and TODO2 to highlight port difference.
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 9c4a145f24f74bcf6dc10fe5118c06e2dc7626d4 Author: Philipp Winter <phw(a)nymity.ch> Date: Tue Sep 3 08:45:32 2019 -0700 Use TODO1 and TODO2 to highlight port difference. We don't want people to think that the OR port and obfs4 port are supposed to be the same. Thanks to Ken Kundert for pointing out this issue and for fixing it for CentOS/RHEL/OpenSuSE in commit a6a8c35. --- .../technical-setup/bridge/debian-ubuntu/contents.lr | 12 +++++++----- .../technical-setup/bridge/freebsd/contents.lr | 11 ++++++----- .../technical-setup/bridge/openbsd/contents.lr | 11 ++++++----- 3 files changed, 19 insertions(+), 15 deletions(-) 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 eed3be8..b97259c 100644 --- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr @@ -25,16 +25,18 @@ If not, you can [build it from source](https://gitlab.com/yawning/obfs4#installa ``` BridgeRelay 1 -# Replace "TODO" with a Tor port of your choice. This port must be externally +# Replace "TODO1" with a Tor port of your choice. This port must be externally # reachable. Avoid port 9001 because it's commonly associated with Tor and # censors may be scanning the Internet for this port. -ORPort TODO +ORPort TODO1 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy -# Replace "TODO" with an obfs4 port of your choice. This port must be externally reachable. -# Avoid port 9001 because it's commonly associated with Tor and censors may be scanning the Internet for this port. -ServerTransportListenAddr obfs4 0.0.0.0:TODO +# 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. +# Avoid port 9001 because it's commonly associated with +# Tor and censors may be scanning the Internet for this port. +ServerTransportListenAddr obfs4 0.0.0.0:TODO2 # Local communication port between Tor and obfs4. Always set this to "auto". # "Ext" means "extended", not "external". Don't try to set a specific port number, nor listen on 0.0.0.0. diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index 862551a..951ef31 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -22,17 +22,18 @@ pkg install obfs4proxy-tor tor ca_root_nss RunAsDaemon 1 BridgeRelay 1 -# Replace "TODO" with a Tor port of your choice. This port must be externally +# Replace "TODO1" with a Tor port of your choice. This port must be externally # reachable. Avoid port 9001 because it's commonly associated with Tor and # censors may be scanning the Internet for this port. -ORPort TODO +ORPort TODO1 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy -# Replace "TODO" with an obfs4 port of your choice. This port must be -# externally reachable. Avoid port 9001 because it's commonly associated with +# 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. +# Avoid port 9001 because it's commonly associated with # Tor and censors may be scanning the Internet for this port. -ServerTransportListenAddr obfs4 0.0.0.0:TODO +ServerTransportListenAddr obfs4 0.0.0.0:TODO2 # Local communication port between Tor and obfs4. Always set this to "auto". # "Ext" means "extended", not "external". Don't try to set a specific port diff --git a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr index 96ffc95..50d1a26 100644 --- a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr @@ -21,17 +21,18 @@ 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 +# Replace "TODO1" with a Tor port of your choice. This port must be externally # reachable. Avoid port 9001 because it's commonly associated with Tor and # censors may be scanning the Internet for this port. -ORPort TODO +ORPort TODO1 ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy -# Replace "TODO" with an obfs4 port of your choice. This port must be -# externally reachable. Avoid port 9001 because it's commonly associated with +# 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. +# Avoid port 9001 because it's commonly associated with # Tor and censors may be scanning the Internet for this port. -ServerTransportListenAddr obfs4 0.0.0.0:TODO +ServerTransportListenAddr obfs4 0.0.0.0:TODO2 # Local communication port between Tor and obfs4. Always set this to "auto". # "Ext" means "extended", not "external". Don't try to set a specific port

1 0

[community/develop] Add some formatting and remove trailing spaces
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 593f3c871030b615bf38d479c6e35202664ac783 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/develop] Fix link to community legal resources in types of relays
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit a99e93dc069de62f56a9c1418371a7259e3b2dbf 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/develop] Add link to GoodBadISPs page
by hiro＠torproject.org 18 Sep '19

18 Sep '19

commit 7787fbe53006eff8a12de10ea016f053704791f1 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:28:02 2019 -0400 Add link to GoodBadISPs page --- content/relay-operations/technical-considerations/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-considerations/contents.lr b/content/relay-operations/technical-considerations/contents.lr index cb76e73..d2760c0 100644 --- a/content/relay-operations/technical-considerations/contents.lr +++ b/content/relay-operations/technical-considerations/contents.lr @@ -17,7 +17,7 @@ If you do not own physical hardware, you could run a relay on a rented dedicated This can cost anywhere between $3.00/month and thousands per month, depending on your provider, hardware configuration, and bandwidth usage. Many VPS providers will not allow you to run exit relays. You must follow the VPS provider's terms of service, or risk having your account disabled. -For more information on hosting providers and their policies on allowing Tor relays, please see this list maintained by the Tor community: [GoodBadISPs](FIXME). +For more information on hosting providers and their policies on allowing Tor relays, please see this list maintained by the Tor community: [GoodBadISPs](/relay/community-resources/good-bad-isps). ## Questions to consider when choosing a host

1 0