tor-commits March 2021

tor-commits@lists.torproject.org

17 participants
2169 discussions

[community/staging] Add a "getting help" section.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 7a3125ff555c6b656ef131475f419f0c440bb4fc Author: Philipp Winter <phw(a)nymity.ch> Date: Wed Aug 7 11:54:23 2019 -0700 Add a "getting help" section. --- .../technical-setup/bridge/getting-help/contents.lr | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/content/relay-operations/technical-setup/bridge/getting-help/contents.lr b/content/relay-operations/technical-setup/bridge/getting-help/contents.lr new file mode 100644 index 0000000..828d351 --- /dev/null +++ b/content/relay-operations/technical-setup/bridge/getting-help/contents.lr @@ -0,0 +1,16 @@ +_model: page +--- +title: Getting help +--- +body: + +If you run into problems while setting up your relay, you can ask your questions on the public [tor-relays mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays). The list is a great resource for asking (and answering) questions, and for getting to know other relay operators. Make sure to check out the archives! + +You can also get help by joining the IRC channel #tor-relays in the network [irc.oftc.net](https://www.oftc.net). + +--- +html: two-columns-page.html +--- +key: 7 +--- +subtitle: How to get help if you run into issues

1 0

[community/staging] Use port 3818 instead of 9001 in our example log.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 3cb1c18146838a1c0d54be462bedd7869fa88e3c Author: Philipp Winter <phw(a)nymity.ch> Date: Wed Aug 7 12:34:39 2019 -0700 Use port 3818 instead of 9001 in our example log. Port 9001 should not be used for a bridge. --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 2 +- .../relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr | 2 +- content/relay-operations/technical-setup/bridge/freebsd/contents.lr | 2 +- content/relay-operations/technical-setup/bridge/openbsd/contents.lr | 2 +- 4 files changed, 4 insertions(+), 4 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 32fe769..a3370a4 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 @@ -89,7 +89,7 @@ To confirm your bridge is running with no issues, you should see something like [notice] Registered server transport 'obfs4' at '[::]:46396' [notice] Tor has successfully opened a circuit. Looks like client functionality is working. [notice] Bootstrapped 100%: Done -[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) +[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. ``` 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 ea88cc7..913eab8 100644 --- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr @@ -75,7 +75,7 @@ To confirm your bridge is running with no issues, you should see something like [notice] Registered server transport 'obfs4' at '[::]:46396' [notice] Tor has successfully opened a circuit. Looks like client functionality is working. [notice] Bootstrapped 100%: Done -[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) +[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. ``` --- diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index 5353d5c..fe3c09c 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -75,7 +75,7 @@ To confirm your bridge is running with no issues, you should see something like [notice] Registered server transport 'obfs4' at '[::]:46396' [notice] Tor has successfully opened a circuit. Looks like client functionality is working. [notice] Bootstrapped 100%: Done -[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) +[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. ``` diff --git a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr index f9c98e9..63d8c73 100644 --- a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr @@ -70,7 +70,7 @@ To confirm your bridge is running with no issues, you should see something like [notice] Registered server transport 'obfs4' at '[::]:46396' [notice] Tor has successfully opened a circuit. Looks like client functionality is working. [notice] Bootstrapped 100%: Done -[notice] Now checking whether ORPort <redacted>:9001 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) +[notice] Now checking whether ORPort <redacted>:3818 is reachable... (this may take up to 20 minutes -- look for log messages indicating success) [notice] Self-testing indicates your ORPort is reachable from the outside. Excellent. Publishing server descriptor. ``` ---

1 0

[community/staging] Merge branch 'obfs4-guide-overhaul'
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit db961cbce7e9e83e1043f5cc429add7bffbdf92c Merge: 1750421 60c4428 Author: Philipp Winter <phw(a)nymity.ch> Date: Wed Aug 7 12:59:29 2019 -0700 Merge branch 'obfs4-guide-overhaul' .../bridge/centos-rhel-opensuse/contents.lr | 6 ++-- .../technical-setup/bridge/contents.lr | 6 ++-- .../bridge/debian-ubuntu/contents.lr | 10 +++---- .../technical-setup/bridge/docker/contents.lr | 32 +++++++++++----------- .../technical-setup/bridge/freebsd/contents.lr | 6 ++-- .../bridge/getting-help/contents.lr | 16 +++++++++++ .../technical-setup/bridge/openbsd/contents.lr | 6 ++-- .../bridge/post-install/contents.lr | 4 +-- 8 files changed, 52 insertions(+), 34 deletions(-)

1 0

[community/staging] Improve minor phrasing issues.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit fbb69822b72aef2623f148b20d783e8c402ae991 Author: Philipp Winter <phw(a)nymity.ch> Date: Wed Aug 7 12:33:03 2019 -0700 Improve minor phrasing issues. --- .../relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 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 f5f7930..ea88cc7 100644 --- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr @@ -12,7 +12,7 @@ Get the latest version of Tor. If you're on Debian stable, `sudo apt-get install ### 2. Install obfs4proxy -On [Debian](https://packages.debian.org/search?keywords=obfs4proxy), the `obfs4proxy` package is available in sid, buster, and stretch. On [Ubuntu](https://packages.ubuntu.com/search?keywords=obfs4proxy), bionic, cosmic, disco, and eoan have the package. If you're running any of them, `sudo apt-get install obfs4proxy` should work. +On [Debian](https://packages.debian.org/search?keywords=obfs4proxy), the `obfs4proxy` package is available in unstable, testing, and stable. On [Ubuntu](https://packages.ubuntu.com/search?keywords=obfs4proxy), bionic, cosmic, disco, and eoan have the package. If you're running any of them, `sudo apt-get install obfs4proxy` should work. If not, you can [build it from source](https://gitlab.com/yawning/obfs4#installation). @@ -56,7 +56,7 @@ Nickname PickANickname `sudo setcap cap_net_bind_service=+ep /usr/bin/obfs4proxy` -* Under Debian, you will also need to set `NoNewPrivileges=no` in `/lib/systemd/system/tor(a)default.service` and `/lib/systemd/system/tor@.service` and then run `systemctl daemon-reload`. [bug #18356](https://trac.torproject.org/projects/tor/ticket/18356) +* Under Debian, you will also need to set `NoNewPrivileges=no` in `/lib/systemd/system/tor(a)default.service` and `/lib/systemd/system/tor@.service` and then run `systemctl daemon-reload`. (see [bug #18356](https://trac.torproject.org/projects/tor/ticket/18356)) * Note that both Tor's OR port and its obfs4 port must be reachable. If your bridge is behind a firewall or NAT, make sure to open both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet.

1 0

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

21 Mar '21

commit 60c4428b637002aa4dec9838070f9adcafe6d46e Author: Philipp Winter <phw(a)nymity.ch> Date: Wed Aug 7 12:57:42 2019 -0700 Improve formatting and phrasing. --- content/relay-operations/technical-setup/bridge/contents.lr | 6 ++++-- .../technical-setup/bridge/post-install/contents.lr | 2 +- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/contents.lr b/content/relay-operations/technical-setup/bridge/contents.lr index c83b3e6..c1175cd 100644 --- a/content/relay-operations/technical-setup/bridge/contents.lr +++ b/content/relay-operations/technical-setup/bridge/contents.lr @@ -6,9 +6,11 @@ title: --- body: -This guide will help you run an obfs4 bridge to help censored users connect to the Tor network. The requirements are 1) 24/7 Internet connectivity and 2) the ability to expose TCP ports to the Internet (make sure that NAT doesn't get in the way). +This guide will help you set up an obfs4 bridge to help censored users connect to the Tor network. The requirements are: +1. 24/7 Internet connectivity +2. The ability to expose TCP ports to the Internet (make sure that NAT doesn't get in the way) -Note: If you're running platforms that are not listed on this page, you should probably [compile obfs4 from source](https://gitlab.com/yawning/obfs4#installation). +Note: If you're running a platform that is not listed on this page, you can [compile obfs4 from source](https://gitlab.com/yawning/obfs4#installation). --- html: two-columns-page.html --- diff --git a/content/relay-operations/technical-setup/bridge/post-install/contents.lr b/content/relay-operations/technical-setup/bridge/post-install/contents.lr index 23825a5..d95da88 100644 --- a/content/relay-operations/technical-setup/bridge/post-install/contents.lr +++ b/content/relay-operations/technical-setup/bridge/post-install/contents.lr @@ -23,4 +23,4 @@ html: two-columns-page.html --- key: 6 --- -subtitle: How to find your Bridge in Relay Search and connect manually +subtitle: How to find your bridge in Relay Search and connect manually

1 0

[community/staging] Be more specific about how file should be edited.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 6fcb36c082d16a7e48e8064474828e9e8ea3d80a Author: Philipp Winter <phw(a)nymity.ch> Date: Wed Aug 7 12:37:28 2019 -0700 Be more specific about how file should be edited. --- .../technical-setup/bridge/centos-rhel-opensuse/contents.lr | 2 +- .../relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr | 2 +- content/relay-operations/technical-setup/bridge/freebsd/contents.lr | 2 +- content/relay-operations/technical-setup/bridge/openbsd/contents.lr | 2 +- 4 files changed, 4 insertions(+), 4 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 a3370a4..14d6e04 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 @@ -40,7 +40,7 @@ go get gitlab.com/yawning/obfs4.git/obfs4proxy sudo cp $GOPATH/bin/obfs4proxy /usr/local/bin/ ``` -### 3. Edit your Tor config file, usually located at `/etc/tor/torrc` and add the following lines: +### 3. Edit your Tor config file, usually located at `/etc/tor/torrc` and replace its content with: ``` RunAsDaemon 1 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 913eab8..cf83c8d 100644 --- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr @@ -17,7 +17,7 @@ On [Debian](https://packages.debian.org/search?keywords=obfs4proxy), the `obfs4p If not, you can [build it from source](https://gitlab.com/yawning/obfs4#installation). -### 3. Edit your Tor config file, usually located at `/etc/tor/torrc` and add the following lines: +### 3. Edit your Tor config file, usually located at `/etc/tor/torrc` and replace its content with: ``` RunAsDaemon 1 diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index fe3c09c..3fdee50 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -14,7 +14,7 @@ body: pkg install obfs4proxy-tor tor ca_root_nss ``` -### 2. Edit your Tor config file, usually located at `/usr/local/etc/tor` and add the following lines +### 2. Edit your Tor config file, usually located at `/usr/local/etc/tor` and replace its content with: ``` RunAsDaemon 1 diff --git a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr index 63d8c73..bf7d98a 100644 --- a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr @@ -15,7 +15,7 @@ pkg_add tor obfs4proxy ### 2. Edit your Tor config file -Usually located at `/etc/tor/torrc`, add the following lines: +Usually located at `/etc/tor/torrc`, and replace its content with: ``` RunAsDaemon 1

1 0

[community/staging] Import EFF - Tor legal FAQ 2014 document from old website
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 7156ae788916a23f32189a2c8a2a6ac630f7a87f Author: gus <gus(a)torproject.org> Date: Thu Aug 8 11:26:20 2019 -0400 Import EFF - Tor legal FAQ 2014 document from old website --- .../eff-tor-legal-faq/contents.lr | 103 +++++++++++++++++++++ 1 file changed, 103 insertions(+) diff --git a/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr b/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr new file mode 100644 index 0000000..ddf4a40 --- /dev/null +++ b/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr @@ -0,0 +1,103 @@ +_model: page +--- +title: The Legal FAQ for Tor Relay Operators +--- +body: + +NOTE: This FAQ is for informational purposes only and does not constitute legal advice. Our aim is to provide a general description of the legal issues surrounding Tor in the United States. Different factual situations and different legal jurisdictions will result in different answers to a number of questions. Therefore, please do not act on this information alone; if you have any specific legal problems, issues, or questions, seek a complete review of your situation with a lawyer licensed to practice in your jurisdiction. + +Also, if you received this document from anywhere besides the EFF web site or https://community.torproject.org/relay/community/eff-tor-legal-faq, it may be out of date. Follow the link to get the latest version. + +Got a DMCA notice? Check out our [sample response letter](FIXME)! + +### General Information + +Has anyone ever been sued or prosecuted for running Tor? + +No, we aren't aware of anyone being sued or prosecuted in the United States just for running a Tor relay. Further, we believe that running a Tor relay including an exit relay that allows people to anonymously send and receive traffic - is legal under U.S. law. + +### Should I use Tor or encourage the use of Tor for illegal purposes? + +No. Tor has been developed to be a tool for free expression, privacy, and human rights. It is not a tool designed or intended to be used to break the law, either by Tor users or Tor relay operators. + + +### Can EFF promise that I won't get in trouble for running a Tor relay? + +No. All new technologies create legal uncertainties, and Tor is no exception. We cannot guarantee that you will never face any legal liability as a result of running a Tor relay. However, EFF believes so strongly that those running Tor relays shouldn't be liable for traffic that passes through the relay that we're running our own middle relay. + +### Will EFF represent me if I get in trouble for running a Tor relay? + +Maybe. While EFF cannot promise legal representation for all Tor relay operators, it will assist relay operators in assessing the situation and will try to locate qualified legal counsel when necessary. Inquiries to EFF for the purpose of securing legal representation or referrals should be directed to our intake coordinator by sending an email to info(a)eff.org . Such inquiries will be kept confidential subject to the limits of the attorney/client privilege. Note that although EFF cannot practice law outside of the United States, it will still try to assist non-U.S. relay operators in finding local representation. + +### Should I contact the Tor developers when I have legal questions about Tor or to inform them if I suspect Tor is being used for illegal purposes? + +No. Tor's developers are available to answer technical questions, but they are not lawyers and cannot give legal advice. Nor do they have any ability to prevent illegal activity that may occur through Tor relays. Furthermore, your communications with Tor's developers are not protected by any legal privilege, so law enforcement or civil litigants could subpoena and obtain any information you give to them. + +You can contact info(a)eff.org if you face a specific legal issue. We will try to assist you, but given EFF's small size, we cannot guarantee that we can help everyone. + +### Do Tor's core developers make any promises about the trustworthiness or reliability of Tor relays that are listed in their directory? + +No. Although the developers attempt to verify that Tor relays listed in the directory maintained by the core developers are stable and have adequate bandwidth, neither they nor EFF can guarantee the personal trustworthiness or reliability of the individuals who run those relays. Tor's core developers further reserve the right to refuse a Tor relay operator's request to be listed in their directory or to remove any relay from their directory for any reason. + +## Exit Relays + +Exit relays raise special concerns because the traffic that exits from them can be traced back to the relay's IP address. While we believe that running an exit relay is legal, it is statistically likely that an exit relay will at some point be used for illegal purposes, which may attract the attention of private litigants or law enforcement. An exit relay may forward traffic that is considered unlawful, and that traffic may be attributed to the operator of a relay. If you are not willing to deal with that risk, a bridge or middle relay may be a better fit for you. These relays do not directly forward traffic to the Internet and so can't be easily mistaken for the origin of allegedly unlawful content. + +The Tor Project's blog has some excellent [recommendations](https://blog.torproject.org/blog/tips-running-exit-node) for running an exit with as little risk as possible. We suggest that you review their advice before setting up an exit relay. + +### Should I run an exit relay from my home? + +No. If law enforcement becomes interested in traffic from your exit relay, it's possible that officers will seize your computer. For that reason, it's best not to run your exit relay in your home or using your home Internet connection. + +Instead, consider running your exit relay in a commercial facility that is supportive of Tor. Have a separate IP address for your exit relay, and don't route your own traffic through it. + +Of course, you should avoid keeping any sensitive or personal information on the computer hosting your exit relay, and you never should use that machine for any illegal purpose. + +### Should I tell my ISP that I'm running an exit relay? + +Yes. Make sure you have a Tor-friendly ISP that knows you're running an exit relay and supports you in that goal. This will help ensure that your Internet access isn't cut off due to abuse complaints. The Tor community maintains a list of ISPs that are particularly Tor-savvy, as well as ones that aren't. + +### Is it a good idea to let others know that I'm running an exit relay? + +Yes. Be as transparent as possible about the fact that you're running an exit relay. If your exit traffic draws the attention of the government or disgruntled private party, you want them to figure out quickly and easily that you are part of the Tor network and not responsible for the content. This could mean the difference between having your computer seized by law enforcement and being left alone. + +The Tor Project [suggests](https://blog.torproject.org/blog/tips-running-exit-node) the following ways to let others know that you're running an exit relay: + + * Set up a reverse DNS name for the IP address that makes clear that the computer is an exit relay. + * Set up a notice like [this](https://blog.torproject.org/blog/tips-running-exit-node) to explain that you're running an exit relay that's part of the Tor network. + * If possible, get an [ARIN](https://www.arin.net/) registration for your exit relay that displays contact information for you, not your ISP. This way, you'll receive any abuse complaints and can respond to them directly. Otherwise, try to ensure that your ISP forwards abuse complaints that it receives to you. + +### Should I snoop on the plaintext traffic that exits through my Tor relay? + +No. You may be technically capable of modifying the Tor source code or installing additional software to monitor or log plaintext that exits your relay. However, Tor relay operators in the United States can possibly create civil and even criminal liability for themselves under state or federal wiretap laws if they monitor, log, or disclose Tor users' communications, while non-U.S. operators may be subject to similar laws. Do not examine anyone's communications without first talking to a lawyer. + +### If I receive a subpoena or other information request from law enforcement or anyone else related to my Tor relay, what should I do? + +Educate them about Tor. In most instances, properly configured Tor relays will have no useful data for inquiring parties, and you should feel free to educate them on this point. To the extent you do maintain logs, however, you should not disclose them to any third party without first consulting a lawyer. In the United States, such a disclosure may violate the Electronic Communications Privacy Act, and relay operators outside of the United States may be subject to similar data protection laws. + +You may receive legal inquiries where you are prohibited by law from telling anyone about the request. We believe that, at least in the United States, such gag orders do not prevent you from talking to a lawyer, including calling a lawyer to find representation. Inquiries to EFF for the purpose of securing legal representation should be directed to our intake coordinator (info at eff.org) Such inquiries will be kept confidential subject to the limits of the attorney/client privilege. + +For more information about responding to abuse complaints and other inquiries, check out the [Tor Abuse FAQ](https://2019.www.torproject.org/docs/faq-abuse.html.en) and the collection of [abuse response templates](/tor-abuse-templates/) on the Tor Project's website. + +For information on what to do if law enforcement seeks access to your digital devices, check out EFF's [Know Your Rights](https://www.eff.org/wp/know-your-rights) guide. + +### My ISP, university, etc. just sent me a DMCA notice. What should I do? + +EFF has written a [short template](FIXME) to help you write a response to your ISP, university, etc., to let them know about the details of the Digital Millennium Copyright Act's safe harbor, and how Tor fits in. Note that template only refers to U.S. jurisdictions, and is intended only to address copyright complaints that are based on a relay of allegedly infringing material through the Tor node. + +If you like, you should consider submitting a copy of your notice to [Chilling Effects](https://www.chillingeffects.org/). This will help us recognize trends and issues that the lawyers might want to focus on. Chilling Effects encourages submissions from people outside the United States too. + +EFF believes that Tor relays should be protected from copyright liability for the acts of their users because a Tor relay operator can raise an immunity defense under the DMCA as well as defenses under copyright's secondary liability doctrines. However, no court has yet addressed these issues in the context of Tor itself. If you are uncomfortable with this uncertainty, you may consider using a reduced exit policy (such as the default policy suggested by the Tor Project) to try to minimize traffic types that are often targeted in copyright complaints. + +If you are a Tor relay operator willing to stand up and help set a clear legal precedent establishing that merely running a relay does not create copyright liability for either operators or their bandwidth providers, EFF is interested in hearing from you. Read more [here](https://lists.torproject.org/pipermail/tor-talk/2005-October/016301.h… about being EFF's test case. + +--- +html: two-columns-page.html +--- +key: 7 +--- +section: Community and legal resources +--- +section_id: community-resources +--- +subtitle: FAQ written by the Electronic Frontier Foundation (EFF). Last updated April 21, 2014.

1 0

[community/staging] Change FIXME links to Tor DMCA response template
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 67f5619768471acc515f6e6d95fa4a37c5ef2996 Author: gus <gus(a)torproject.org> Date: Thu Aug 8 12:01:40 2019 -0400 Change FIXME links to Tor DMCA response template --- .../eff-tor-legal-faq/contents.lr | 33 +++++++++++----------- 1 file changed, 16 insertions(+), 17 deletions(-) diff --git a/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr b/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr index ddf4a40..89adfff 100644 --- a/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr +++ b/content/relay-operations/community-resources/eff-tor-legal-faq/contents.lr @@ -6,38 +6,37 @@ body: NOTE: This FAQ is for informational purposes only and does not constitute legal advice. Our aim is to provide a general description of the legal issues surrounding Tor in the United States. Different factual situations and different legal jurisdictions will result in different answers to a number of questions. Therefore, please do not act on this information alone; if you have any specific legal problems, issues, or questions, seek a complete review of your situation with a lawyer licensed to practice in your jurisdiction. -Also, if you received this document from anywhere besides the EFF web site or https://community.torproject.org/relay/community/eff-tor-legal-faq, it may be out of date. Follow the link to get the latest version. +Also, if you received this document from anywhere besides the EFF web site or https://community.torproject.org/relay/community-resources/eff-tor-legal-faq, it may be out of date. Follow the link to get the latest version. -Got a DMCA notice? Check out our [sample response letter](FIXME)! +Got a DMCA notice? Check out our [sample response letter](/tor-dmca-response)! -### General Information +## General Information -Has anyone ever been sued or prosecuted for running Tor? +### Has anyone ever been sued or prosecuted for running Tor? -No, we aren't aware of anyone being sued or prosecuted in the United States just for running a Tor relay. Further, we believe that running a Tor relay including an exit relay that allows people to anonymously send and receive traffic - is legal under U.S. law. +**No**, we aren't aware of anyone being sued or prosecuted in the United States just for running a Tor relay. Further, we believe that running a Tor relay including an exit relay that allows people to anonymously send and receive traffic - is legal under U.S. law. ### Should I use Tor or encourage the use of Tor for illegal purposes? -No. Tor has been developed to be a tool for free expression, privacy, and human rights. It is not a tool designed or intended to be used to break the law, either by Tor users or Tor relay operators. - +**No**. Tor has been developed to be a tool for free expression, privacy, and human rights. It is not a tool designed or intended to be used to break the law, either by Tor users or Tor relay operators. ### Can EFF promise that I won't get in trouble for running a Tor relay? -No. All new technologies create legal uncertainties, and Tor is no exception. We cannot guarantee that you will never face any legal liability as a result of running a Tor relay. However, EFF believes so strongly that those running Tor relays shouldn't be liable for traffic that passes through the relay that we're running our own middle relay. +**No**. All new technologies create legal uncertainties, and Tor is no exception. We cannot guarantee that you will never face any legal liability as a result of running a Tor relay. However, EFF believes so strongly that those running Tor relays shouldn't be liable for traffic that passes through the relay that we're running our own middle relay. ### Will EFF represent me if I get in trouble for running a Tor relay? -Maybe. While EFF cannot promise legal representation for all Tor relay operators, it will assist relay operators in assessing the situation and will try to locate qualified legal counsel when necessary. Inquiries to EFF for the purpose of securing legal representation or referrals should be directed to our intake coordinator by sending an email to info(a)eff.org . Such inquiries will be kept confidential subject to the limits of the attorney/client privilege. Note that although EFF cannot practice law outside of the United States, it will still try to assist non-U.S. relay operators in finding local representation. +**Maybe**. While EFF cannot promise legal representation for all Tor relay operators, it will assist relay operators in assessing the situation and will try to locate qualified legal counsel when necessary. Inquiries to EFF for the purpose of securing legal representation or referrals should be directed to our intake coordinator by sending an email to info(a)eff.org . Such inquiries will be kept confidential subject to the limits of the attorney/client privilege. Note that although EFF cannot practice law outside of the United States, it will still try to assist non-U.S. relay operators in finding local representation. ### Should I contact the Tor developers when I have legal questions about Tor or to inform them if I suspect Tor is being used for illegal purposes? -No. Tor's developers are available to answer technical questions, but they are not lawyers and cannot give legal advice. Nor do they have any ability to prevent illegal activity that may occur through Tor relays. Furthermore, your communications with Tor's developers are not protected by any legal privilege, so law enforcement or civil litigants could subpoena and obtain any information you give to them. +**No**. Tor's developers are available to answer technical questions, but they are not lawyers and cannot give legal advice. Nor do they have any ability to prevent illegal activity that may occur through Tor relays. Furthermore, your communications with Tor's developers are not protected by any legal privilege, so law enforcement or civil litigants could subpoena and obtain any information you give to them. You can contact info(a)eff.org if you face a specific legal issue. We will try to assist you, but given EFF's small size, we cannot guarantee that we can help everyone. ### Do Tor's core developers make any promises about the trustworthiness or reliability of Tor relays that are listed in their directory? -No. Although the developers attempt to verify that Tor relays listed in the directory maintained by the core developers are stable and have adequate bandwidth, neither they nor EFF can guarantee the personal trustworthiness or reliability of the individuals who run those relays. Tor's core developers further reserve the right to refuse a Tor relay operator's request to be listed in their directory or to remove any relay from their directory for any reason. +**No**. Although the developers attempt to verify that Tor relays listed in the directory maintained by the core developers are stable and have adequate bandwidth, neither they nor EFF can guarantee the personal trustworthiness or reliability of the individuals who run those relays. Tor's core developers further reserve the right to refuse a Tor relay operator's request to be listed in their directory or to remove any relay from their directory for any reason. ## Exit Relays @@ -47,7 +46,7 @@ The Tor Project's blog has some excellent [recommendations](https://blog.torproj ### Should I run an exit relay from my home? -No. If law enforcement becomes interested in traffic from your exit relay, it's possible that officers will seize your computer. For that reason, it's best not to run your exit relay in your home or using your home Internet connection. +**No**. If law enforcement becomes interested in traffic from your exit relay, it's possible that officers will seize your computer. For that reason, it's best not to run your exit relay in your home or using your home Internet connection. Instead, consider running your exit relay in a commercial facility that is supportive of Tor. Have a separate IP address for your exit relay, and don't route your own traffic through it. @@ -55,11 +54,11 @@ Of course, you should avoid keeping any sensitive or personal information on the ### Should I tell my ISP that I'm running an exit relay? -Yes. Make sure you have a Tor-friendly ISP that knows you're running an exit relay and supports you in that goal. This will help ensure that your Internet access isn't cut off due to abuse complaints. The Tor community maintains a list of ISPs that are particularly Tor-savvy, as well as ones that aren't. +**Yes**. Make sure you have a Tor-friendly ISP that knows you're running an exit relay and supports you in that goal. This will help ensure that your Internet access isn't cut off due to abuse complaints. The Tor community maintains a list of ISPs that are particularly Tor-savvy, as well as ones that aren't. ### Is it a good idea to let others know that I'm running an exit relay? -Yes. Be as transparent as possible about the fact that you're running an exit relay. If your exit traffic draws the attention of the government or disgruntled private party, you want them to figure out quickly and easily that you are part of the Tor network and not responsible for the content. This could mean the difference between having your computer seized by law enforcement and being left alone. +**Yes**. Be as transparent as possible about the fact that you're running an exit relay. If your exit traffic draws the attention of the government or disgruntled private party, you want them to figure out quickly and easily that you are part of the Tor network and not responsible for the content. This could mean the difference between having your computer seized by law enforcement and being left alone. The Tor Project [suggests](https://blog.torproject.org/blog/tips-running-exit-node) the following ways to let others know that you're running an exit relay: @@ -69,11 +68,11 @@ The Tor Project [suggests](https://blog.torproject.org/blog/tips-running-exit-no ### Should I snoop on the plaintext traffic that exits through my Tor relay? -No. You may be technically capable of modifying the Tor source code or installing additional software to monitor or log plaintext that exits your relay. However, Tor relay operators in the United States can possibly create civil and even criminal liability for themselves under state or federal wiretap laws if they monitor, log, or disclose Tor users' communications, while non-U.S. operators may be subject to similar laws. Do not examine anyone's communications without first talking to a lawyer. +**No**. You may be technically capable of modifying the Tor source code or installing additional software to monitor or log plaintext that exits your relay. However, Tor relay operators in the United States can possibly create civil and even criminal liability for themselves under state or federal wiretap laws if they monitor, log, or disclose Tor users' communications, while non-U.S. operators may be subject to similar laws. Do not examine anyone's communications without first talking to a lawyer. ### If I receive a subpoena or other information request from law enforcement or anyone else related to my Tor relay, what should I do? -Educate them about Tor. In most instances, properly configured Tor relays will have no useful data for inquiring parties, and you should feel free to educate them on this point. To the extent you do maintain logs, however, you should not disclose them to any third party without first consulting a lawyer. In the United States, such a disclosure may violate the Electronic Communications Privacy Act, and relay operators outside of the United States may be subject to similar data protection laws. +**Educate them about Tor**. In most instances, properly configured Tor relays will have no useful data for inquiring parties, and you should feel free to educate them on this point. To the extent you do maintain logs, however, you should not disclose them to any third party without first consulting a lawyer. In the United States, such a disclosure may violate the Electronic Communications Privacy Act, and relay operators outside of the United States may be subject to similar data protection laws. You may receive legal inquiries where you are prohibited by law from telling anyone about the request. We believe that, at least in the United States, such gag orders do not prevent you from talking to a lawyer, including calling a lawyer to find representation. Inquiries to EFF for the purpose of securing legal representation should be directed to our intake coordinator (info at eff.org) Such inquiries will be kept confidential subject to the limits of the attorney/client privilege. @@ -83,7 +82,7 @@ For information on what to do if law enforcement seeks access to your digital de ### My ISP, university, etc. just sent me a DMCA notice. What should I do? -EFF has written a [short template](FIXME) to help you write a response to your ISP, university, etc., to let them know about the details of the Digital Millennium Copyright Act's safe harbor, and how Tor fits in. Note that template only refers to U.S. jurisdictions, and is intended only to address copyright complaints that are based on a relay of allegedly infringing material through the Tor node. +EFF has written a [short template](tor-dmca-response) to help you write a response to your ISP, university, etc., to let them know about the details of the Digital Millennium Copyright Act's safe harbor, and how Tor fits in. Note that template only refers to U.S. jurisdictions, and is intended only to address copyright complaints that are based on a relay of allegedly infringing material through the Tor node. If you like, you should consider submitting a copy of your notice to [Chilling Effects](https://www.chillingeffects.org/). This will help us recognize trends and issues that the lawyers might want to focus on. Chilling Effects encourages submissions from people outside the United States too.

1 0

[community/staging] without this escaping, the build breaks
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit bacc42dd625a27196cd49b4f7db6b699d2e27632 Author: emma peel <emma.peel(a)riseup.net> Date: Thu Aug 8 23:15:17 2019 +0200 without this escaping, the build breaks --- .../relay-operations/technical-setup/bridge/docker/contents.lr | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index b68770c..9ff4a6e 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -18,10 +18,10 @@ Now, it's time to run the container. You have two options: 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" \ + 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 ```

1 0

[community/staging] Replace EFF Tor legal FAQ old url to child page
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit f8f8336af2a73335ea7181da9c555ea0f36455cb Author: gus <gus(a)torproject.org> Date: Thu Aug 8 12:57:41 2019 -0400 Replace EFF Tor legal FAQ old url to child page --- content/relay-operations/community-resources/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/community-resources/contents.lr b/content/relay-operations/community-resources/contents.lr index eb905fc..809ab89 100644 --- a/content/relay-operations/community-resources/contents.lr +++ b/content/relay-operations/community-resources/contents.lr @@ -20,7 +20,7 @@ Exit relay operators should understand the potential risks associated with runni # Legal resources -The [EFF Tor Legal FAQ](https://www.torproject.org/eff/tor-legal-faq.html.en) answers many common questions about relay operation and the law. We also like [Noisebridge's wiki](https://www.noisebridge.net/wiki/Noisebridge_Tor/FBI) for additional legal resources. In general it's a good idea to consult with a lawyer before deciding to operate an exit relay, especially if you live in a place where exit relay operators have been harassed, or if you're the only exit relay operator in your region. Get in touch with your local digital rights organization to see if they have recommendations about legal assistance, and if you're not sure what organizations are working in your region, [write to EFF](https://www.eff.org/about/contact) and see if they can help connect you. +The [EFF Tor Legal FAQ](eff-tor-legal-faq) answers many common questions about relay operation and the law. We also like [Noisebridge's wiki](https://www.noisebridge.net/wiki/Noisebridge_Tor/FBI) for additional legal resources. In general it's a good idea to consult with a lawyer before deciding to operate an exit relay, especially if you live in a place where exit relay operators have been harassed, or if you're the only exit relay operator in your region. Get in touch with your local digital rights organization to see if they have recommendations about legal assistance, and if you're not sure what organizations are working in your region, [write to EFF](https://www.eff.org/about/contact) and see if they can help connect you. Also see the [Tor Exit Guidelines](tor-exit-guidelines).

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits March 2021