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

[community/staging] change subtitle.lr
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit deae4c7da67672248af92028ac47aa93d1142d93 Author: Stephanie A. Whited <steph(a)torproject.org> Date: Fri Oct 4 20:42:35 2019 +0000 change subtitle.lr --- content/training/code-of-conduct/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/training/code-of-conduct/contents.lr b/content/training/code-of-conduct/contents.lr index 03dc97a..a0d2bba 100644 --- a/content/training/code-of-conduct/contents.lr +++ b/content/training/code-of-conduct/contents.lr @@ -10,7 +10,7 @@ _template: layout.html --- title: Code of Conduct for Trainers --- -subtitle: Don't be a jerk. Be awesome instead. +subtitle: Foster a safe, engaging environment. --- cta: Code of Conduct ---

1 0

[community/staging] as dfBSD was sad to be added alone, we brought NetBSD to the rescue;
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 8e1d02a7490dc482ddec1be353ac54b159c8ab5f Author: Vinicius Zavam <egypcio(a)googlemail.com> Date: Fri Oct 4 22:05:44 2019 +0000 as dfBSD was sad to be added alone, we brought NetBSD to the rescue; - of course it runs netbsd ]:-) --- .../technical-setup/bridge/netbsd/contents.lr | 96 ++++++++++++++++++++++ 1 file changed, 96 insertions(+) diff --git a/content/relay-operations/technical-setup/bridge/netbsd/contents.lr b/content/relay-operations/technical-setup/bridge/netbsd/contents.lr new file mode 100644 index 0000000..8262eda --- /dev/null +++ b/content/relay-operations/technical-setup/bridge/netbsd/contents.lr @@ -0,0 +1,96 @@ +_model: page +--- +color: primary +--- +title: NetBSD +--- +html: two-columns-page.html +--- +key: 3 +--- +body: + +### 1. Setup `pkg_add` + +``` +echo "PKG_PATH=http://cdn.netbsd.org/pub/pkgsrc/packages/NetBSD/$(uname -m)/$(uname -r)/All" > /etc/pkg_install.conf +``` + +2. Install `obfs4proxy` and `tor` NetBSD's package + +``` +pkg_add obfs4proxy tor +``` + +### 2. Configure `/usr/pkg/etc/tor/torrc` to run **Tor** as a Bridge + +``` +RunAsDaemon 1 +BridgeRelay 1 + +# Replace "TODO1" with a Tor port of your choice. This port must be externally +# reachable. Avoid port 9001 because it's commonly associated with Tor and +# censors may be scanning the Internet for this port. +ORPort TODO1 + +ServerTransportPlugin obfs4 exec /usr/pkg/bin/obfs4proxy + +# Replace "TODO2" with an obfs4 port of your choice. This port must be +# externally reachable and must be different from the one specified for ORPort. +# Avoid port 9001 because it's commonly associated with +# Tor and censors may be scanning the Internet for this port. +ServerTransportListenAddr obfs4 0.0.0.0:TODO2 + +# Local communication port between Tor and obfs4. Always set this to "auto". +# "Ext" means "extended", not "external". Don't try to set a specific port +# number, nor listen on 0.0.0.0. +ExtORPort auto + +# Replace "<address(a)email.com>" with your email address so we can contact you if +# there are problems with your bridge. This is optional but encouraged. +ContactInfo <address(a)email.com> + +# Pick a nickname that you like for your bridge. This is optional. +Nickname PickANickname + +Log notice syslog +``` + +Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, and `Nickname` options. + +* Please note that both `ORPort` and the port you used as `TODO2` (for obfs4) must be reachable. If your bridge is behind a firewall or NAT, make sure to open/forward both ports. You can use [our reachability test](https://bridges.torproject.org/scan/) to see if your obfs4 port is reachable from the Internet. + +* Are you firewalling your NetBSD? If so, make sure that `obfs4proxy` can talk to `tor` over the loopback interface - do not forget to whitelist the **ExtORPort**. + +### 3. Start `tor`: + +``` +ln -sf /usr/pkg/share/examples/rc.d/tor /etc/rc.d/tor +echo "tor=YES" >> /etc/rc.conf +/etc/rc.d/tor start +``` + +### 4. Monitor your logs + +To confirm your bridge is running with no issues, you should see something like this: + +``` +[notice] Your Tor server's identity key fingerprint is '<NICKNAME> <FINGERPRINT>' +[notice] Your Tor bridge's hashed identity key fingerprint is '<NICKNAME> <HASHED FINGERPRINT>' +[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>: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. +``` + +### 5. Final Notes + +If you are having troubles setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/). + +--- +subtitle: How to deploy an obfs4 bridge on NetBSD +--- +section: Bridge +--- +section_id: bridge

1 0

[community/staging] Updated contents, removed redundancies
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit ff4a1e64c5e221800825faba7639418997edc1bf Author: Stephanie A. Whited <steph(a)torproject.org> Date: Fri Oct 4 20:54:39 2019 +0000 Updated contents, removed redundancies --- .../localization/becoming-tor-translator/contents.lr | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/content/localization/becoming-tor-translator/contents.lr b/content/localization/becoming-tor-translator/contents.lr index f5986cc..229f70d 100644 --- a/content/localization/becoming-tor-translator/contents.lr +++ b/content/localization/becoming-tor-translator/contents.lr @@ -8,25 +8,24 @@ _template: layout.html --- title: Becoming a Tor translator --- -subtitle: Tor Project localization is hosted in the Localization Lab Hub on Transifex, a third-party translation platform. Read on for details on how to sign up and begin contributing. +subtitle: Our localization efforts happen in the Localization Lab Hub on Transifex, a third-party translation platform. Learn how to sign up and begin contributing. --- key: 1 --- html: two-columns-page.html --- body: +Thank you for your interest in helping us with translations. -If you are interested in helping out the project by translating the manual or the Tor Browser to your language, your help would be greatly appreciated! -Tor Project localization is hosted in the [Localization Lab Hub](https://www.localizationlab.org/) on Transifex, a third-party translation platform. +Our localization efforts are hosted in the [Localization Lab Hub](https://www.localizationlab.org/) on Transifex, a third-party translation platform. -Before translating, please read through the Tor Project page on the [Localization Lab Wiki](https://wiki.localizationlab.org/index.php/Tor). -There you will find translation guidelines and resources that will help you contribute to Tor translations, as well as translation priorities. +Before translating, please read through the Tor Project page on the [Localization Lab Wiki](https://wiki.localizationlab.org/index.php/Tor). The page includes guidelines, resources, and priorities that will help you make the most out of your contribution. ### Localization mailing list You are cordially invited to join the [Tor localization mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-l10n), to organize translations, participate in our decisions, report errors in source strings, etc. -In order to begin contributing you will have to sign up with Transifex. Below is an outline of how to sign up and begin. +In order to begin contributing you will have to sign up with Transifex. Here's an outline of what to expect during that process. # Signing Up On Transifex @@ -45,8 +44,4 @@ In order to begin contributing you will have to sign up with Transifex. Below is - A notification will now show up on the top of the page like so: ![Request Submitted](/static/images/localization/tr5.png) -After your membership is approved you can begin translating; there is a list of needed translations at [Tor Transifex page](https://www.transifex.com/otf/torproject/) when you are ready to begin. - -The [Localization Lab Wiki](https://wiki.localizationlab.org/index.php/Tor) also has information about the translations with bigger priority. - -Thanks for your interest in helping the project! +After your membership is approved, you're ready to begin. \ No newline at end of file

1 0

[community/staging] stephs review
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 711bd249561bdfddf76401fbff94726081399a75 Author: emma peel <emma.peel(a)riseup.net> Date: Sat Oct 5 08:46:39 2019 +0200 stephs review --- content/relay-operations/technical-setup/contents.lr | 18 ++++++++++-------- 1 file changed, 10 insertions(+), 8 deletions(-) diff --git a/content/relay-operations/technical-setup/contents.lr b/content/relay-operations/technical-setup/contents.lr index 71bd65a..6ce43c8 100644 --- a/content/relay-operations/technical-setup/contents.lr +++ b/content/relay-operations/technical-setup/contents.lr @@ -10,7 +10,7 @@ _template: layout.html --- title: Technical Setup --- -subtitle: Installing and configuring your Tor relay: Bridge, Guard / Middle node, Exit. +subtitle: How to install and configure each type of relay: bridge, guard, middle, and exit. --- html: two-columns-page.html --- @@ -20,19 +20,21 @@ This section covers the installation and configuration of the program required t These steps are intended for the latest stable version of the given OS, on Ubuntu for the latest LTS release. -Note: For some operating systems, there are alpha version packages available (tor versions with new features not deemed to be stable yet). - +Note: For some operating systems, there are alpha version packages available (Tor versions with new features not deemed to be stable yet). These are only recommended for people eager to test and report bugs in bleeding edge releases/features. -If you are looking to run a relay with minimal effort we recommend you stick to stable releases. +If you are looking to run a relay with minimal effort, we recommend you stick to stable releases. # Questions you should clarify before configuring Tor -* Do you want to run a Tor exit or non-exit (guard/middle) relay? -* If you want to run an exit relay: Which ports do you want to allow in your exit policy? (more ports usually means potentially more abuse complains) +* Do you want to run a Tor exit or non-exit (bridge/guard/middle) relay? +* If you want to run an exit relay: Which ports do you want to allow in your exit policy? + (More ports usually means potentially more abuse complaints.) * What external TCP port do you want to use for incoming Tor connections? - ("ORPort" configuration, we recommend port 443 if that is not used by another daemon on your server already. ORPort 443 is recommended because it is often one of the few open ports on public WIFI networks. Port 9001 is another commonly used ORPort.) + ("ORPort" configuration: We recommend port 443 if that is not used by another daemon on your server already. + ORPort 443 is recommended because it is often one of the few open ports on public WIFI networks. + Port 9001 is another commonly used ORPort.) * What email address will you use in the ContactInfo field of your relay(s)? - Note: This information will be made public. + This information will be made public. * How much bandwidth/monthly traffic do you want to allow for Tor traffic? * Does the server have an IPv6 address?

1 0

[community/staging] update user research content
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 505f904e52a8a3505af2aa8e84a905b56cd8987a Author: Antonela <hola(a)antonela.me> Date: Wed Oct 16 11:27:29 2019 -0300 update user research content --- content/user-research/become-tester/contents.lr | 22 ++++++++++ content/user-research/contents.lr | 10 ++--- content/user-research/current/contents.lr | 19 --------- content/user-research/open/contents.lr | 54 +++++++++++++++++++++++++ content/user-research/signup/contents.lr | 19 --------- 5 files changed, 80 insertions(+), 44 deletions(-) diff --git a/content/user-research/become-tester/contents.lr b/content/user-research/become-tester/contents.lr new file mode 100644 index 0000000..248d815 --- /dev/null +++ b/content/user-research/become-tester/contents.lr @@ -0,0 +1,22 @@ +section: user research +--- +section_id: user-research +--- +color: primary +--- +image: eye +--- +_template: layout.html +--- +title: Become a tester +--- +subtitle: We regularly release Tor Browser Alpha versions to allow users to test software improvements and new ideas. +--- +key: 1 +--- +html: two-columns-page.html +--- +body: + +We regularly release Tor Browser Alpha versions to allow users to test software improvements and new ideas. +Sign up to be in our testing pool > diff --git a/content/user-research/contents.lr b/content/user-research/contents.lr index 164efb8..844d79d 100644 --- a/content/user-research/contents.lr +++ b/content/user-research/contents.lr @@ -4,15 +4,13 @@ section_id: user-research --- color: primary --- -_hidden: yes ---- _template: layout.html --- title: User Research --- subtitle: We conduct user research while also respecting user privacy. --- -cta: In progress +cta: Learn about Tor users --- key: 4 --- @@ -20,6 +18,6 @@ html: user-research.html --- body: -Protecting privacy is what we do at Tor. -So how do we collect meaningful user feedback without violating user consent? -We conduct all of our user research through in-person studies that users explicitly opt into. +## We conduct user research while also respecting user privacy. + +We practice human-centered design on building tools for internet freedom while we build community. Our user research is funded by the premises of consent, respect, and empathy. Make an impact in your local community by listening to our users. Learn how we do it and help Tor with user research. diff --git a/content/user-research/current/contents.lr b/content/user-research/current/contents.lr deleted file mode 100644 index 1283e37..0000000 --- a/content/user-research/current/contents.lr +++ /dev/null @@ -1,19 +0,0 @@ -section: user research ---- -section_id: user-research ---- -color: primary ---- -image: clipboard ---- -_template: layout.html ---- -title: Currently Testing Stuffs ---- -subtitle: Link to somewhere we csan update more than this webpage, even banners will be tedious if we do testing all the time. We can even oput some thing puilled from there and have it populated here. ---- -key: 1 ---- -html: user-research.html ---- -body: diff --git a/content/user-research/open/contents.lr b/content/user-research/open/contents.lr new file mode 100644 index 0000000..c0a9198 --- /dev/null +++ b/content/user-research/open/contents.lr @@ -0,0 +1,54 @@ +section: user research +--- +section_id: user-research +--- +color: primary +--- +image: eye +--- +_template: layout.html +--- +title: Open user research +--- +subtitle: We put our users in the center of our development process. That is how we bring privacy-enhancing technology to the ones who more need it. Explore what we are working on and start to run user research with your local community. +--- +key: 2 +--- +html: two-columns-page.html +--- +body: + +In this page you find the current needs to be run when testing Tor products, as well as methodologies and testing scripts. Before running a Tor user research, be sure you read our [Guidelines to be a User Researcher with Tor]. + +Tor Browser for Desktop +* [Usability Testing: Onboarding](https://link) +* [Usability Testing: Security Settings](https://link) +* [Usability Testing: New Identity](https://link) +* [Usability Testing: Warnings and Notifications](https://link) +* [Usability Testing: Circuit Display](https://link) + +Tor Browser for Android +* [Usability Testing: Onboarding](https://link) +* [Usability Testing: Security Settings](https://link) +* [Usability Testing: New Identity](https://link) +* [Usability Testing: Warnings and Notifications](https://link) + +### Onion Services +* [Usability Testing: Onion Security Indicator](https://trac.torproject.org/projects/tor/attachment/wiki/org/tea… +* [Usability Methodology: Onion Security Indicator](https://trac.torproject.org/projects/tor/attachment/wiki/org/tea… + +### Circuit Display +* [Usability Testing: Circuit Display](https://trac.torproject.org/projects/tor/attachment/wiki/org/teams… +* [Usability Methodology: Circuit Display](https://trac.torproject.org/projects/tor/attachment/wiki/org/teams… + +## Past User Research +On our commitment with an open design, we make public here our user research ran through the global-south. If you want to run user research with us, please [get in touch.](https://lists.torproject.org/cgi-bin/mailman/listinfo/ux) + +| Project | Methodology | Locations | Dates | Reporting | +| -------- | ----------- | --------- | --------- | ----- | +| Tor Launcher | Usability testing (.pdf) | Mumbai(IN) | Q118 | .pdf | +| Onion Security Indicator | Usability testing (.pdf) | Mumbai(IN), Kampala(UG), Valencia(ES), Mombasa(KE)| Q118, Q218 | .pdf | +| TB Circuit Display | Usability testing (.pdf) | Kampala(UG), Nairobi(KE), Mombasa(KE) | Q118, Q218 | .pdf | +| Tor Browser for Desktop | User needs discovery (.pdf) | Bogotá(CL), Cali(CL), Valle del Cauca(CL), Kampala(UG), Hoima(UG), Nairobi(KE) | 2018 | .pdf | +| Tor Browser for Android | User needs discovery (.pdf) | Bogotá(CL), Cali(CL), Valle del Cauca(CL), Kampala(UG), Hoima(UG), Nairobi(KE) | 2018 | .pdf | +| Tor Users Demographics | Survey (link) | Online | 2018 | .pdf | diff --git a/content/user-research/signup/contents.lr b/content/user-research/signup/contents.lr deleted file mode 100644 index 06cd047..0000000 --- a/content/user-research/signup/contents.lr +++ /dev/null @@ -1,19 +0,0 @@ -section: user research ---- -section_id: user-research ---- -color: primary ---- -image: eye ---- -_template: layout.html ---- -title: Sign up to be in our testing pool ---- -subtitle: Will you help us by becoming a Tor tester? Sign up for the user testing mailing list and we'll email you when there's a new test. We will never use your email for any other purposes. ---- -key: 2 ---- -html: user-research.html ---- -body:

1 0

[community/staging] IP can be many things, IP address is better here. reported by arma on irc
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit a317b8ceab32626ad58305a0ea3a1bec9d98e251 Author: emma peel <emma.peel(a)riseup.net> Date: Sat Oct 12 11:56:15 2019 +0200 IP can be many things, IP address is better here. reported by arma on irc --- content/onion-services/overview/contents.lr | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/onion-services/overview/contents.lr b/content/onion-services/overview/contents.lr index f70589a..330dea4 100644 --- a/content/onion-services/overview/contents.lr +++ b/content/onion-services/overview/contents.lr @@ -24,7 +24,8 @@ Onion services offer various privacy and security benefits to their users. ### Location hiding -An onion service's IP is protected. Onion services are an overlay network on top of TCP/IP, so in some sense IP addresses are not even meaningful to onion services: they are not even used in the protocol. +An onion service's IP address is protected. +Onion services are an overlay network on top of TCP/IP, so in some sense IP addresses are not even meaningful to onion services: they are not even used in the protocol. ### End-to-end authentication

1 0

[community/staging] made a few flow edits.lr
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 82f5f7c44dcf545c4b5fa75cf8ac58c4bc119acb Author: Stephanie A. Whited <steph(a)torproject.org> Date: Thu Oct 10 19:52:26 2019 +0000 made a few flow edits.lr --- content/onion-services/overview/contents.lr | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/onion-services/overview/contents.lr b/content/onion-services/overview/contents.lr index e747052..f70589a 100644 --- a/content/onion-services/overview/contents.lr +++ b/content/onion-services/overview/contents.lr @@ -24,11 +24,11 @@ Onion services offer various privacy and security benefits to their users. ### Location hiding -An onion service's IP is hidden. Onion services are an overlay network on top of TCP/IP, so in some sense IP addresses are not even meaningful to onion services: they are not even used in the protocol. +An onion service's IP is protected. Onion services are an overlay network on top of TCP/IP, so in some sense IP addresses are not even meaningful to onion services: they are not even used in the protocol. ### End-to-end authentication -When a user visits a particular onion, they know that the content they are seeing can only come from that particular onion and that no impersonation is possible. This is not the case with the normal web, where reaching a website does not mean that a man-in-the-middle did not reroute to some other location (e.g. DNS attacks). +When a user visits a particular onion, they know that the content they are seeing can only come from that particular onion. No impersonation is possible, which is generally not the case. Usually, reaching a website does not mean that a man-in-the-middle did not reroute to some other location (e.g. DNS attacks). ### End-to-end encryption @@ -36,18 +36,18 @@ Onion service traffic is encrypted from the client to the onion host. This is li ### NAT punching -Is your network filtered and you can't open ports on your firewall? This could happen if you are in a university campus, an office, an airport or pretty much anywhere. Onion services don't need open ports because they punch through NAT, since they only establish outgoing connections. +Is your network filtered and you can't open ports on your firewall? This could happen if you are in a university campus, an office, an airport, or pretty much anywhere. Onion services don't need open ports because they punch through NAT. They only establish outgoing connections. ## The Onion Service Protocol: Overview -Now the question becomes **what kind of protocol do we need to achieve all these properties?** In particular, on the normal web, we connect to an IP address and we are done, but in this case how do we connect to something that does not have an IP address? +Now the question becomes **what kind of protocol is needed to achieve all these properties?** Usually, people connect to an IP address and are done, but how can you connect to something that does not have an IP address? In particular, an onion service's address looks like this: `vww6ybal4bd7szmgncyruucpgfkqahzddi37ktceo3ah7ngmcopnpyyd.onion` -This looks weird and random because in reality it's the _identity public key_ of the onion service and that's one of the reasons we can achieve the security properties from above. +This looks weird and random because it's the _identity public key_ of the onion service. That's one of the reasons we can achieve the security properties above. -The general concept behind the onion service protocol is that we use the Tor network so that the client (Alice) can introduce itself to the service (Bob), and then sets up a rendezvous with the service. Here is a detailed breakdown of how this happens: +The onion service protocol uses the Tor network so that the client (Alice) can introduce itself to the service (Bob), and then set up a rendezvous point with the service over the Tor network. Here is a detailed breakdown of how this happens: ### Act 1: Where the onion service sets up its introduction points @@ -79,7 +79,7 @@ Now let's fast-forward to the point where an actual client wants to visit the se In this case, Alice (the client) has the onion address of Bob and she wants to visit it, so she connects to it with her Tor Browser. Now the next thing that needs to happen is that Alice goes to the _distributed hash table_ from the step above, and ask for the signed descriptor of Bob. -When Alice receives the signed descriptor she verifies the signature of the descriptor using the public key that is encoded in the onion address. +When Alice receives the signed descriptor, she verifies the signature of the descriptor using the public key that is encoded in the onion address. This provides the _end-to-end authentication_ security property, since we are now sure that this descriptor could only be produced by Bob and no one else. And inside the descriptor there are the introduction points which allow Alice to introduce herself to Bob. @@ -112,7 +112,7 @@ This provides _location hiding_ to this connection: ## Further resources -This was just a high-level overview of the Tor onion services protocol. Here are some more resources for the curious who want to learn more: +This was just a high-level overview of the Tor onion services protocol. Here are some more resources if you want to learn more: - The original Tor design paper describing the original design: https://svn.torproject.org/svn/projects/design-paper/tor-design.pdf

1 0

[community/staging] remove user-testing section
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 8d8d0bcf22ba5b481a3eecb7e1de6654dfc98a5b Author: Antonela <hola(a)antonela.me> Date: Wed Oct 16 11:18:48 2019 -0300 remove user-testing section we are going to use user-research because it the proper name for holding all the HCD methodologies we are running --- content/user-testing/current/contents.lr | 19 ------------------- content/user-testing/signup/contents.lr | 19 ------------------- 2 files changed, 38 deletions(-) diff --git a/content/user-testing/current/contents.lr b/content/user-testing/current/contents.lr deleted file mode 100644 index d71015f..0000000 --- a/content/user-testing/current/contents.lr +++ /dev/null @@ -1,19 +0,0 @@ -section: user testing ---- -section_id: user-testing ---- -color: primary ---- -image: clipboard ---- -_template: layout.html ---- -title: Currently Testing Stuffs[FIXME] ---- -subtitle: Link to somewhere we can update more than this webpage, even banners will be tedious if we do testing all the time. We can even output some thing pulled from there and have it populated here.[FIXME] ---- -key: 1 ---- -html: user-testing.html ---- -body: diff --git a/content/user-testing/signup/contents.lr b/content/user-testing/signup/contents.lr deleted file mode 100644 index e238096..0000000 --- a/content/user-testing/signup/contents.lr +++ /dev/null @@ -1,19 +0,0 @@ -section: user testing ---- -section_id: user-testing ---- -color: primary ---- -image: eye ---- -_template: layout.html ---- -title: Sign up to be in our testing pool ---- -subtitle: Will you help us by becoming a Tor tester? Sign up for the user testing mailing list and we'll email you when there's a new test. We will never use your email for any other purposes. ---- -key: 2 ---- -html: user-testing.html ---- -body:

1 0

[community/staging] backslash breaks the translation
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit e4e41083f5d5af557b87e7a44c452d31aa542763 Author: emma peel <emma.peel(a)riseup.net> Date: Sat Oct 5 08:47:22 2019 +0200 backslash breaks the translation --- content/relay-operations/technical-setup/guard/openbsd/contents.lr | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/relay-operations/technical-setup/guard/openbsd/contents.lr b/content/relay-operations/technical-setup/guard/openbsd/contents.lr index 24a5dd7..2c0ebd9 100644 --- a/content/relay-operations/technical-setup/guard/openbsd/contents.lr +++ b/content/relay-operations/technical-setup/guard/openbsd/contents.lr @@ -59,8 +59,8 @@ By default, OpenBSD maintains a rather low limit on the maximum number of open f Append the following section to `/etc/login.conf`: ``` -tor:\ - :openfiles-max=13500:\ +tor: + :openfiles-max=13500: :tc=daemon: ```

1 0

[community/staging] sort layout items
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 2f8c9270e48ea0dffa2ff7876c9b30bf1782e6e6 Author: Antonela <hola(a)antonela.me> Date: Wed Oct 16 11:49:39 2019 -0300 sort layout items --- content/localization/contents.lr | 4 ++-- content/onion-services/contents.lr | 2 +- content/relay-operations/contents.lr | 2 +- content/user-research/contents.lr | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/localization/contents.lr b/content/localization/contents.lr index e356bc4..00b6229 100644 --- a/content/localization/contents.lr +++ b/content/localization/contents.lr @@ -12,7 +12,7 @@ subtitle: We want Tor to work for everyone in the world, which means our softwar --- cta: Help us translate --- -key: 2 +key: 4 --- html: localization.html --- @@ -22,4 +22,4 @@ body: In order for Tor to work for everyone, it needs to speak everyone's languages. Our volunteer translation team works hard to make this a reality, and we can always use more help. -Our current translation priorities are translating [Tor Browser](https://torpat.ch/locales), Tor Browser documentation, and the [Tor Project website](https://torpat.ch/tpo-locales), but there are many other documents that we could use help translating as well. +Our current translation priorities are translating [Tor Browser](https://torpat.ch/locales), Tor Browser documentation, and the [Tor Project website](https://torpat.ch/tpo-locales), but there are many other documents that we could use help translating as well. diff --git a/content/onion-services/contents.lr b/content/onion-services/contents.lr index 9e51c1c..d9af6b7 100644 --- a/content/onion-services/contents.lr +++ b/content/onion-services/contents.lr @@ -12,7 +12,7 @@ subtitle: Onion services help you and your users defeat surveillance and censors --- cta: Grow your .onion --- -key: 6 +key: 3 --- html: onion-services.html --- diff --git a/content/relay-operations/contents.lr b/content/relay-operations/contents.lr index 40f0df7..6bf4422 100644 --- a/content/relay-operations/contents.lr +++ b/content/relay-operations/contents.lr @@ -12,7 +12,7 @@ subtitle: Relays are the backbone of the Tor network. Help make Tor stronger and --- cta: Grow the Tor network --- -key: 5 +key: 6 --- html: relay-operations.html --- diff --git a/content/user-research/contents.lr b/content/user-research/contents.lr index 844d79d..5787f2c 100644 --- a/content/user-research/contents.lr +++ b/content/user-research/contents.lr @@ -12,7 +12,7 @@ subtitle: We conduct user research while also respecting user privacy. --- cta: Learn about Tor users --- -key: 4 +key: 5 --- html: user-research.html ---

1 0