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

[community/master] Fix EFF Legal Faq link
by emmapeel＠torproject.org 03 Sep '19

03 Sep '19

commit 6fae30e967fe2e48f22ef35825ee6449f96cedd4 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 10:22:41 2019 -0400 Fix EFF Legal Faq link --- .../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 9ba85fb..9c43196 100644 --- a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr +++ b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr @@ -53,7 +53,7 @@ If you country is missing here and you know a lawyer who can provide a legal opi ### If you're part of an organization that will be running the exit relay (ISP, university etc), consider teaching your legal people about Tor. -It's way better for them to hear about Tor from you, in a relaxed environment, than to hear about it from a stranger over the phone. Make them aware of [EFF's Legal FAQ for Tor Operators](https://2019.www.torproject.org/eff/tor-legal-faq). EFF has also offered to talk to other lawyers to explain the legal aspects of Tor. +It's way better for them to hear about Tor from you, in a relaxed environment, than to hear about it from a stranger over the phone. Make them aware of [EFF's Legal FAQ for Tor Operators](/relay/community-resources/eff-tor-legal-faq). EFF has also offered to talk to other lawyers to explain the legal aspects of Tor. ### If you're not part of an organization, think about starting one!

1 0

[community/master] Replace URL to EFF Legal guide and fix new relay-operations slug
by emmapeel＠torproject.org 03 Sep '19

03 Sep '19

commit 7590fb904e8c53adeee08e08f4119eda14099954 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 10:57:43 2019 -0400 Replace URL to EFF Legal guide and fix new relay-operations slug --- .../community-resources/tor-relay-universities/contents.lr | 6 +++--- 1 file changed, 3 insertions(+), 3 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 df6149f..d8250cc 100644 --- a/content/relay-operations/community-resources/tor-relay-universities/contents.lr +++ b/content/relay-operations/community-resources/tor-relay-universities/contents.lr @@ -46,7 +46,7 @@ Ask for advice from everybody you meet who likes the idea, and try to work your * Sixth, teach your university's lawyers about Tor. This may seem like a risky move, but it's way better for them to hear about Tor from you, in a relaxed environment, than to hear about it from a stranger over the phone. -Remember that lawyers don't like being told how to interpret laws by a non-lawyer, but they are often pleased to hear that other lawyers have done a lot of the research and leg-work (this is where [the EFF's legal FAQ](https://2019.www.torproject.org/eff/tor-legal-faq) comes in, along with your law school contacts if you found any). +Remember that lawyers don't like being told how to interpret laws by a non-lawyer, but they are often pleased to hear that other lawyers have done a lot of the research and leg-work (this is where [the EFF's legal FAQ](/relay/community-resources/eff-tor-legal-faq/) comes in, along with your law school contacts if you found any). Make sure to keep these discussions informal and small -- invite one of the general counsel out to coffee to discuss "something neat that may come up later on." Feel free to bring along one of the allies you found above, if it makes you more comfortable. Avoid having actual meetings or long email discussions, and make it clear that you don't need their official legal opinion yet. Remember that lawyers are paid to say no unless they have a reason to say yes, so when the time finally comes to ask their opinion on running a Tor exit node, make sure the question is not "are there any liability issues?", but rather "we'd like to do this, can you help us avoid the biggest issues?" Try to predict what they will say, and try to gain allies among the lawyers who like your cause and want to help. @@ -71,10 +71,10 @@ 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](https://2019.www.torproject.org/eff/tor-legal-faq.html#RequestForLogs). +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-operations), such +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.

1 0

[community/master] Add some style in Tor relay universities
by emmapeel＠torproject.org 03 Sep '19

03 Sep '19

commit 3c9b0563e0d5e0c6e424117ce6cccbbe575cef5c 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/master] Fix Tor Exit Guidelines link in GoodBadISPs page
by emmapeel＠torproject.org 03 Sep '19

03 Sep '19

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/master] Add missing old FAQ link and oftc.net link
by emmapeel＠torproject.org 03 Sep '19

03 Sep '19

commit b52b3170393186d1298b9f4ef20e5605ae7c038e 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/master] Add some formatting and remove trailing spaces
by emmapeel＠torproject.org 03 Sep '19

03 Sep '19

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/master] Add link to GoodBadISPs page
by emmapeel＠torproject.org 03 Sep '19

03 Sep '19

commit 480c416be0bff97570f6d161ba88389cc150f769 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

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

03 Sep '19

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/master] Following our Relay Guide, the ideal monthly Outbound Traffic is 2 TB and not 20 TB
by emmapeel＠torproject.org 03 Sep '19

03 Sep '19

commit 5bdfc276a083029f4317b26576d0fa25122b18c2 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:21:41 2019 -0400 Following our Relay Guide, the ideal monthly Outbound Traffic is 2 TB and not 20 TB --- 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 ccee8c3..6ae3581 100644 --- a/content/relay-operations/relays-requirements/contents.lr +++ b/content/relay-operations/relays-requirements/contents.lr @@ -35,7 +35,7 @@ If you do not know your bandwidth you can use http://beta.speedtest.net to measu It is required that a Tor relay be allowed to use a minimum of 100 GByte of outbound traffic (and the same amount of incoming traffic) per month. 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 20 TB/month or more. +**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). # Public IPv4 Address

1 0

[community/master] Fix Bridge Guide link in relays-requirements
by emmapeel＠torproject.org 03 Sep '19

03 Sep '19

commit 2c9cb75b940e330d3d21efad81b464a7b6273e88 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