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

[community/develop] Fix link to Tor abuse templates in DMCA template
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit 79846b321c2ca5d59f5afc48914fde1dbcb80792 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 10:12:03 2019 -0400 Fix link to Tor abuse templates in DMCA template --- .../community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr b/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr index 3be4b05..e844d39 100644 --- a/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr +++ b/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr @@ -6,7 +6,7 @@ body: Written by the Electronic Frontier Foundation ([EFF](https://www.eff.org/)) Last updated May 31, 2011. -Note to Tor relay operators: In this litigious era, anyone providing routing services may face copyright complaints for transmitted content. Fortunately, the Digital Millennium Copyright Act safe harbors should provide protections from many of them both to you and to your upstream provider. If your Internet host forwards a DMCA copyright complaint to you, you can use this template to write a response, though you will need to customize it to your situation. Please also ensure all the statements are true for you. (The Tor Project has an [abuse collection of templates](/tor-abuse-templates/) to help you respond to other types of abuse complaints, too.) Before sending any response to your ISP, you may want to seek the advice of an attorney licensed to practice in your jurisdiction. +Note to Tor relay operators: In this litigious era, anyone providing routing services may face copyright complaints for transmitted content. Fortunately, the Digital Millennium Copyright Act safe harbors should provide protections from many of them both to you and to your upstream provider. If your Internet host forwards a DMCA copyright complaint to you, you can use this template to write a response, though you will need to customize it to your situation. Please also ensure all the statements are true for you. (The Tor Project has an [abuse collection of templates](/relay/community-resources/tor-abuse-templates/) to help you respond to other types of abuse complaints, too.) Before sending any response to your ISP, you may want to seek the advice of an attorney licensed to practice in your jurisdiction. This template letter is for informational purposes only and does not constitute legal advice. Whether and how you should respond when you or your ISP has received a DMCA notice will turn on the particular facts of your situation. This template is intended as a starting point, but you should tailor it to your own circumstances. In addition, it's up to you to comply with your ISP's terms of service. If you're not comfortable including so much legal explanation, feel free to invite the ISP to contact EFF for a fuller discussion.

1 0

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

05 Oct '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/develop] Replace urls to EFF Legal guide
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit be5d0a42ecb363741ff4226001abf2cacb625119 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 10:55:15 2019 -0400 Replace urls to EFF Legal guide --- .../community-resources/tor-relay-universities/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 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 6aba040..df6149f 100644 --- a/content/relay-operations/community-resources/tor-relay-universities/contents.lr +++ b/content/relay-operations/community-resources/tor-relay-universities/contents.lr @@ -17,8 +17,8 @@ Most likely it is ambiguously worded, to let them allow or deny things based on But it might be extremely restrictive ("no services of any kind"), in which case you're going to have a tough road ahead of you. * Second, learn about your local laws with respect to liability of traffic that exits from your Tor relay. -In the US, these appear to be mainly the [DMCA](https://2019.www.torproject.org/eff/tor-legal-faq.html#DMCA) and [CDA](https://2019.www.torproject.org/eff/tor-legal-faq.html#Lawsuits), and the good news is that many lawyers believe that Tor exit node operators are in the same boat as the ISPs themselves. -Become familiar with [the EFF's template letter regarding DMCA notices for Tor](https://2019.www.torproject.org/eff/tor-dmca-response.html), which is quite clear about not putting liability on service providers. +In the US, these appear to be mainly the [DMCA](/relay/community-resources/eff-tor-legal-faq/) and [CDA](/relay/community-resources/eff-tor-legal-faq/), and the good news is that many lawyers believe that Tor exit node operators are in the same boat as the ISPs themselves. +Become familiar with [the EFF's template letter regarding DMCA notices for Tor](/relay/community-resources/eff-tor-legal-faq/tor-dmca-response/), which is quite clear about not putting liability on service providers. The CDA is less clear, because it was written before the modern Internet emerged, but EFF and ACLU are optimistic. Of course, you need to understand that without actual clear precedent (and even then), it's still possible that a given judge will not interpret things the way the lawyers expect. In any case, the key here is to become familiar with the laws and their implications and uncertainties.

1 0

[community/develop] Replace full email with tshirt AT torproject
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit ac432a004f1cb8ec864ee293e71ee02bea6a6ce3 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 10:19:03 2019 -0400 Replace full email with tshirt AT torproject --- content/relay-operations/community-resources/swag/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/swag/contents.lr b/content/relay-operations/community-resources/swag/contents.lr index 28f6583..b1c1419 100644 --- a/content/relay-operations/community-resources/swag/contents.lr +++ b/content/relay-operations/community-resources/swag/contents.lr @@ -10,7 +10,7 @@ You can get one of these fine Tor T-shirts for contributing to the Tor project. * Help out in other ways. Maintain a translation. Run Tor trainings. Write a good support program and get a lot of people to use it. Do research on Tor and anonymity, solve some of our bugs, or establish yourself as a Tor advocate. -If you're operating a fast relay or you've done something else cool, email us at tshirt(a)torproject.org with the details. (We want to make sure our shirts help outreach happen all around the world, so please understand if we can't send you 5 shirts for your 5 excellent relays.) +If you're operating a fast relay or you've done something else cool, email us at tshirt at torproject.org with the details. (We want to make sure our shirts help outreach happen all around the world, so please understand if we can't send you 5 shirts for your 5 excellent relays.) There are a variety of colors, shapes, and sizes available in the great roots design that Leiah Jansen made for us, as well as some older designs. ---

1 0

[community/develop] Fix EFF Legal Faq link
by emmapeel＠torproject.org 05 Oct '19

05 Oct '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/develop] Add some formatting and remove trailing spaces
by emmapeel＠torproject.org 05 Oct '19

05 Oct '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/develop] Fix Tor Exit Guidelines link in GoodBadISPs page
by emmapeel＠torproject.org 05 Oct '19

05 Oct '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/develop] Fix Bridge Guide link in relays-requirements
by emmapeel＠torproject.org 05 Oct '19

05 Oct '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

[community/develop] Add link to Tor relay universities page
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit e88310010cd9a3027aa0ced5f439466edb94d07c Author: gus <gus(a)torproject.org> Date: Tue Sep 3 10:24:18 2019 -0400 Add link to Tor relay universities page --- .../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 9c43196..120716f 100644 --- a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr +++ b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr @@ -17,7 +17,7 @@ Therefore, please do not act on this information alone; if you have any specific Find some professors (or deans!) who like the idea of supporting and/or researching anonymity on the Internet. If possible, use an extra IP range whose abuse contact doesn't go through the main university abuse team. Ideally, use addresses that are not trusted by the IP-based authentication many library-related services use -- if the university's entire IP address space is "trusted" to access these library resources, the university is forced to maintain an iron grip on all its addresses. -Also read [How do I make my University / ISP / etc happy with my exit node?](tor-relay-universities) +Also read [How do I make my University / ISP / etc happy with my exit node?](/relay/community-resources/tor-relay-universities/) ### Find Tor-friendly ISPs.

1 0

[community/develop] Removed torservers.net email contact
by emmapeel＠torproject.org 05 Oct '19

05 Oct '19

commit d511f72cb289f51f4c1018c7d127436115b3a5c5 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 10:21:28 2019 -0400 Removed torservers.net email contact --- .../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 64e60d3..9ba85fb 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; contact us at support(a)torservers.net and we'll make the connections for you. +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. ### If you're not part of an organization, think about starting one!

1 0