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

[community/staging] Replace urls to EFF Legal guide
by hiro＠torproject.org 21 Mar '21

21 Mar '21

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/staging] Fix Bridge Guide link in relays-requirements
by hiro＠torproject.org 21 Mar '21

21 Mar '21

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/staging] Replace URL to EFF Legal guide and fix new relay-operations slug
by hiro＠torproject.org 21 Mar '21

21 Mar '21

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/staging] Following our Relay Guide, the ideal monthly Outbound Traffic is 2 TB and not 20 TB
by hiro＠torproject.org 21 Mar '21

21 Mar '21

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/staging] Merge branch 'patch-2' of github.com:BunnyApocalypse/community into patch-2
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 7557129f320138495efa87a1a52832834e4637bf Merge: 4577ba8 7400359 Author: Philipp Winter <phw(a)nymity.ch> Date: Tue Sep 3 08:54:41 2019 -0700 Merge branch 'patch-2' of github.com:BunnyApocalypse/community into patch-2 .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

1 0

[community/staging] Remove Fedora Instructions
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 4d3ac1c968573db19831d8ea7b9d811884be74c4 Author: Christopher King <bunnyapocalypse(a)protonmail.com> Date: Tue Sep 3 16:15:35 2019 +0000 Remove Fedora Instructions Fair enough, that all makes sense. I removed all of the Fedora stuff but kept the parts relevant to RHEL / CentOS. --- .../bridge/centos-rhel-opensuse/contents.lr | 46 +--------------------- 1 file changed, 1 insertion(+), 45 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 915cfa6..521ed71 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 @@ -21,12 +21,6 @@ yum install git golang tor policycoreutils-python-utils zypper install tor go git ``` -* Fedora: - -``` -dnf install git golang tor policycoreutils-python-utils -``` - ### 2. Build obfs4proxy and move it into place. Heavily outdated versions of git can make `go get` fail, so try upgrading to a more recent git version if you're running into this problem. @@ -48,14 +42,6 @@ go get gitlab.com/yawning/obfs4.git/obfs4proxy sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/ ``` -* Fedora: - -``` -export GOPATH=`mktemp -d` -go get gitlab.com/yawning/obfs4.git/obfs4proxy -sudo cp $GOPATH/bin/obfs4proxy /usr/bin/ -``` - ### 3. Edit your Tor config file, usually located at `/etc/tor/torrc` and replace its content with: * CentOS / RHEL / OpenSUSE: @@ -85,36 +71,6 @@ ExtORPort auto # there are problems with your bridge. This is optional but encouraged. ContactInfo <address(a)email.com> -# Pick a nickname that you like for your bridge. This is optional. -Nickname PickANickname -``` -* Fedora: - -``` -RunAsDaemon 1 -BridgeRelay 1 - -# Replace "TODO" 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 - -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 - -# 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. -ExtORPort auto - -# Replace "<address(a)email.com>" with your email address so we can contact you if -# there are problems with your bridge. This is optional but encouraged. -ContactInfo <address(a)email.com> - # Pick a nickname that you like for your bridge. This is optional. Nickname PickANickname ``` @@ -129,7 +85,7 @@ Nickname PickANickname `systemctl restart tor` -* Fedora / RHEL / CentOS: +* RHEL / CentOS: ``` sudo semanage port -a -t tor_port_t -p tcp [desired ORPort number set earlier]

1 0

[community/staging] Add full url path to EFF Legal FAQ
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 02bc5b618bf97bc8b7e5d43fe967df9469c19927 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 12:00:52 2019 -0400 Add full url path to EFF Legal FAQ --- .../community-resources/tor-abuse-templates/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr index 2af9f6b..0e37f24 100644 --- a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr +++ b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr @@ -212,7 +212,7 @@ If a serious abuse complaint not covered by this template set arrives, the best ## Other Template Sets - * [DMCA Response template for Tor node maintainer to ISP](community-resources/eff-tor-legal-faq/) as written by the [EFF](http://www.eff.org). + * [DMCA Response template for Tor node maintainer to ISP](/relay/community-resources/eff-tor-legal-faq/) as written by the [EFF](http://www.eff.org). * Torservers [response template emails](https://www.torservers.net/wiki/abuse/templates). --- html: two-columns-page.html

1 0

[community/staging] Merge branch 'patch-1' of github.com:KenKundert/community into patch-1
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit e425b9886bc256f5294a4797f5182a54d20180de Merge: 6c837c7 a6a8c35 Author: Philipp Winter <phw(a)nymity.ch> Date: Tue Sep 3 08:42:51 2019 -0700 Merge branch 'patch-1' of github.com:KenKundert/community into patch-1 .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-)

1 0

[community/staging] Add link to GoodBadISPs page
by hiro＠torproject.org 21 Mar '21

21 Mar '21

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/staging] Link to EFF DMCA response template
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 3d224994502c9176d4047fe0966c580979b84792 Author: gus <gus(a)torproject.org> Date: Tue Sep 3 11:58:12 2019 -0400 Link to EFF DMCA response template --- .../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 ddbddef..3d31bf1 100644 --- a/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr +++ b/content/relay-operations/community-resources/tor-exit-guidelines/contents.lr @@ -101,7 +101,7 @@ At least law enforcement in Germany regularly uses the fax and phone numbers pre ### Consider using the Reduced Exit Policy. 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](https://2019.www.torproject.org/eff/tor-dmca-response) you will receive. +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.

1 0