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

[community/staging] Change obfs4proxy patch in OpenBSD install doc
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit fd0862583435e73d0c04f7ee49b5e57fe16c1dba Author: Nick Gnazzo <nickgnazzo(a)icloud.com> Date: Thu Sep 12 13:11:52 2019 -0400 Change obfs4proxy patch in OpenBSD install doc By default, the 'obfs4proxy' in OpenBSD 6.5 seems to install the obfs4proxy binary in /usr/local/bin, as opposed to /usr/bin. --- content/relay-operations/technical-setup/bridge/openbsd/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr index 55b8f60..7bb27e3 100644 --- a/content/relay-operations/technical-setup/bridge/openbsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/openbsd/contents.lr @@ -26,7 +26,7 @@ BridgeRelay 1 # censors may be scanning the Internet for this port. ORPort TODO1 -ServerTransportPlugin obfs4 exec /usr/bin/obfs4proxy +ServerTransportPlugin obfs4 exec /usr/local/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.

1 0

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

21 Mar '21

commit f96b32d918d75b76c86723ae7b38e7bd49eae6ed Author: Stephanie A. Whited <steph(a)torproject.org> Date: Thu Sep 19 16:17:56 2019 +0000 Editflowandgrammar.lr --- content/localization/contents.lr | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/localization/contents.lr b/content/localization/contents.lr index ccdc74d..e356bc4 100644 --- a/content/localization/contents.lr +++ b/content/localization/contents.lr @@ -8,9 +8,9 @@ _template: layout.html --- title: Localization --- -subtitle: We want Tor to work for everyone in the world, which means a lot of languages. +subtitle: We want Tor to work for everyone in the world, which means our software must be translated into a lot of languages. --- -cta: Help us to translate +cta: Help us translate --- key: 2 --- @@ -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 the [Tor Browser](https://torpat.ch/locales), its documentation and the [Tor Project website](https://torpat.ch/tpo-locales), and there are always other documents to translate. +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.

1 0

[community/staging] breadcrumbs go full-width
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit d07015523c9605da09289c1d130dfb2216e55b49 Author: Antonela <hola(a)antonela.me> Date: Wed Sep 18 10:16:37 2019 -0300 breadcrumbs go full-width close #68 --- lego | 2 +- templates/two-columns-page.html | 8 +++++--- 2 files changed, 6 insertions(+), 4 deletions(-) diff --git a/lego b/lego index 09c5813..8cb5f20 160000 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 09c5813e895e67104dbdcf15bfec66367bd11790 +Subproject commit 8cb5f20089a163b0a5134d841248778cb518bdf2 diff --git a/templates/two-columns-page.html b/templates/two-columns-page.html index a4fa3f6..5151905 100644 --- a/templates/two-columns-page.html +++ b/templates/two-columns-page.html @@ -1,7 +1,9 @@ -<div class="row pt-5"> + +{% include 'breadcrumb.html' %} + +<div class="row"> {% include 'sidenav.html' %} - <div class="col-sm-12 col-xs-12 col-md-8 col-lg-8 mr-auto {{ bag('alternatives', this.alt, 'order') }}"> - {% include 'breadcrumb.html' %} + <div class="col-sm-12 col-xs-12 col-md-8 col-lg-8 pt-3 mr-auto {{ bag('alternatives', this.alt, 'order') }}"> {{ this.body }} <div class="row"> {% for child in this.children|sort(attribute='key') %}

1 0

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

21 Mar '21

commit 929778fb1e80405ebdf7e74c40d35d567e6d2d77 Author: Stephanie A. Whited <steph(a)torproject.org> Date: Thu Sep 19 15:51:08 2019 +0000 FlowAndGrammarEdit.lr --- content/localization/current-status/contents.lr | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/localization/current-status/contents.lr b/content/localization/current-status/contents.lr index 1f539df..e9131f6 100644 --- a/content/localization/current-status/contents.lr +++ b/content/localization/current-status/contents.lr @@ -16,14 +16,14 @@ html: two-columns-page.html --- body: -We have some languages in very good shape, with a number of active and committed contributors (as French, Spanish, Russian, Portuguese). Even when the translations are finished, we always welcome more contributors to this languages. +We have some languages in very good shape, with a number of active and committed contributors (as French, Spanish, Russian, Portuguese). Even when the translations are finished, you are still welcome to help us with these languages. -We also have a lot of languages with incomplete translations, maybe spoken by less numbers of people, but still important to improve access to the Tor network for people that does not speak English. +Our translations are incomplete for a lot of languages. They may be spoken by fewer people around the world, but it is still critical that we improve access to Tor for people who do not speak English. -We are committed to provide translations to more languagues, please consider [helping with translations](/localization/becoming-tor-translator/) to your native language. +Please consider [helping with translations](/localization/becoming-tor-translator/) in your native language. -The most important languages we need help with at the moment are: Farsi (Persian), Arabic and Korean. But many other languages are being translated, as you can see here: +Right now, we need the most help with Farsi (Persian), Arabic, and Korean. But many other languages are being translated, as you can see here: <img class="col-lg-6" src="../../static/images/localization/stats.png"> -You can also see the open tickets about translation problems on our [bugtracker](https://trac.torproject.org/projects/tor/query?status=!closed&c…. +You can see the open tickets about translation problems on our [bugtracker](https://trac.torproject.org/projects/tor/query?status=!closed&c….

1 0

[community/staging] Fix template hero spacing
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 315f634e7bf8c0ca58ad99d7ba48f5207447b701 Author: hiro <hiro(a)torproject.org> Date: Wed Sep 18 12:29:54 2019 +0200 Fix template hero spacing --- lego | 2 +- templates/hero.html | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/lego b/lego index 8cb5f20..09c5813 160000 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit 8cb5f20089a163b0a5134d841248778cb518bdf2 +Subproject commit 09c5813e895e67104dbdcf15bfec66367bd11790 diff --git a/templates/hero.html b/templates/hero.html index 4b096aa..3a8f7c0 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">{% block section %}{{ this.section }}{% endblock %}</h6> + <h6 class="mx-auto text-white pt-3">{% block section %}{{ this.section }}{% endblock %}</h6> </div> <div class="row"> <h2 class="mx-auto display-3 text-white">{% block title %}{{ this.title }}{% endblock %}</h2>

1 0

[community/staging] Improve Consistency
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit d556fe5afce4b2c24c8264f1db5ce1f6d2484ddf Author: Aadi Bajpai <me(a)aadibajpai.me> Date: Fri Sep 20 08:03:11 2019 +0530 Improve Consistency --- content/onion-services/setup/contents.lr | 4 ++-- databags/pagenav+en.ini | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/onion-services/setup/contents.lr b/content/onion-services/setup/contents.lr index 784cf45..a33df07 100644 --- a/content/onion-services/setup/contents.lr +++ b/content/onion-services/setup/contents.lr @@ -8,9 +8,9 @@ image: cloud-upload-alt --- _template: layout.html --- -title: Set up your .onion Service +title: Set up your Onion Service --- -subtitle: Learn how to set up a .onion of your very own. +subtitle: Learn how to set up a .onion site of your very own. --- key: 1 --- diff --git a/databags/pagenav+en.ini b/databags/pagenav+en.ini index cb5b415..7d03cec 100644 --- a/databags/pagenav+en.ini +++ b/databags/pagenav+en.ini @@ -16,4 +16,4 @@ label = Relay Operations [onion-services] path = onion-services -label = .Onion Services +label = Onion Services

1 0

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

21 Mar '21

commit 35a5ad7d4bf2b651d314e50cbd0ff84cf398ace8 Author: Stephanie A. Whited <steph(a)torproject.org> Date: Fri Sep 20 07:53:41 2019 +0000 Update contents.lr

1 0

[community/staging] Use Docker's 'latest' tag for up-to-date image.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 2879ca75eb9411fe4060c2ed9503dcbba3b0d871 Author: Philipp Winter <phw(a)nymity.ch> Date: Thu Sep 19 12:28:45 2019 -0700 Use Docker's 'latest' tag for up-to-date image. --- content/relay-operations/technical-setup/bridge/docker/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index bf5f5b1..f82a65e 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -8,7 +8,7 @@ body: We are maintaining a docker container that allows you to quickly set up an obfs4 bridge. First, fetch the container: -`docker pull phwinter/obfs4-bridge:0.2` +`docker pull phwinter/obfs4-bridge:latest` Now, it's time to run the container. We maintain a script that automatically determines a free OR and obfs4 port for you. The script only requires your email address as argument: ```

1 0

[community/staging] README.md small style fixes
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 558fa7e9a53cb1a53570b18c51cdeb6d0ce7e632 Author: Pili Guerra <pili(a)piliguerra.com> Date: Fri Sep 20 12:36:34 2019 +0200 README.md small style fixes --- README.md | 14 ++------------ 1 file changed, 2 insertions(+), 12 deletions(-) diff --git a/README.md b/README.md index 1bc2893..f196cd5 100644 --- a/README.md +++ b/README.md @@ -68,17 +68,7 @@ If you want to contribute to the Community portal, we will be happy to help you. This is the workflow that Tor Internal people should use when making changes on the Community Portal: -1. When starting work on an issue or content, please assign the issue to yourself and move into the `Doing` column on the [Community Portal Project Board](https://dip.torproject.org/web/community/-/boards). You can follow the process outlined in ["How to send a merge request or propose a change"](https://dip.torproject.org/web/tpo/wikis/Git-flow-and-merge-requests#how-to-send-a-merge-request-or-propose-a-change) to work on your changes. e.g -``` -# Start a new feature -git checkout -b new-feature master -# Edit some files -git add <file> -git commit -m "Start a feature" -# Edit some files -git add <file> -git commit -m "Finish a feature" -``` +1. When starting work on an issue or content, please assign the issue to yourself and move into the `Doing` column on the [Community Portal Project Board](https://dip.torproject.org/web/community/-/boards). You can follow the process outlined in ["How to send a merge request or propose a change"](https://dip.torproject.org/web/tpo/wikis/Git-flow-and-merge-requests#how-to-send-a-merge-request-or-propose-a-change) to work on your changes. 2. To view your changes on the website, you can [run lektor locally](https://dip.torproject.org/web/tpo/wikis/Compiling-a-local-version… 3. Once you are happy with your work, push your changes to `develop` branch and move to `needs-review` column on the [Community Portal Project Board](https://dip.torproject.org/web/community/-/boards) 4. Add a comment to the issue, tagging the reviewer, e.g `@steph`, with: @@ -86,7 +76,7 @@ git commit -m "Finish a feature" - Contents file, containing your changes where it would be located on the **reviewer's repo** e.g `https://dip.torproject.org/steph/community/blob/develop/content/onion-services/contents.lr` - For the review workflow, please see (Reviewer Workflow) 5. Once the work has been reviewed and any necessary changes and merge request has been made, a repo maintainer or team members with write access to gitweb master will then merge or cherry-pick these changes to master, following the workflow outlined in [How to use our git flow](https://dip.torproject.org/web/tpo/wikis/Git-flow-and-merge-requests#… -6. Merger should then move the the ticket to the `Closed` column +6. Merger should then move the the ticket to the `Closed` column. ### Reviewer Workflow

1 0

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

21 Mar '21

commit aa02a195d6aed33e0bf1d32040ef93db519438eb Author: Stephanie A. Whited <steph(a)torproject.org> Date: Fri Sep 20 08:04:01 2019 +0000 Update contents.lr --- content/onion-services/overview/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/onion-services/overview/contents.lr b/content/onion-services/overview/contents.lr index c85306f..e747052 100644 --- a/content/onion-services/overview/contents.lr +++ b/content/onion-services/overview/contents.lr @@ -24,7 +24,7 @@ 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 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. ### End-to-end authentication

1 0