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

[community/slideshow] Add windows instructions: snowflake option, final notes, and fix styling.
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit adb3c39d17ddfdb3d675451600d0f5435fd34400 Author: gus <gus(a)torproject.org> Date: Fri Apr 9 11:54:59 2021 -0300 Add windows instructions: snowflake option, final notes, and fix styling. --- .../technical-setup/guard/windows/contents.lr | 34 ++++++++++++---------- 1 file changed, 19 insertions(+), 15 deletions(-) diff --git a/content/relay-operations/technical-setup/guard/windows/contents.lr b/content/relay-operations/technical-setup/guard/windows/contents.lr index 8733b55..2dcd62d 100644 --- a/content/relay-operations/technical-setup/guard/windows/contents.lr +++ b/content/relay-operations/technical-setup/guard/windows/contents.lr @@ -2,13 +2,24 @@ _model: page --- color: primary --- -title: Windows +title: Windows 10 +--- +html: two-columns-page.html +--- +key: 8 +--- +section: Middle/Guard relay +--- +section_id: relay-operations +--- +subtitle: How to deploy a middle/Guard relay on Windows --- body: -# Relay setup guide for Windows 10 -Setting up a Windows system as a relay requires performing a few simple steps to set up a user account, download the expert bundle, implement a torrc configuration file and start up Tor from the command line. Below are detailed instructions on how to perform these steps - please ensure you follow them very carefully, and make any of the necessary modifications outlined along the way. +**Note: You should only run a Windows relay 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.** +Setting up a Windows system as a relay requires performing a few simple steps to set up a user account, download the expert bundle, implement a torrc configuration file and start up Tor from the command line. +Below are detailed instructions on how to perform these steps - please ensure you follow them very carefully, and make any of the necessary modifications outlined along the way. # 1. Creating a user account for Tor First you will need to create a new account to allow Tor to run isolated from your personal configuration as well as have manageable system permissions. @@ -41,7 +52,6 @@ The next step is to download and install Windows Expert bundle as well as set up ``` #Change the nickname "myNiceRelay" to a name that you like Nickname myNiceRelay - ORPort 9001 ExitRelay 0 SocksPort 0 @@ -76,14 +86,8 @@ There are two methods for starting up your relay for the first time depending on 3. You should now see Tor starting up in your terminal. Wait until its finished bootstrapping. 4. After a short period it should publish its OrPort, and you will be successfully relaying traffic for the Tor Network. * **Notice:** Depending on your systems settings, Tor may fail to start and produce an error indicating it is unable to create files. If this occurs, simply open the Windows Defender Security Center and select "App & browser control". Add the tor.exe file to the permissions list, then rerun `tor.exe` from the command line. Tor should now start up normally. ---- -html: two-columns-page.html ---- -key: 8 ---- -section: Middle/Guard relay ---- -section_id: relay-operations ---- -subtitle: How to deploy a middle/Guard relay on Windows ---- + +## 4. Final notes + +If you are having trouble setting up your relay, have a look at our [help section](/relay/getting-help/). +If your relay is now running, check out the [post-install](/relay/setup/post-install/) notes.

1 0

[community/slideshow] Update links to gitlab.tpo
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit a852d296bf7b73ab6b908cb59ad32808d9f3ea54 Author: gus <gus(a)torproject.org> Date: Mon Apr 12 16:11:07 2021 -0300 Update links to gitlab.tpo --- content/relay-operations/technical-setup/bridge/docker/contents.lr | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index 6448ba3..85ffb24 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -9,7 +9,7 @@ body: ### 1. Deploy a container We provide a docker-compose file that helps you deploy the container. -First, [download docker-compose.yml](https://dip.torproject.org/torproject/anti-censorship/d…, and then write your bridge configuration to a new file, `.env`, which is in the same directory as `docker-compose.yml`. Here's a template: +First, [download docker-compose.yml](https://gitlab.torproject.org/torproject/anti-censorshi…, and then write your bridge configuration to a new file, `.env`, which is in the same directory as `docker-compose.yml`. Here's a template: ``` # Your bridge's Tor port. @@ -82,8 +82,7 @@ OBFS4_ENABLE_ADDITIONAL_VARIABLES=1 OBFS4V_AddressDisableIPv6=1 ``` -You may [download our template .env](https://dip.torproject.org/torproject/anti-censorship/docker-obfs4-bridge/raw/master/.env) to get started. - +You may [download our template .env](https://gitlab.torproject.org/torproject/anti-censorship/docker-obfs4-bridge/raw/master/.env) to get started. --- html: two-columns-page.html ---

1 0

[community/slideshow] added space
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit 26e6f93a3cc7c9e50a20a39f3724b34b4f179f19 Author: Anushka Jain <anushkajain2902(a)gmail.com> Date: Tue Apr 13 01:34:49 2021 +0530 added space --- templates/relay-operations.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/templates/relay-operations.html b/templates/relay-operations.html index 7690b3b..1109d78 100644 --- a/templates/relay-operations.html +++ b/templates/relay-operations.html @@ -21,7 +21,7 @@ </div> <div class="row py-5 text-center mx-auto"> <h2 class="display-4 text-primary text-center mx-auto my-3">{{ _('Connect with other Relay Operators') }}</h2> - <p class="text-center">{{ _('The best resource of all is the active community of relay operators on tor-relays mailing list and on IRC #tor-relays in irc.oftc.net. ') }}</p> + <p class="text-center">{{ _('The best resource of all is the active community of relay operators on tor-relays mailing list and on IRC') }} <a href="https://webchat.oftc.net/?channels=tor-relays" target="_blank">{{_('#tor-relays') }}</a> {{ _('in irc.oftc.net.') }}</p> <a class="btn btn-lg btn-outline-primary mx-auto my-3" href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays"> {{ _('Relay Operators mailing list') }}<i class="ml-3 pt-2 fas fa-arrow-right"></i> </a>

1 0

[community/slideshow] Remove extra spaces
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit b5e1acb0de6d2be6a1c850ba5c014726db701949 Author: gus <gus(a)torproject.org> Date: Wed Apr 14 08:56:19 2021 -0300 Remove extra spaces --- content/user-research/how-to-volunteer/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/user-research/how-to-volunteer/contents.lr b/content/user-research/how-to-volunteer/contents.lr index b3a5c81..754db35 100644 --- a/content/user-research/how-to-volunteer/contents.lr +++ b/content/user-research/how-to-volunteer/contents.lr @@ -8,8 +8,8 @@ body: If this is your first time running a User Research session for the Tor Project, we recommend starting with one of these studies. Both can be conducted on a rolling basis and ran remotely. -- [Usability Testing Tor Browser Desktop](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/script… -- [Discovery Bridges](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/script… +- [Usability Testing Tor Browser Desktop](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/script… +- [Discovery Bridges](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/script… After choosing which study to run, open an issue in our [GitLab page](https://gitlab.torproject.org/tpo/ux/research). Add the title of your research, then select the Usability Testing template option and fill it in.

1 0

[community/slideshow] grammar and style
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit 621714934e620bd88dd48c9faf15ca5fb3c1aa97 Author: emma peel <emma.peel(a)riseup.net> Date: Fri Apr 16 15:17:32 2021 +0200 grammar and style --- .../training/resources/tor-training/contents.lr | 39 ++++++++++------------ 1 file changed, 17 insertions(+), 22 deletions(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index 29222d6..0c6b74c 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -44,14 +44,14 @@ description: #### slide #### -title: Why run a Tor relay? +title: Why running a Tor relay? ---- description: By running a Tor relay, you can help make the Tor network: - faster (and therefore more usable) - more robust against attacks - more stable in case of outages -- safer for its users (spying on more relays is harder than on a few) +- safer for users (spying on more relays is harder than on a few) #### slide #### @@ -71,7 +71,7 @@ title: Guard/middle (aka non-exit) relay ---- description: - A guard is the first relay in the chain of 3 relays building a Tor circuit. -- A middle relay is neither a guard nor an exit but acts as the second hop between them. +- A middle relay is neither a guard nor an exit, but acts as the second hop between them. - To become a guard, a middle relay has to be stable and fast (at least 2MByte/s); otherwise, it will remain a middle relay. @@ -91,7 +91,7 @@ title: Bridge description: - A bridge is a node in the network that is not listed in the public Tor directory, making it harder for ISPs and governments to block it. - Bridges are relatively easy, low-risk, and low bandwidth Tor relays to operate. -- And there's another special kind of bridge: Pluggable transports. It hides your Tor traffic by adding a layer of obfuscation. +- And there's another special kind of bridge: Pluggable transport. Hides your Tor traffic by adding a layer of obfuscation. #### slide #### @@ -127,8 +127,9 @@ description: title: Before we start ---- description: -- Never run a relay without the consent of the network administrator or machine owner. Read the Terms of Service (ToS) first, so you don’t risk losing money. -- Choose which type of relay you will host. Non-exit relay is a easy way to start helping the network. +- Never run a relay without the consent of the network administrator or machine owner. + Read the Terms of Service (ToS) first, so you don’t risk losing money. +- Choose which type of relay you will host. A non-exit relay is an easy way to start helping the network. - Read the documentation: [https://community.torproject.org/relay](https://community.torproject.org/re… @@ -146,7 +147,7 @@ title: Monthly outbound traffic ---- description: - It is required to use a minimum of 100 GByte of outbound/incoming traffic per month. -- If you have a metered plan, you might want to configure Tor only to use a given amount of bandwidth or monthly traffic. +- If you have a metered plan, you might want to configure Tor to use only a given amount of bandwidth or monthly traffic. - More (>2 TB/month) is better and recommended. @@ -180,15 +181,9 @@ description: title: Choosing your relay hosting ---- description: -- Tor community maintain the list GoodBadISPs, about the experience of running relays: https://community.torproject.org/relay/community-resources/good-bad-isps/ -- Some providers only allow non-exit relays, so before buying a service, check the GoodBadISPs. - - -#### slide #### -title: Choosing your relay hosting ----- -description: -- Runnin a relay can cost anywhere between a few bucks and hundreds per month. +- The Tor community team maintains the list GoodBadISPs, about the experience of running relays: <https://community.torproject.org/relay/community-resources/good-bad-isps/> +- Some providers only allow non-exit relays, so check the GoodBadISPs list before buying a service. +- Running a relay can cost anywhere between a few bucks to hundreds per month. #### slide #### @@ -218,7 +213,7 @@ description: title: Non-exit relay - Debian/Ubuntu ---- description: -- Put the configuration file `/etc/tor/torrc` in place: +- Add relay configuration to the `/etc/tor/torrc` file: ``` Nickname myNiceRelay ExitRelay 0 @@ -256,7 +251,7 @@ description: title: Non-exit relay - FreeBSD ---- description: - - Edit the configuration `file/usr/local/etc/tor/torrc` + - Edit the configuration file `/usr/local/etc/tor/torrc` ``` Nickname myNiceRelay @@ -335,7 +330,7 @@ description: - Enable automatic software updates. - Backup your Tor Identity Keys. - It's possible to limit bandwidth usage (and traffic). Check the parameters, for example, AccountingMax, AccountingRule, AccountingStart. -- If run more than one Tor relay, you need to set the MyFamily parameter. +- If you run more than one Tor relay, you need to set the MyFamily parameter. #### slide #### @@ -354,7 +349,7 @@ description: - Metrics portal - [https://metrics.torproject.org](https://metrics.torproject.org) - Is possible to search: how many relays are in the network, how many are exits, etc. - In 2021 there are ~6,600 public relays and ~1,500 bridges. -- Check: how many relays are in your country? Who runs these relays? How diverse is it? +- Check: how many relays are in your country? Who runs these relays? How diverse are they? #### slide #### @@ -372,7 +367,7 @@ description: title: Monoculture ---- description: -- A single kernel vulnerability in GNU/Linux impacting Tor relays could be devastating. +- A single kernel vulnerability in GNU/Linux impacting all Tor relays could be devastating. - Diversity of Operating System (OS): ~90% of relays are Linux. @@ -380,7 +375,7 @@ description: title: Monoculture ---- description: -- Diversity of Autonomous System (AS). +- Diversity of Autonomous Systems (AS). - Try to avoid the following hosters: OVH SAS (AS16276), Online S.a.s. (AS12876), Hetzner Online GmbH (AS24940), DigitalOcean, LLC (AS14061).

1 0

[community/slideshow] remove phrase to edit, as document will not be editable
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit aa12aae299b8552ce37f967a3001f5925e61e084 Author: emma peel <emma.peel(a)riseup.net> Date: Fri Apr 16 15:21:17 2021 +0200 remove phrase to edit, as document will not be editable --- content/training/resources/tor-training/contents.lr | 10 ++-------- 1 file changed, 2 insertions(+), 8 deletions(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index a04a824..22179c1 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -533,20 +533,14 @@ title: Getting help ---- description: - Read the Tor Relay documentation: -- [https://community.torproject.org/relay](https://community.torproject.org/re… -- Subscribe to tor-relays mailing list: [https://lists.torproject.org](https://lists.torproject.org) + <https://community.torproject.org/relay> +- Subscribe to tor-relays mailing list: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays> - Join our IRC channel: #tor-relays in irc.oftc.net #### slide #### title: Thank you! ---- -author: -name - email(a)example.com ----- -subtitle: -PGP FINGERPRINT ----- slide_layout: title-slide ---- background_image: /static/images/onion-white.png

1 0

[community/slideshow] change order because it made more sense for me
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit e91175cbd7c405f6a0842c08675d247549e5389f Author: emma peel <emma.peel(a)riseup.net> Date: Fri Apr 16 15:12:33 2021 +0200 change order because it made more sense for me --- content/training/resources/tor-training/contents.lr | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index 07a1fde..29222d6 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -37,9 +37,10 @@ description: title: The Tor network ---- description: -- An open network, everyone can be part of it. Your server will relay the Tor traffic to another server on the Internet. +- An open network, everyone can be part of it. - The network is composed of different types of servers run by volunteers around the world. -- Before ingressing the network, the server will pass automatically to the relay lifecycle. +- Your server will relay the Tor traffic to another server on the Internet. +- Before entering the network, your server will automatically go through the relay lifecycle. #### slide ####

1 0

[community/slideshow] Better strings for localization
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit 174e6c0ebdce0972b92ea4dbe62680498130b5ec Author: gus <gus(a)torproject.org> Date: Tue Apr 13 15:36:50 2021 -0300 Better strings for localization --- content/user-research/guidelines/contents.lr | 21 +++++++++---- content/user-research/how-to-volunteer/contents.lr | 34 ++++++++++++++++------ 2 files changed, 40 insertions(+), 15 deletions(-) diff --git a/content/user-research/guidelines/contents.lr b/content/user-research/guidelines/contents.lr index ff0586b..c78ca5e 100644 --- a/content/user-research/guidelines/contents.lr +++ b/content/user-research/guidelines/contents.lr @@ -35,18 +35,21 @@ You'd love to read about your experiences during the training, product testing, * Scenario: describe the process of the test you ran. * Demographics: While we are not interested in specific characteristics of our audience, or binary attributes, we must know the total reach of your Tor training. You should take [this material]() with you on the day of your research, distribute it among participants, and answer their questions about how to fill it in if they have any. -* Interview Process: Thank the participant for their willingness to participate in this process and explain that we are testing the product, not them. The interview should not last longer than 20 minutes, you can record if you wish, but you can also take notes on the printed material you will carry with you (or on your computer). Thank the participant again and end the interview. +* Interview Process: Thank the participant for their willingness to participate in this process and explain that we are testing the product, not them. +The interview should not last longer than 20 minutes, you can record if you wish, but you can also take notes on the printed material you will carry with you (or on your computer). +Thank the participant again and end the interview. Send us the result - you don't have to write a report, we can do this data analysis with the material you collected. - ## Coordinate with the trainer and the Tor UX team You're not doing all this work alone - we will support you with meetings, guides, and mentorship if you want. You can join us at any time on our IRC channel #tor-ux and our [mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/ux). -You must be aligned about the agenda and time to run interviews (if that is the case) during the end of the training. **We strongly recommend that you go through the program of the exercise with the trainer**. Also, we want you two to coordinate feedback together — both for you and for your audience. +You must be aligned about the agenda and time to run interviews (if that is the case) during the end of the training. **We strongly recommend that you go through the program of the exercise with the trainer**. +Also, we want you two to coordinate feedback together - both for you and for your audience. At the beginning of the training, be sure to let everyone know what is your role there and why you're taking notes on the practice. ## Get prepared! + Print and bring with you the material that you will need to run the research - that will probably be something like: * Demographics @@ -58,12 +61,18 @@ It is easier to have this material printed and in hand, but if you prefer, you c Keep in mind that you might not have Internet access at the venue, so if you're going to install a Tor feature with someone during the interview, you may need to have it downloaded before the training. ## Report to Tor UX team -Before ending the training, coordinate the feedback with the trainer. The two of you should work together to hand out post-its for the audience, you can give each participant post-it of a different color per question and ask them to fill it with what they think about: 1. the service they just learned; 2. Tor project; and 3. Tor in general. It can also be questions - keep in mind that any feedback is a good feedback. -It is very important for us to hear back from you. We want to know how the training and the research was for you, how we can improve our support and also, if you want to keep running Tor User Research. We will ask you to fill a form at the end of the research, so we can get your address to send to you a researcher kit (t-shirt and stickers). +Before ending the training, coordinate the feedback with the trainer. +The two of you should work together to hand out post-its for the audience, you can give each participant post-it of a different color per question and ask them to fill it with what they think about: 1. the service they just learned; 2. Tor project; and 3. Tor in general. +It can also be questions - keep in mind that any feedback is a good feedback. + +It is very important for us to hear back from you. +We want to know how the training and the research was for you, how we can improve our support and also, if you want to keep running Tor User Research. +We will ask you to fill a form at the end of the research, so we can get your address to send to you a researcher kit (t-shirt and stickers). We hope to hear back from you very soon! -Before your session, read and print this material on [User Research Reporting](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/comm…. If you don't think you'll have time to report in this format, we will happily accept your findings another way – for example, you can take pictures or send your 'raw' notes to us. +Before your session, read and print this material on [User Research Reporting](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/comm…. +If you don't think you'll have time to report in this format, we will happily accept your findings another way - for example, you can take pictures or send your 'raw' notes to us. ### How to submit your findings diff --git a/content/user-research/how-to-volunteer/contents.lr b/content/user-research/how-to-volunteer/contents.lr index a3f3f3f..b3a5c81 100644 --- a/content/user-research/how-to-volunteer/contents.lr +++ b/content/user-research/how-to-volunteer/contents.lr @@ -8,27 +8,43 @@ body: If this is your first time running a User Research session for the Tor Project, we recommend starting with one of these studies. Both can be conducted on a rolling basis and ran remotely. - - [Usability Testing Tor Browser Desktop](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/script… - [Discovery Bridges](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/script… -After choosing which study to run, open an issue in our [GitLab page](https://gitlab.torproject.org/tpo/ux/research). Add the title of your research, then select the Usability Testing template option and fill it in. Please remember to update the issue as your research evolves. +After choosing which study to run, open an issue in our [GitLab page](https://gitlab.torproject.org/tpo/ux/research). +Add the title of your research, then select the Usability Testing template option and fill it in. +Please remember to update the issue as your research evolves. -Not all of the data collected in our research is disclosed to the public, but our general findings are. To protect our participants' privacy we take care to anonymize their responses and avoid recording our sessions. +Not all of the data collected in our research is disclosed to the public, but our general findings are. +To protect our participants' privacy we take care to anonymize their responses and avoid recording our sessions. -If you're already familiar with the Tor Project and user testing, have a look at our [current needs for user research](https://community.torproject.org/user-research/open/) and see which study better suits you. Remember to drop us an email telling us about your plans so we can follow and support your research. +If you're already familiar with the Tor Project and user testing, have a look at our [current needs for user research](https://community.torproject.org/user-research/open/) and see which study better suits you. +Remember to drop us an email telling us about your plans so we can follow and support your research. As a volunteer we also ask that you read and follow our [Code of Conduct](https://gitweb.torproject.org/community/policies.git/tree/code_of_…, as well our [Guidelines for Research](https://community.torproject.org/user-research/guidelines/). -**Why do we run Demographics?** We don't collect personal data in our [Demographics](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/s…, and all questions are optional. We believe it's important to collect basic demographics to help us understand if we are meeting our mission regarding diversity and inclusion. In addition, collecting these demographics is required for specific studies to support human rights. +**Why do we run Demographics?** +We don't collect personal data in our [Demographics](https://gitlab.torproject.org/tpo/ux/research/-/blob/master/s…, and all questions are optional. +We believe it's important to collect basic demographics to help us understand if we are meeting our mission regarding diversity and inclusion. +In addition, collecting these demographics is required for specific studies to support human rights. -**We don't trick participants.** We don't use trick questions in our research. We expect participants to be honest with us, and we must be honest about our questions in return. As a transparent research space our surveys, studies, and reports are all public, and participants are free to view past studies prior to taking part – however they are not advised to do so. +**We don't trick participants.** We don't use trick questions in our research. +We expect participants to be honest with us, and we must be honest about our questions in return. +As a transparent research space our surveys, studies, and reports are all public, and participants are free to view past studies prior to taking part - however they are not advised to do so. -**We don't track participants.** We care about your privacy and security. If we invite you to participate in a study, we won't track you and any recordings will be erased after the report is complete. We advise volunteers not to record their sessions at all. +**We don't track participants.** We care about your privacy and security. +If we invite you to participate in a study, we won't track you and any recordings will be erased after the report is complete. +We advise volunteers not to record their sessions at all. -**Open source for privacy.** We use free and open source software to analyze our data, and we recommend our volunteers do the same. We also ask anyone running research not use software hosted by third parties like cloud providers. +**Open source for privacy.** +We use free and open source software to analyze our data, and we recommend our volunteers do the same. +We also ask anyone running research not use software hosted by third parties like cloud providers. -**Decision-making process.** We don't have a single model for decision making. After conducting your research, it's normal to be excited to see your feedback implemented as soon as possible. However all feedback must be discussed internally across the different teams at the Tor Project first. This means that it's often necessary to run the same research more than once to validate your findings, and meet the expectations of the engineers, developers, designers, researchers and others at Tor. Please read our [Guidelines](https://community.torproject.org/user-research/guidelines/) to get to know this process more. +**Decision-making process.** We don't have a single model for decision making. +After conducting your research, it's normal to be excited to see your feedback implemented as soon as possible. +However all feedback must be discussed internally across the different teams at the Tor Project first. +This means that it's often necessary to run the same research more than once to validate your findings, and meet the expectations of the engineers, developers, designers, researchers and others at Tor. +Please read our [Guidelines](https://community.torproject.org/user-research/guidelines/) to get to know this process more. ## Checklist

1 0

[community/slideshow] Update the training material, removed broken links, added community.tpo reference, grammar review
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit 98e2be57319ebe33cd9e8c47adf73c0424424e7d Author: gus <gus(a)torproject.org> Date: Wed Apr 14 11:42:54 2021 -0300 Update the training material, removed broken links, added community.tpo reference, grammar review --- .../training/resources/tor-training/contents.lr | 151 +++++++++++---------- 1 file changed, 83 insertions(+), 68 deletions(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index 8292dd2..08dacbd 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -15,7 +15,7 @@ title: Topics ---- description: -- What' s Tor? +- What's Tor? - Types of relays - Technical setup - More about relays @@ -28,10 +28,10 @@ description: title: What's Tor? ---- description: -- Tor is a free software and an open network -- Mitigates against tracking, surveillance and censorship -- Run by a US non-profit and volunteers from all over the world -- It' s Tor, not TOR +- Tor is a free software and an open network. +- Mitigates against tracking, surveillance and censorship. +- Run by a US non-profit and volunteers from all over the world. +- It's Tor, not TOR. @@ -39,17 +39,17 @@ description: title: The Tor network ---- description: -- An open network, everyone can be part of it. Basically, your server will relay the tor traffic to another server in the Internet. -- The network is composed by different types of servers run by volunteers around the world. -- To ingress in the network, the new server will pass automatically to a new relay lifecycle. +- An open network, everyone can be part of it. Your server will relay the Tor traffic to another server on the Internet. +- The network is composed of different types of servers run by volunteers around the world. +- Before ingressing the network, the server will pass automatically to the relay lifecycle. #### slide #### title: Why run a Tor relay? ---- description: -By running a Tor relay you can help make the Tor network: -- faster (and therefore more usable +By running a Tor relay, you can help make the Tor network: +- faster (and therefore more usable) - more robust against attacks - more stable in case of outages - safer for its users (spying on more relays is harder than on a few) @@ -72,27 +72,27 @@ title: Guard/middle (aka non-exit) relay ---- description: - A guard is the first relay in the chain of 3 relays building a Tor circuit. -- A middle relay is neither a guard nor an exit, but acts as the second hop between the two. -- To become a guard, a relay has to be stable and fast (at least 2MByte/s) otherwise it will remain a middle relay. +- A middle relay is neither a guard nor an exit but acts as the second hop between them. +- To become a guard, a middle relay has to be stable and fast (at least 2MByte/s); otherwise, it will remain a middle relay. #### slide #### title: Exit relay ---- description: -- The exit relay is the final relay in a Tor circuit, the one that sends traffic out its destination. -- That's why exit relays have the greatest legal exposure and liability of all the relays. -- Before running an exit relay, check it with your local digital rights organization. -- **You should not run a Tor exit relay from your home** +- The exit relay is the final relay in a Tor circuit that sends traffic out its destination. +- That's why exit relays have the most significant legal exposure and liability of all the relays. +- Before running an exit relay, talk with your local digital rights organization. +- **You should not run a Tor exit relay from your home.** #### slide #### title: Bridge ---- description: -- A bridge is a node in the network that isn't listed in the public Tor directory, which make it harder for ISPs and governments to block it. -- Bridges are relatively easy, low-risk and low bandwidth Tor nodes to operate. -- And there's another special kind of bridge: Pluggable transports. It hides your tor traffic by adding an additional layer of obfuscation. +- A bridge is a node in the network that isn't listed in the public Tor directory, making it harder for ISPs and governments to block it. +- Bridges are relatively easy, low-risk, and low bandwidth Tor relays to operate. +- And there's another special kind of bridge: Pluggable transports. It hides your Tor traffic by adding a layer of obfuscation. #### slide #### @@ -100,9 +100,9 @@ title: The lifecycle of a new relay ---- description: Non-exit relays pass by a lifecycle of four phases (defined by days): -- Days 0-3: the unmeasured phase -- Days 3-8: network authorities start the remote measurement phase (the ramp-up guard phase) -- Days 8-68: guard phase (where load counter intuitively drops and then rises higher) +- Days 0-3: the unmeasured phase. +- Days 3-8: network authorities start the remote measurement phase (the ramp-up guard phase). +- Days 8-68: guard phase (where load counter intuitively drops and then rises higher). #### slide #### @@ -110,7 +110,6 @@ title: The lifecycle of a new relay ---- description: - And after 68 days, if the relay is stable and fast enough, it receives a Guard flag (steady-state guard phase). -- Exit relays also have a lifecycle more or less similar. - Read about all the phases in: [https://blog.torproject.org/lifecycle-new-relay](https://blog.torproject.or… @@ -129,18 +128,18 @@ description: title: Before we start ---- description: -- Never run a relay without the consent of network administrator or machine owner. Read the Terms of Service (ToS) first, so you don’t lose money. +- Never run a relay without the consent of the network administrator or machine owner. Read the Terms of Service (ToS) first, so you don’t risk losing money. - Choose which type of relay you will host. Non-exit relay is a easy way to start helping the network. -- Read the documentation: [https://torproject.org/tor-relays](https://torproject.org/tor-relays) +- Read the documentation: [https://community.torproject.org/relay](https://community.torproject.org/re… #### slide #### title: Bandwidth requirements ---- description: -- At least 16 Mbit/s (Mbps) upload and download bandwidth available for Tor. More is better. +- It’s recommended at least 16 Mbit/s (Mbps) upload and 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. +- If you have less than 10 Mbit/s but at least 1 Mbit/s, we recommend running a bridge with obfs4 support. #### slide #### @@ -148,8 +147,8 @@ title: Monthly outbound traffic ---- description: - It is required to use a minimum of 100 GByte of outbound/incoming traffic per month. -- If you have a metered plan you might want to configure tor to only use a given amount of bandwidth or monthly traffic. -- More (>2 TB/month) is better and recommended +- If you have a metered plan, you might want to configure Tor only to use a given amount of bandwidth or monthly traffic. +- More (>2 TB/month) is better and recommended. #### slide #### @@ -157,7 +156,7 @@ title: Public IPv4 address ---- description: - Every relay needs a public IPv4 address - either directly on the host (preferred) or via NAT and port forwarding. -- The IPv4 address is not required to be static but static IP addresses are preferred. +- The IPv4 address is not required to be static, but static IP addresses are preferred. - Your IPv4 address should remain unchanged for at least 3 hours (network consensus). - You can only run two Tor relays per public IPv4. @@ -175,14 +174,14 @@ title: Other requirements ---- description: - Any modern CPU should be fine. -- Uptime: Ideally the relay runs on a server which runs 24/7. +- Uptime: Ideally, the relay runs on a server which runs 24/7. #### slide #### title: Choosing your relay hosting ---- description: -- Tor community maintain the list GoodBadISPs, about the experience of running relays: https://trac.torproject.org/projects/tor/wiki/doc/GoodBadISPs +- Tor community maintain the list GoodBadISPs, about the experience of running relays: https://community.torproject.org/relay/community-resources/good-bad-isps/ - Some providers only allow non-exit relays, so before buying a service, check the GoodBadISPs. @@ -190,7 +189,7 @@ description: title: Choosing your relay hosting ---- description: -- This can cost anywhere between $3.00/mo and thousands per month. +- Runnin a relay can cost anywhere between a few bucks and hundreds per month. #### slide #### @@ -208,7 +207,7 @@ description: title: Non-exit relay - Debian/Ubuntu ---- description: -- Enable the Torproject package repository +- Enable the Tor Project package repository - Install the tor package ``` @@ -299,8 +298,8 @@ description: title: Non-exit relay - FreeBSD ---- description: -Optional, but recommended to get package updates faster: -[https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/FreeBSD](https://trac.torproject.org/projects/tor/wiki/TorRelayGuide/FreeBSD) + +- Optional, but recommended to get package updates faster: [https://community.torproject.org/relay/setup/guard/freebsd/](https://commun… #### slide #### @@ -316,7 +315,7 @@ After restarting the service, verify in the log file if it contains the followin Publishing server descriptor. ``` -About 3 hours after you started your relay it should appear on Metrics portal in Relay Search. +About 3 hours after you started your relay, it should appear on Metrics portal in Relay Search. #### slide #### @@ -336,8 +335,8 @@ title: Technical tips description: - Enable automatic software updates. - Backup your Tor Identity Keys. -- It’s possible to limit bandwidth usage (and traffic). Check the parameters, for example: AccountingMax, AccountingRule, AccountingStart. -- If run more than one Tor relay, you need to set MyFamily parameter. +- It's possible to limit bandwidth usage (and traffic). Check the parameters, for example, AccountingMax, AccountingRule, AccountingStart. +- If run more than one Tor relay, you need to set the MyFamily parameter. #### slide #### @@ -347,7 +346,6 @@ description: - Running multiple relays by hand can be challenging. - Configuration management tools can make the relay operator life easier: - Ansible-relayor: [http://github.com/nusenu/ansible-relayor](http://github.com/nusenu/ansible-… -- Bash script: [https://github.com/coldhakca/tor-relay-bootstrap](https://github.com/coldha… #### slide #### @@ -355,9 +353,9 @@ title: Metrics ---- description: - Metrics portal - [https://metrics.torproject.org](https://metrics.torproject.org) -- It’s possible to search: how many relays are in the network, how many are exit, etc -- In 2019 there are ~6,600 relays and ~1,500 bridges. -- Check: how many relays are in your country? Who run these relays? How diverse it is? +- It's possible to search: how many relays are in the network, how many are exits, etc. +- In 2021 there are ~6,600 public relays and ~1,500 bridges. +- Check: how many relays are in your country? Who runs these relays? How diverse is it? #### slide #### @@ -383,7 +381,16 @@ description: title: Monoculture ---- description: -- Diversity of Autonomous System (AS). Try to avoid the following hosters: OVH SAS (AS16276), Online S.a.s. (AS12876), Hetzner Online GmbH (AS24940), DigitalOcean, LLC (AS14061). +- Diversity of Autonomous System (AS). +- Try to avoid the following hosters: OVH SAS (AS16276), Online S.a.s. (AS12876), Hetzner Online GmbH (AS24940), DigitalOcean, LLC (AS14061). + + +#### slide #### +title: The TorBSD Diversity Project +---- +description: +- The Tor BSD Diversity Project (TDP) is an initiative seeking the BSD Unix operating systems’ use in the network. +- Goals: increase the number of Tor relays running BSDs; Engage the BSD community about Tor anonymity; Port Tor related programs to BSD operating systems. #### slide #### @@ -401,9 +408,9 @@ description: title: Legal information ---- description: -- In many countries there are regulations that exclude communication service providers from liability. +- In many countries, some regulations exclude internet service providers from liability. - It's a good idea to consult with a lawyer or your local digital rights organization. -- Under most circumstances you will be able to handle legal matters by having an abuse response letter. +- Under most circumstances, you will be able to handle legal matters by having an abuse response letter. #### slide #### @@ -412,11 +419,21 @@ title: Legal resources description: - The EFF Tor Legal FAQ: [https://community.torproject.org/relay/community-resources/eff-tor-legal-fa… -- It’s important to respond to abuse complaints in a timely manner (usually within 24 hours). +- It's important to respond to abuse complaints in a timely manner (usually within 24 hours). - Abuse templates letters: [https://community.torproject.org/relay/community-resources/tor-abuse-templa… +#### slide #### +title: Tips for running an exit relay +---- +description: +- Get a separate IP for the relay, and don’t use it for other services. +- Set up a Tor Exit Notice, so if someone checks your exit IP, they will quickly know that it’s a Tor Exit. +- If you receive excessive complaints, consider running a Reduced Exit Policy. +- For more tips: [https://blog.torproject.org/tips-running-exit-node](https://blog.torproject… + + #### slide #### title: Running relays with others ---- @@ -432,18 +449,16 @@ description: title: Running a relay with others ---- description: -- You can work with your university department, employer or institution, or an organization like [Torservers.org](Torservers.org) -- [Torservers.org](Torservers.org) is an independent, global network of organizations that helps the Tor network by running high bandwidth Tor relays. -- In many countries operating as a corporation instead of as an individual can also get you certain legal protections. +- You can work with your university department, employer or institution, or an organization like Torservers.org, Nos oignons, etc. +- Some organizations are dedicated to this purpose only, and they are called Relay Associations: [https://community.torproject.org/relay/community-resources/relay-associatio… #### slide #### title: Relays associations ---- description: -- It’s often advised to create some type of non-profit corporation. This is useful for having a bank account and shared ownership. -- To start a relay association, the most important thing is to have a group of people (3-5 suggested to start) interested in helping. -- For example: Torservers.org, Cold Hak, enn.lu, nos-oignons. +- It's often advised to create some type of non-profit corporation. This is useful for having a bank account and shared ownership. +- The most important thing is to have a group of people (3-5 suggested to start) interested in helping. #### slide #### @@ -451,14 +466,14 @@ title: Running a relay with universities ---- description: - Universities are typically home to a reliable, robust, and well-equipped network. -- Many computer science departments and university libraries run relays, i.e., Massachussetts Institute of Technology (MIT CSAIL), Universitaet Stuttgart, the University of Waterloo. - +- Many computer science departments and university libraries run relays: Massachusetts Institute of Technology, Universität Stuttgart, the University of Waterloo. #### slide #### title: Running a relay with universities ---- description: -- Start running a relay campaign in your university: [https://www.eff.org/torchallenge/tor-on-campus.html](https://www.eff.org/to… +- Read more: [https://community.torproject.org/relay/community-resources/tor-relay-univer… + #### slide #### @@ -466,8 +481,8 @@ title: At your company or organization ---- description: - If you work at a Tor-friendly company or organization, that's another ideal place to run a relay. -- Companies like Brass Horn Communications, Quintex Alliance Consulting, and OmuraVPN -- And organizations like Digital Courage, Access Now, Derechos Digitales, and Lebanon Libraries in New Hampshire. +- Companies like Brass Horn Communications, Quintex Alliance Consulting, and many others. +- And organizations like Digital Courage, Access Now, Derechos Digitales, Calyx Institute, and Lebanon Libraries in New Hampshire. #### slide #### @@ -485,7 +500,7 @@ description: title: What is a bad relay? ---- description: -- A bad relay is one that either doesn't work properly or tampers with our users' connections. This can be either through maliciousness or misconfiguration. +- A bad relay is one that either doesn't work properly or tampers with our users' connections. That can be either through maliciousness or misconfiguration. #### slide #### @@ -499,17 +514,17 @@ description: title: Reporting a bad relay ---- description: -- Bad relays is also a private working group in Tor Project to detect misconfigured, malicious, or suspicious relay. -- Users can report bad relays sending an email to bad-relays(a)lists.torproject.org with the relay's IP address or fingerprint, what kind of behavior did you see, and any additional information it’s needed to reproduce the issue. +- Bad relays is also a private working group in the Tor Project to detect misconfigured, malicious, or suspicious relay. +- Users can report bad relays by sending an email to bad-relays(a)lists.torproject.org with the relay’s IP address or fingerprint, what kind of behavior you see, and any additional information’s needed to reproduce the issue. #### slide #### title: What happens to bad relays? ---- description: -- After a relay is reported and we've verified the behavior we'll attempt to contact the relay operator. -- We'll flag it to prevent it from continuing to be used (BadExit, Invalid, Reject). -- The working group actively look for bad relays using open source tools like: exitmap, sysbilhunter. +- After a relay is reported and verified the behavior, the Tor Project will attempt to contact the relay operator. +- The relay will be flagged to prevent it from being used (BadExit, Invalid, Reject). +- The working group actively looks for bad relays using open source tools like exitmap, sysbilhunter. #### slide #### @@ -527,10 +542,10 @@ description: title: Getting help ---- description: -- Read the Tor Relay Guide documentation before: -- [https://torproject.org/relay-guide](https://torproject.org/relay-guide) -- Search the mailing list archive: tor-relays in [https://lists.torproject.org](https://lists.torproject.org) -- Join the IRC channel: #tor-relays in irc.oftc.net +- Read the Tor Relay documentation: +- [https://community.torproject.org/relay](https://community.torproject.org/re… +- Subscribe to tor-relays mailing list: [https://lists.torproject.org](https://lists.torproject.org) +- Join our IRC channel: #tor-relays in irc.oftc.net #### slide ####

1 0

[community/slideshow] use less contractions
by emmapeel＠torproject.org 16 Apr '21

16 Apr '21

commit 3185d669e5b10625b35974caad45a116bee940da Author: emma peel <emma.peel(a)riseup.net> Date: Fri Apr 16 15:07:44 2021 +0200 use less contractions --- content/training/resources/tor-training/contents.lr | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/content/training/resources/tor-training/contents.lr b/content/training/resources/tor-training/contents.lr index 08dacbd..07a1fde 100644 --- a/content/training/resources/tor-training/contents.lr +++ b/content/training/resources/tor-training/contents.lr @@ -14,8 +14,7 @@ slides: title: Topics ---- description: - -- What's Tor? +- What is Tor? - Types of relays - Technical setup - More about relays @@ -23,9 +22,8 @@ description: - Getting help - #### slide #### -title: What's Tor? +title: What is Tor? ---- description: - Tor is a free software and an open network. @@ -80,8 +78,8 @@ description: title: Exit relay ---- description: -- The exit relay is the final relay in a Tor circuit that sends traffic out its destination. -- That's why exit relays have the most significant legal exposure and liability of all the relays. +- The exit relay is the final relay in a Tor circuit, sends the traffic to its destination. +- That is why exit relays have the most significant legal exposure and liability of all the relays. - Before running an exit relay, talk with your local digital rights organization. - **You should not run a Tor exit relay from your home.** @@ -90,7 +88,7 @@ description: title: Bridge ---- description: -- A bridge is a node in the network that isn't listed in the public Tor directory, making it harder for ISPs and governments to block it. +- A bridge is a node in the network that is not listed in the public Tor directory, making it harder for ISPs and governments to block it. - Bridges are relatively easy, low-risk, and low bandwidth Tor relays to operate. - And there's another special kind of bridge: Pluggable transports. It hides your Tor traffic by adding a layer of obfuscation. @@ -353,7 +351,7 @@ title: Metrics ---- description: - Metrics portal - [https://metrics.torproject.org](https://metrics.torproject.org) -- It's possible to search: how many relays are in the network, how many are exits, etc. +- Is possible to search: how many relays are in the network, how many are exits, etc. - In 2021 there are ~6,600 public relays and ~1,500 bridges. - Check: how many relays are in your country? Who runs these relays? How diverse is it? @@ -450,14 +448,14 @@ title: Running a relay with others ---- description: - You can work with your university department, employer or institution, or an organization like Torservers.org, Nos oignons, etc. -- Some organizations are dedicated to this purpose only, and they are called Relay Associations: [https://community.torproject.org/relay/community-resources/relay-associatio… +- Some organizations are dedicated to this purpose only, and they are called Relay Associations: <https://community.torproject.org/relay/community-resources/relay-associatio…>. #### slide #### title: Relays associations ---- description: -- It's often advised to create some type of non-profit corporation. This is useful for having a bank account and shared ownership. +- It's often advised to create some type of non-profit organization. This is useful for having a bank account and shared ownership. - The most important thing is to have a group of people (3-5 suggested to start) interested in helping.

1 0