tor-commits March 2021

tor-commits@lists.torproject.org

17 participants
2169 discussions

[community/staging] Add instructions for Caddy 2
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 2810a3c8724c9df184c3826bd7c33f4779237cf1 Author: Amin Shah Gilani <amin(a)gilani.me> Date: Tue Jul 14 05:58:10 2020 +0500 Add instructions for Caddy 2 --- .../advanced/onion-location/contents.lr | 30 ++++++++++++++++++++++ 1 file changed, 30 insertions(+) diff --git a/content/onion-services/advanced/onion-location/contents.lr b/content/onion-services/advanced/onion-location/contents.lr index efd5e0c..b1e1dcf 100644 --- a/content/onion-services/advanced/onion-location/contents.lr +++ b/content/onion-services/advanced/onion-location/contents.lr @@ -184,6 +184,36 @@ To test if the Onion-Location is working, fetch the web site HTTP headers, for e Look for `onion-location` entry and the onion service address. Or, open the web site in Tor Browser and a purple pill will appear in the address bar. +### Caddy + +Caddy features [automatic HTTPS](https://caddyserver.com/docs/automatic-https) +by default, so it provisions your TLS certificate and takes care of +HTTP-to-HTTPS redirection for you. If you're using Caddy 2, to include an +Onion-Location header, add the following declaration in your Caddyfile: + +``` +header Onion-Location http://<your-onion-address>.onion{path} +``` + +If you're running a static site and have the onion address in a `$TOR_HOSTNAME` +environment variable, your Caddyfile will look like this: + +``` +your-website.tld + +header Onion-Location http://{$TOR_HOSTNAME}{path} +root * /var/www +file_server +``` + +**Testing it out:** Test it out with: + +``` +curl -I https://your-website.tld +``` + +and look for the `onion-location` line. + ### Using an HTML `<meta>` attribute The identical behaviour of Onion-Location includes the option of defining it as a HTML `<meta>` http-equiv attribute.

1 0

[community/staging] Update pluggable transport link
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit d3713f649c4e1dc18ef1fad2e43e2519b283b120 Author: Nicolei Ocana <nicoleiocana(a)gmail.com> Date: Sun Jun 7 20:57:29 2020 +0000 Update pluggable transport link --- content/relay-operations/types-of-relays/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/types-of-relays/contents.lr b/content/relay-operations/types-of-relays/contents.lr index c4ca5e8..dccab39 100644 --- a/content/relay-operations/types-of-relays/contents.lr +++ b/content/relay-operations/types-of-relays/contents.lr @@ -60,7 +60,7 @@ Tor bridges are nodes in the network that are not listed in the public Tor direc Bridges are useful for Tor users under oppressive regimes or for people who want an extra layer of security because they're worried somebody will recognize that they are contacting a public Tor relay IP address. Several countries, including China and Iran, have found ways to detect and block connections to Tor bridges. -[Pluggable transports](https://2019.www.torproject.org/docs/pluggable-transports.html.…, a special kind of bridge, address this by adding an additional layer of obfuscation. +[Pluggable transports](https://tb-manual.torproject.org/circumvention/), a special kind of bridge, address this by adding an additional layer of obfuscation. Bridges are relatively easy, low-risk and low bandwidth Tor nodes to operate, but they have a big impact on users. A bridge isn't likely to receive any abuse complaints, and since bridges are not listed in the public consensus, they are unlikely to be blocked by popular services.

1 0

[community/staging] Merge branch 'pluggable-transport-link'
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 6ce05bb16cd965757dd8704370264cf71c0282f4 Merge: 45ac51b d3713f6 Author: gus <gus(a)torproject.org> Date: Mon Jun 8 23:24:40 2020 -0400 Merge branch 'pluggable-transport-link' content/relay-operations/types-of-relays/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

1 0

[community/staging] Update link and add note at top
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit ec8fbbacaac5aa9151e812aa2b2ca9f5e4fa58bc Author: Nicolei Ocana <nicoleiocana(a)gmail.com> Date: Thu Jul 2 19:41:08 2020 +0000 Update link and add note at top --- content/relay-operations/technical-setup/bridge/windows/contents.lr | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/windows/contents.lr b/content/relay-operations/technical-setup/bridge/windows/contents.lr index 6f1e088..8de2601 100644 --- a/content/relay-operations/technical-setup/bridge/windows/contents.lr +++ b/content/relay-operations/technical-setup/bridge/windows/contents.lr @@ -10,13 +10,15 @@ key: 10 --- body: +**Note: You should only run a Windows bridge if you can run it 24/7. If the operator is unable to guarantee that, a [Snowflake](https://snowflake.torproject.org/) is a better way to contribute resources.** + ### 1. Download the Windows Expert Bundle and the Tor Browser -* [Windows Expert Bundle](https://www.torproject.org/dist/torbrowser/9.0.10/tor-win32-0.4.2.7…. Unzip the contents on the desktop. +* [Windows Expert Bundle](https://www.torproject.org/download/tor/). Unzip the contents on the desktop. * [Tor Browser](https://www.torproject.org/download/#windows). Run the `.exe` and install with default settings. -**Note: You will need to show hidden items and file name extensions. In your Explorer window, in the top-left, click on the View tab. In the Show/hide section furthest to the right, check the checkbox for Hidden items; check the checkbox for File name extensions.** +You will need to show hidden items and file name extensions. In your Explorer window, in the top-left, click on the View tab. In the Show/hide section furthest to the right, check the checkbox for Hidden items; check the checkbox for File name extensions. ### 2. Build files and relocate

1 0

[community/staging] Adding missing link
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit ef7406711e5cac796fbfef193d79b012da15ea2b Author: Enjeck Cleopatra <32180937+PROTechThor(a)users.noreply.github.com> Date: Thu Dec 12 15:00:03 2019 +0100 Adding missing link --- content/onion-services/setup/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/onion-services/setup/contents.lr b/content/onion-services/setup/contents.lr index a33df07..23c5f42 100644 --- a/content/onion-services/setup/contents.lr +++ b/content/onion-services/setup/contents.lr @@ -61,7 +61,7 @@ Now save your `torrc` and restart Tor. If Tor starts up again, great. Otherwise, something is wrong. First look at your logfiles for hints. It will print some warnings or error messages. That should give you an idea what went wrong. -Typically there are typos in the torrc or wrong directory permissions (See the logging FAQ [FIXME add link] entry if you don't know how to enable or find your log file.) +Typically there are typos in the torrc or wrong directory permissions (See the [logging FAQ](www.torproject.org/docs/faq#Logs) entry if you don't know how to enable or find your log file.) When Tor starts, it will automatically create the `HiddenServiceDir` that you specified (if necessary). Make sure this is the case.

1 0

[community/staging] Update h6 header to include portal and section
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 3b7add0533da45fd2e2bd1ac3c1068b5b2274daa Author: Antonela <hola(a)antonela.me> Date: Thu Dec 5 09:15:00 2019 -0300 Update h6 header to include portal and section Fix https://dip.torproject.org/torproject/web/community/issues/38 --- templates/hero.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/hero.html b/templates/hero.html index 3a8f7c0..f02d70c 100644 --- a/templates/hero.html +++ b/templates/hero.html @@ -2,7 +2,7 @@ <div class="row"> <div class="col-12 content-center"> <div class="row"> - <h6 class="mx-auto text-white pt-3">{% block section %}{{ this.section }}{% endblock %}</h6> + <h6 class="mx-auto text-white pt-3">{{ _(Community) }}</h6> </div> <div class="row"> <h2 class="mx-auto display-3 text-white">{% block title %}{{ this.title }}{% endblock %}</h2>

1 0

[community/staging] Update contents.lr
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 83f54c919485f1700000f6b11c892d2e544982d4 Author: Enjeck Cleopatra <32180937+PROTechThor(a)users.noreply.github.com> Date: Thu Dec 12 15:03:03 2019 +0100 Update contents.lr --- content/onion-services/setup/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/onion-services/setup/contents.lr b/content/onion-services/setup/contents.lr index 7114fd8..a8aefdc 100644 --- a/content/onion-services/setup/contents.lr +++ b/content/onion-services/setup/contents.lr @@ -61,7 +61,7 @@ Now save your `torrc` and restart Tor. If Tor starts up again, great. Otherwise, something is wrong. First look at your logfiles for hints. It will print some warnings or error messages. That should give you an idea what went wrong. -Typically there are typos in the torrc or wrong directory permissions (See the [logging FAQ](www.torproject.org/docs/faq#Logs) entry if you don't know how to enable or find your log file.) +Typically, there are typos in the torrc or wrong directory permissions (See the [logging FAQ](www.torproject.org/docs/faq#Logs) entry if you don't know how to enable or find your log file.) When Tor starts, it will automatically create the `HiddenServiceDir` that you specified (if necessary). Make sure this is the case.

1 0

[community/staging] Merge branch 'master' into PROTechThor-log-faq-link
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit ef20e52d1f3600e6ab76681ef3fc21965333ea45 Merge: ef74067 3b7add0 Author: Enjeck Cleopatra <32180937+PROTechThor(a)users.noreply.github.com> Date: Thu Dec 12 15:02:27 2019 +0100 Merge branch 'master' into PROTechThor-log-faq-link assets/static/images/home/png/block-trackers.png | Bin 0 -> 18192 bytes .../static/images/home/png/block-trackers(a)2x.png | Bin 0 -> 42047 bytes .../static/images/home/png/block-trackers(a)3x.png | Bin 0 -> 66496 bytes assets/static/images/home/png/browse-freely.png | Bin 0 -> 27282 bytes assets/static/images/home/png/browse-freely(a)2x.png | Bin 0 -> 62800 bytes assets/static/images/home/png/browse-freely(a)3x.png | Bin 0 -> 99137 bytes assets/static/images/home/png/encryption.png | Bin 0 -> 19727 bytes assets/static/images/home/png/encryption(a)2x.png | Bin 0 -> 44050 bytes assets/static/images/home/png/encryption(a)3x.png | Bin 0 -> 70895 bytes assets/static/images/home/png/fingerprinting.png | Bin 0 -> 28619 bytes .../static/images/home/png/fingerprinting(a)2x.png | Bin 0 -> 64240 bytes .../static/images/home/png/fingerprinting(a)3x.png | Bin 0 -> 100068 bytes assets/static/images/home/png/surveillance.png | Bin 0 -> 18021 bytes assets/static/images/home/png/surveillance(a)2x.png | Bin 0 -> 40297 bytes assets/static/images/home/png/surveillance(a)3x.png | Bin 0 -> 63810 bytes assets/static/images/home/png/take-back(a)3x.png | Bin 0 -> 124543 bytes assets/static/images/home/svg/block-trackers.svg | 1 + assets/static/images/home/svg/browse-freely.svg | 1 + assets/static/images/home/svg/encryption.svg | 1 + assets/static/images/home/svg/fingerprinting.svg | 1 + assets/static/images/home/svg/surveillance.svg | 1 + assets/static/images/home/svg/take-back.svg | 7902 ++++++++++++++++++++ .../becoming-tor-translator/contents.lr | 18 +- content/localization/contents.lr | 4 +- .../localization/translation-problem/contents.lr | 2 +- content/onion-services/contents.lr | 2 +- content/onion-services/overview/contents.lr | 33 +- content/onion-services/setup/contents.lr | 12 +- content/onion-services/ssl-tls/contents.lr | 21 - .../community-resources/bad-relays/contents.lr | 26 +- .../eff-tor-legal-faq/contents.lr | 4 +- .../tor-dmca-response/contents.lr | 2 + .../community-resources/good-bad-isps/contents.lr | 2 + .../community-resources/swag/contents.lr | 6 +- .../tor-abuse-templates/contents.lr | 2 + .../tor-exit-guidelines/contents.lr | 4 +- .../tor-relay-universities/contents.lr | 4 +- content/relay-operations/contents.lr | 2 +- .../bridge/debian-ubuntu/contents.lr | 15 +- .../technical-setup/bridge/docker/contents.lr | 95 +- .../bridge/dragonflybsd/contents.lr | 145 + .../technical-setup/bridge/netbsd/contents.lr | 100 + .../relay-operations/technical-setup/contents.lr | 2 +- .../technical-setup/exit/contents.lr | 36 +- content/training/checklist/contents.lr | 20 +- content/training/faq/contents.lr | 16 +- content/training/risks/contents.lr | 28 +- content/user-research/become-tester/contents.lr | 13 + content/user-research/contents.lr | 17 +- content/user-research/current/contents.lr | 19 - content/user-research/guidelines/contents.lr | 76 + content/user-research/open/contents.lr | 47 + content/user-research/persona/contents.lr | 27 + content/user-research/signup/contents.lr | 19 - content/user-testing/current/contents.lr | 19 - content/user-testing/signup/contents.lr | 19 - databags/menu+bn-BD.ini | 1 - databags/menu+de.ini | 1 - databags/menu+en.ini | 1 - databags/menu+es.ini | 1 - databags/menu+fr.ini | 1 - databags/menu+id.ini | 1 - databags/menu+is.ini | 1 - databags/menu+it.ini | 1 - databags/menu+ka.ini | 1 - databags/menu+ko.ini | 1 - databags/menu+pt-BR.ini | 1 - databags/menu+ru.ini | 1 - databags/menu+tr.ini | 1 - databags/menu+zh-CN.ini | 1 - databags/menu.ini | 1 + databags/menu_footer+bn-BD.ini | 1 - databags/menu_footer+de.ini | 1 - databags/menu_footer+en.ini | 1 - databags/menu_footer+es.ini | 1 - databags/menu_footer+fr.ini | 1 - databags/menu_footer+id.ini | 1 - databags/menu_footer+is.ini | 1 - databags/menu_footer+it.ini | 1 - databags/menu_footer+ka.ini | 1 - databags/menu_footer+ko.ini | 1 - databags/menu_footer+pt-BR.ini | 1 - databags/menu_footer+ru.ini | 1 - databags/menu_footer+tr.ini | 1 - databags/menu_footer+zh-CN.ini | 1 - databags/menu_footer.ini | 1 + databags/pagenav+de.ini | 1 - databags/pagenav+es.ini | 1 - databags/pagenav+fr.ini | 1 - databags/pagenav+it.ini | 1 - databags/pagenav+pt-BR.ini | 1 - databags/pagenav+ru.ini | 1 - databags/{pagenav+en.ini => pagenav.ini} | 4 + databags/training-resources.json | 11 + lego | 2 +- templates/banner.html | 1 + templates/hero.html | 2 +- templates/onion-services.html | 49 +- templates/pagenav.html | 4 +- templates/resources.html | 21 +- templates/user-research.html | 34 +- 101 files changed, 8616 insertions(+), 312 deletions(-)

1 0

[community/staging] one sentence per line, needed for localization
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 07fae35ad17d630b3e0e035fbc2aeacac9e00c0e Author: emma peel <emma.peel(a)riseup.net> Date: Wed Dec 11 10:52:54 2019 +0100 one sentence per line, needed for localization --- .../eff-tor-legal-faq/contents.lr | 62 ++++++++++++++++------ .../relays-requirements/contents.lr | 2 +- content/training/best-practices/contents.lr | 3 +- 3 files changed, 49 insertions(+), 18 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 acc857c..385a255 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,7 +6,10 @@ 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. +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-resources/eff-tor-legal-faq, it may be out of date. Follow the link to get the latest version. @@ -24,25 +27,36 @@ Got a DMCA notice? Check out our [sample response letter](/relay/community-resou ### 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 at 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 -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. +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. @@ -56,27 +70,38 @@ 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: * 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. + * 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. +**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. +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. @@ -84,13 +109,18 @@ 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](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. +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. +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. +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. +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 diff --git a/content/relay-operations/relays-requirements/contents.lr b/content/relay-operations/relays-requirements/contents.lr index 0c1808e..5ad16cc 100644 --- a/content/relay-operations/relays-requirements/contents.lr +++ b/content/relay-operations/relays-requirements/contents.lr @@ -8,7 +8,7 @@ _template: layout.html --- title: Relay requirements --- -subtitle: Requirements for Tor relays depend on the type of relay and the bandwidth they provide. Learn more about specific relay requirements. +subtitle: Requirements for Tor relays depend on the type of relay and the bandwidth they provide. Learn more about specific relay requirements. --- key: 2 --- diff --git a/content/training/best-practices/contents.lr b/content/training/best-practices/contents.lr index 19c7946..91bb2dd 100644 --- a/content/training/best-practices/contents.lr +++ b/content/training/best-practices/contents.lr @@ -48,7 +48,8 @@ Once you've answered those questions, you're ready to plan your training! This includes downloads and PDFs of handouts. You'll share this link list on a whiteboard or project it at the training. 6. Determine how you'll do hands-on assistance at your training. - Will you be able to handle this alone? Or will you require partners? If you need more help, make sure the partners you're bringing in are aware of the safety needs of the community, and communicate with your contacts in the community to make sure they're okay with you bringing in additional trainers. + Will you be able to handle this alone? Or will you require partners? + If you need more help, make sure the partners you're bringing in are aware of the safety needs of the community, and communicate with your contacts in the community to make sure they're okay with you bringing in additional trainers. 7. Make sure your presentation is up-to-date (both information and screenshots) and save your presentation in two file formats -- for example, odp and pdf -- and on at least one additional device -- for example, on your computer and on a USB stick. 8. Decide how you will facilitate a safer space. We recommend using the [Tor Code of Conduct](/training/code-of-conduct/).

1 0

[community/staging] add redirects for languages still not published.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit f1d585122351616a09acddc86d37d6a35d3328d0 Author: emma peel <emma.peel(a)riseup.net> Date: Mon Dec 16 11:22:31 2019 +0100 add redirects for languages still not published. will-fix: https://trac.torproject.org/projects/tor/ticket/32760 --- .htaccess | 18 ++++++++++++++++++ 1 file changed, 18 insertions(+) diff --git a/.htaccess b/.htaccess index 6e2c53a..ba7c37a 100644 --- a/.htaccess +++ b/.htaccess @@ -1,4 +1,22 @@ +RewriteEngine On + # forward requests in /en to the root folder RewriteRule ^(en-US|en)$ / [R=302,L] RewriteRule ^(en-US|en)/(.*) /$2 [R=302,L] +# forward requests in /en and /en-US to the root folder +RewriteRule ^(en|en-US)$ / [R=302,L] +RewriteRule ^(en|en-US)/(.*) /$2 [R=302,L] + +# Rewrites for languages that have a different mapping in the page than in TBB +RewriteRule ^(es-ES|es-MX|es-CO|es-AR)(.*) /es$2 [R=302,L] + +# we have only one translation for this locales +RewriteRule ^(bn-BD|bn-IN)(.*) /bn$2 [R=302,L] +RewriteRule ^ga-IE/(.*) /ga$1 [R=302,L] + +# Rewrites for languages that have a Tor Browser release +# but don't have a community page +# You can see them at https://dist.torproject.org/torbrowser/, pick the last alpha for the most languages +# this languages are the translation priority for the community portal! +RewriteRule ^(ar|ca|cs|da|de|el|es|fa|fr|ga|he|hu|id|is|ja|ka|ko|lt|mk|ms|nb-NO|nl|pl|pt-BR|pt-PT|ro|ru|sv-SE|th|tr|vi|zh-CN|zh-TW)/(.*) /$2 [R=302,L]

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

tor-commits March 2021