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

[community/staging] update l10n requirements as discussed at https://gitlab.torproject.org/tpo/community/l10n/-/issues/40020
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 60429f40196cec08a6130e45e494f423ce2c85f9 Author: emma peel <emma.peel(a)riseup.net> Date: Tue Mar 2 10:04:05 2021 +0100 update l10n requirements as discussed at https://gitlab.torproject.org/tpo/community/l10n/-/issues/40020 --- content/localization/becoming-tor-translator/contents.lr | 2 +- content/localization/current-status/contents.lr | 11 ++++------- content/localization/pick-a-project/contents.lr | 12 +++++++++++- 3 files changed, 16 insertions(+), 9 deletions(-) diff --git a/content/localization/becoming-tor-translator/contents.lr b/content/localization/becoming-tor-translator/contents.lr index 362df91..02298b7 100644 --- a/content/localization/becoming-tor-translator/contents.lr +++ b/content/localization/becoming-tor-translator/contents.lr @@ -8,7 +8,7 @@ _template: layout.html --- title: Becoming a Tor translator --- -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. +subtitle: Learn how to sign up and begin contributing. --- key: 1 --- diff --git a/content/localization/current-status/contents.lr b/content/localization/current-status/contents.lr index e9131f6..274b4ea 100644 --- a/content/localization/current-status/contents.lr +++ b/content/localization/current-status/contents.lr @@ -16,14 +16,11 @@ 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, you are still welcome to help us with these languages. +We have some languages more active, with a number of active and committed contributors (as French, Russian, Portuguese). Even when the translations are finished, you are still welcome to help us with these languages. 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. -Please consider [helping with translations](/localization/becoming-tor-translator/) in your native language. +You can see the open tickets about translation problems on our [bugtracker](https://gitlab.torproject.org/tpo/community/l10n/-/issues). -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 see the open tickets about translation problems on our [bugtracker](https://trac.torproject.org/projects/tor/query?status=!closed&c…. +Our documentation is very important for users around the world to be able to use Tor and Tor Browser: +This includes the Tor Browser User Manual, the Support Portal, the Tor Project Website and this website, the Community Portal. diff --git a/content/localization/pick-a-project/contents.lr b/content/localization/pick-a-project/contents.lr index f651937..ca6122c 100644 --- a/content/localization/pick-a-project/contents.lr +++ b/content/localization/pick-a-project/contents.lr @@ -19,9 +19,19 @@ We want our tools to be available and localized for anyone who wants to use them <img class="col-lg-6" src="../../static/images/localization/stats.png"> -Although we would value your contribution to any of the projects above, our most critical needs are Tor Browser, the Tor Browser User Manual, and our Support portal: +Please consider [helping with translations](/localization/becoming-tor-translator/) in your native language, but don't start a regional variant of your language if there is a more general language available (for example: contribute to the French translation, instead of French-Canada). + +The reason is that every language needs resources, a set of committed tranlators, makes compilations take longer, and takes more space in servers. +There are many files to translate and keep up to date to maintain a language for the Tor Project. Moreover, once translated there are always updates and more pages to translate. + +It is more scalable if we contribute to a translation that will benefit more users, and be up to date because it will count with the help of more volunteers. +For that we also ask you to form a team for your language: this way, all the contents can be reviewed by another person and the translation will be of better quality, and it is more possible that it is maintained. + +Although we would value your contribution to any of the projects above, our most critical needs are Tor Browser, the Tor Browser User Manual, and our Support Portal: * Tor Browser is translated in many different Transifex resources, but you can see the [Tor Browser total strings translated per language](https://torpat.ch/locales) to see where help is needed. * The Tor Browser User Manual is a very useful resource for new users that do not speak English, see [Tor Browser User Manual translation statistics](https://torpat.ch/manual-locales) or [translate](https://www.transifex.com/otf/tor-project-support-community-port… to help. * The [Support portal](https://support.torproject.org/) is also a valuable resource for all Tor users, see [Tor Support portal translation statistics](https://torpat.ch/support-locales) or [translate](https://www.transifex.com/otf/tor-project-support-community-port… to help. + +We are also translating this page, the Community Portal: * The [Community portal](https://community.torproject.org/) is this website, where you can find ways to contribute to Tor. Help us [translate](https://www.transifex.com/otf/tor-project-support-community-port… it.

1 0

[community/staging] Merge branch 'fix-typo'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit c1bd2668eb502ea780138ed7b5fa5e7d7eb69d86 Merge: 8449708 6d8f42f Author: gus <gus(a)torproject.org> Date: Wed Mar 3 13:25:56 2021 -0500 Merge branch 'fix-typo' content/onion-services/advanced/https/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

1 0

[community/staging] Add Focal Fossa as supported release in how to install obfs4proxy
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 2bfaeda62e50163bd02e0a4144b1f2208f1b18ce Author: kulsoomzahra <kulsoomzahra24(a)gmail.com> Date: Wed Mar 3 19:48:19 2021 +0530 Add Focal Fossa as supported release in how to install obfs4proxy Added to the docs that Ubuntu focal supports obfs4proxy package installation --- .../relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr index 8dfc9e7..4d25952 100644 --- a/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr +++ b/content/relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr @@ -15,7 +15,7 @@ Get the latest version of Tor. If you're on Debian stable, `sudo apt-get install ### 2. Install obfs4proxy On [Debian](https://packages.debian.org/search?keywords=obfs4proxy), the `obfs4proxy` package is available in unstable, testing, and stable. -On [Ubuntu](https://packages.ubuntu.com/search?keywords=obfs4proxy), bionic, cosmic, disco, and eoan have the package. +On [Ubuntu](https://packages.ubuntu.com/search?keywords=obfs4proxy), bionic, cosmic, disco, eoan, and focal have the package. If you're running any of them, `sudo apt-get install obfs4proxy` should work. If not, you can [build it from source](https://gitlab.com/yawning/obfs4#installation).

1 0

[community/staging] Merge branch 'update-goodbad-isps-de'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit c39a7ef7309aa0d8593dfbc06834c09cad1698bb Merge: c1bd266 681232c Author: gus <gus(a)torproject.org> Date: Wed Mar 3 13:37:14 2021 -0500 Merge branch 'update-goodbad-isps-de' .../community-resources/good-bad-isps/contents.lr | 35 ++++++++++++++-------- 1 file changed, 23 insertions(+), 12 deletions(-)

1 0

[community/staging] Revert "replace \ with \ U to prevent escaping errors" as it does
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 992989246e7632f6a6abea4b0e387212b22478af Author: emma peel <emma.peel(a)riseup.net> Date: Fri Mar 5 07:41:03 2021 +0100 Revert "replace \ with \U to prevent escaping errors" as it does not work in the server, only on my machine. This reverts commit 7e6ce5302f1b6b451397a31b6bdcf174d2f412be. --- .../technical-setup/bridge/windows/contents.lr | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/windows/contents.lr b/content/relay-operations/technical-setup/bridge/windows/contents.lr index 5ce0b6c..7bf3ddc 100644 --- a/content/relay-operations/technical-setup/bridge/windows/contents.lr +++ b/content/relay-operations/technical-setup/bridge/windows/contents.lr @@ -22,24 +22,24 @@ You will need to show hidden items and file name extensions. In your Explorer wi ### 2. Build files and relocate -Open up the Tor folder on your desktop. Double click `tor.exe`. Once the command prompt reads: `[notice] Bootstrapped 100% (done): Done`, close the window. This creates the folder `C:\Users\<user>\AppData\Roaming\tor\` (where `<user>` is your user name). +Open up the Tor folder on your desktop. Double click `tor.exe`. Once the command prompt reads: `[notice] Bootstrapped 100% (done): Done`, close the window. This creates the folder `C:\Users\<user>\AppData\Roaming\tor\` (where `<user>` is your user name). -From the Tor folder on your desktop, select all `.dll`'s and `.exe`'s and cut/paste them into the `C:\Users\<user>\AppData\Roaming\tor\` folder. +From the Tor folder on your desktop, select all `.dll`'s and `.exe`'s and cut/paste them into the `C:\Users\<user>\AppData\Roaming\tor\` folder. -Open up the Data folder on your desktop. Inside that Tor folder, select both `geoip` and `geoip6` and cut/paste them into the `C:\Users\<user>\AppData\Roaming\tor\` folder. +Open up the Data folder on your desktop. Inside that Tor folder, select both `geoip` and `geoip6` and cut/paste them into the `C:\Users\<user>\AppData\Roaming\tor\` folder. -Navigate to `C:\Users\<user>\Desktop\Tor Browser\Browser\TorBrowser\Tor\PluggableTransports`. Select `obfs4proxy.exe` and cut/paste it into the `C:\Users\<user>\AppData\Roaming\tor\` folder. +Navigate to `C:\Users\<user>\Desktop\Tor Browser\Browser\TorBrowser\Tor\PluggableTransports`. Select `obfs4proxy.exe` and cut/paste it into the `C:\Users\<user>\AppData\Roaming\tor\` folder. ### 3. Create and edit your Tor config file -In the `C:\Users\<user>\AppData\Roaming\tor\` folder, right-click on white space and select `New > Text Document`. Name the file `torrc`; there is no extension. +In the `C:\Users\<user>\AppData\Roaming\tor\` folder, right-click on white space and select `New > Text Document`. Name the file `torrc`; there is no extension. Double-click on the `torrc` file. When prompted *How do you want to open this file?*, select `Notepad`. Add the following: ``` -Log notice file C:\Users\<user>\AppData\Roaming\tor\notice.log -GeoIPFile C:\Users\<user>\AppData\Roaming\tor\geoip -GeoIPv6File C:\Users\<user>\AppData\Roaming\tor\geoip6 +Log notice file C:\Users\<user>\AppData\Roaming\tor\notice.log +GeoIPFile C:\Users\<user>\AppData\Roaming\tor\geoip +GeoIPv6File C:\Users\<user>\AppData\Roaming\tor\geoip6 BridgeRelay 1 @@ -48,7 +48,7 @@ BridgeRelay 1 # 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 C:\Users\<user>\AppData\Roaming\tor\obfs4proxy.exe +ServerTransportPlugin obfs4 exec C:\Users\<user>\AppData\Roaming\tor\obfs4proxy.exe # 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. @@ -77,11 +77,11 @@ Don't forget to change the `ORPort`, `ServerTransportListenAddr`, `ContactInfo`, ### 4. Start tor -Open up the Command Prompt App. Change your directory with: `cd C:\Users\<user>\AppData\Roaming\tor\`. Type: `tor.exe -f torrc`. +Open up the Command Prompt App. Change your directory with: `cd C:\Users\<user>\AppData\Roaming\tor\`. Type: `tor.exe -f torrc`. ### 5. Monitor your logs -To confirm your bridge is running with no issues, you should see something like this in `C:\Users\<user>\AppData\Roaming\tor\notice.log`. +To confirm your bridge is running with no issues, you should see something like this in `C:\Users\<user>\AppData\Roaming\tor\notice.log`. ``` [notice] Your Tor server's identity key fingerprint is '<NICKNAME> <FINGERPRINT>'

1 0

[community/staging] It's Tor, not TOR.
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit a351353d7946febc92db151ae13210de273c638f Author: gus <gus(a)torproject.org> Date: Wed Mar 3 13:40:32 2021 -0500 It's Tor, not TOR. --- .../relay-operations/community-resources/good-bad-isps/contents.lr | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/relay-operations/community-resources/good-bad-isps/contents.lr b/content/relay-operations/community-resources/good-bad-isps/contents.lr index c6dca64..dc4bb3c 100644 --- a/content/relay-operations/community-resources/good-bad-isps/contents.lr +++ b/content/relay-operations/community-resources/good-bad-isps/contents.lr @@ -95,20 +95,20 @@ For network diversity and stronger anonymity, you should avoid providers and cou | [linevast](https://www.linevast.de) | AS201206 | No | No | No | | 03/2021 | | [Server4You](https://www.server4you.de)| AS131914 | No | No | No | - | 03/2021 | | [Hetzner](http://hetzner.de) | AS24940 | Yes | Yes | Yes | Offers good dedicated root servers for a good price. "It is not a Problem, however, abuse reports can lead to a server lock" | 03/2021 | -| [Contabo](https://contabo.de) | AS51167 | No | No | No | TOR prohibited due to terms of service | 03/2021 | +| [Contabo](https://contabo.de) | AS51167 | No | No | No | Tor prohibited due to terms of service | 03/2021 | | [Strato](https://strato.de) | AS6724 | No | No | No | - | 03/2021 | | [PraHost](https://www.prahost.com) | - | Yes | Yes | Yes | "If there is any abuse notice received, you need to solve it in given time, else your IP will be blocked until you take any action" | 03/2021 | | [DomainFactory](https://www.df.eu/de/cloud-hosting/cloud-server) | AS34011 | Yes | Yes | Yes | Only allowed on jiffybox | 03/2021 | | [NetCologne](https://www.netcologne.de) | - | - | Yes | Yes | - | - | | [Signaltransmitter](https://signaltransmitter.de) | AS24961 | Yes | Yes | Yes | "In principle, we do not limit our services apart from mining bitcoins" | 03/2021 | -| [Netcup](https://www.netcup.de) | AS197540 | Yes | Yes | Yes | TOR allowed on VPS and rootservers | 03/2021 | +| [Netcup](https://www.netcup.de) | AS197540 | Yes | Yes | Yes | Tor allowed on VPS and rootservers | 03/2021 | | [Onyxhosting](https://onyxhosting.de) | - | No | No | No | - | 03/2021 | | [IP-Projects](https://www.ip-projects.de) | AS48314 | No | No | No | - | 03/2021 | | [Lansol](https://www.lansol.de) | - | No | No | No | - | 03/2021 | | [delta.networks](https://www.delta-networks.de) | AS9937 | No | No | No | - | 03/2021 | | [VPS2Day](https://www.vps2day.com) | AS58329 | Yes | Yes | No | Exit nodes prohibited due to terms of service | 03/2021 | | [Serverprofis](https://www.serverprofis.de) | AS5539 | No | No | No | - | 03/2021 | -| [manitu](https://www.manitu.de) | AS34240 | No | No | No | "I´m sorry - even if the network has great added value for specific purposes, we have decided to prohibit TOR services on our network" | 03/2021 | +| [manitu](https://www.manitu.de) | AS34240 | No | No | No | "I'm sorry - even if the network has great added value for specific purposes, we have decided to prohibit Tor services on our network" | 03/2021 | | [active-servers](https://www.active-servers.com) | AS197071 | Yes | Yes | Yes | "Usually this leads to abuse mails, which only cause trouble – but basically we have nothing against it" | 03/2021 | | [UltraVPS](https://www.ultravps.eu) | - | No | No | No | "We are not the right host for your project" | 03/2021 |

1 0

[community/staging] Add Onion Balance v3 enhancements project to list of GSoC projects
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit db3e2355c4592471126916729a3c99e99fb63a84 Author: Pili Guerra <pili(a)piliguerra.com> Date: Mon Mar 8 13:18:24 2021 +0100 Add Onion Balance v3 enhancements project to list of GSoC projects --- content/gsoc/onion-balance-v3/contents.lr | 57 +++++++++++++++++++++++++++++++ 1 file changed, 57 insertions(+) diff --git a/content/gsoc/onion-balance-v3/contents.lr b/content/gsoc/onion-balance-v3/contents.lr new file mode 100644 index 0000000..53cb558 --- /dev/null +++ b/content/gsoc/onion-balance-v3/contents.lr @@ -0,0 +1,57 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 3 +--- +languages: +Python +--- +mentors: +asn +--- +difficulty: medium +--- +title: Onion Balance V3 Enhancements +--- +subtitle: + +OnionBalance allows Tor onion service requests to be distributed across multiple backend Tor instances. OnionBalance provides load-balancing while also making onion services more resilient and reliable by eliminating single points-of-failure. +--- +body: + +# Problem + +Onion services have been around for a while. During the past few years, they have been deployed by many serious websites like major media organizations (like the Washington Post), search engines (such as DuckDuckGo) and critical Internet infrastructure (e.g. PGP keyservers). This has been a great opportunity for us, the onion balance development team, since our code has been hardened and tested by the sheer volume of clients that use it every day. + +Onionbalance is one of the standard ways onion service administrators can load balance onion services, but it didn't work for v3 onions. Until [recently](https://blog.torproject.org/cooking-onions-reclaiming-onionbalanc… when we released a new version of Onionbalance that supports v3 onion services. + +# Proposal + +We would like someone to help us implement some of the currently [open feature requests](https://github.com/asn-d6/onionbalance/labels/patches-welcome). + +In particular, we would like to implement some or all of the following features: + +- Support for v3 ["distinct descriptor" mode](https://onionbalance-v3.readthedocs.io/en/latest/v2/design.html#choice-of-introduction-points). +This mode allows Onionbalance v2 to load-balance more than 10 backend instances, whereas currently Onionbalance v3 has a limit of 8 backend instances. In theory, Onionbalance could load-balance hundreds of backend instances by publishing descriptors at small time intervals that contain introduction points from a different subset of those instances each time. +- Minimize the differences between both v3 and other descriptors. +Currently Onionbalance v3 descriptors can look different from other descriptors, which makes it possible for clients and HSDirs to learn that a service is using Onionbalance. This can be an issue for more [advanced onion service threat models](https://github.com/mikeperry-tor/vanguards/blob/master/README_SECUR…. +- Enable client authorization on the frontend service. +This may be needed in specialized use cases. Adding this feature would first require implementing client authorization support to Stem v3 descriptors and then using that feature in Onionbalance. +- Allow the ability to transfer your existing v3 onion service to Onionbalance. + + +# Resources + +- [OnionBalance v3 repo on github](https://github.com/asn-d6/onionbalance) +- [OnionBalance Documentation](https://onionbalance-v3.readthedocs.io/en/latest/v3/tutorial-v3.html#tutorial-v3) \ No newline at end of file

1 0

[community/staging] Merge branch 'add-focal-support'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 11c25c357aa5a34790156217cb2c9fbaf2a1d15d Merge: 860810f 2bfaeda Author: gus <gus(a)torproject.org> Date: Thu Mar 4 09:08:20 2021 -0500 Merge branch 'add-focal-support' .../relay-operations/technical-setup/bridge/debian-ubuntu/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

1 0

[community/staging] Add new project to list of potential GSoC projects
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit d64491d7bf9a8b8c4dc1d44ebcfd21d0f5d551bc Author: Pili Guerra <pili(a)piliguerra.com> Date: Mon Mar 8 12:43:26 2021 +0100 Add new project to list of potential GSoC projects --- content/gsoc/alexa-captcha-monitoring/contents.lr | 83 +++++++++++++++++++++++ 1 file changed, 83 insertions(+) diff --git a/content/gsoc/alexa-captcha-monitoring/contents.lr b/content/gsoc/alexa-captcha-monitoring/contents.lr new file mode 100644 index 0000000..c8d03bb --- /dev/null +++ b/content/gsoc/alexa-captcha-monitoring/contents.lr @@ -0,0 +1,83 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +completed: False +--- +url: /alexa-captcha-monitoring +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 1 +--- +languages: +python +javascript +--- +mentors: +GeKo +arma +--- +difficulty: medium +--- +title: Alexa Top Sites Captcha and Tor Block Monitoring +--- +subtitle: + +This project should implement a mechanism to track the rate that Alexa Top 500 webpages return Captchas to or directly block Tor users over time. + +--- +body: + +# Problem + +A large number of Tor users report getting hit by infinite Captcha loops when visiting some of the most popular websites, such as Reddit, Twitter or YouTube. This makes them feel punished for using Tor to protect their privacy and prevents them from legitimately accessing websites. + +# Proposal + +For this project we would like to track in practice how often [Alexa Top 500 websites](https://www.alexa.com/topsites) return Captchas to Tor clients. + +During GSoC 2020, we had a project to track captchas from Cloudflare fronted websites. This project would build upon this work to further test other popular websites. + +The project should consist of an automated way to systematically test a selection of [these websites](https://www.alexa.com/topsites) and record whether there is a difference in behaviour when a connection comes from various Tor exit IPs versus non-Tor exit IPs. For example, in the case where it seems like connections from Tor users are being discriminated against, we should record whether the user is presented with a captcha or some other error, e.g Forbidden or Service Temporarily Unavailable. Some discussion regarding this issue can be found [here](https://gitlab.torproject.org/tpo/community/support/-/issues/40013). + +Our proposed approach consists of: + +1. Writing a web client to periodically fetch a selection of the [Alexa Top Sites](https://www.alexa.com/topsites) via Tor and record how often a Captcha or failure is returned. +1. Record and graph the various types of failure (including Captchas) vs real page rates +1. Using the pre-existing architecture, run a second client that does not fetch this webpage via Tor. This will allow us to contrast and compare how these sites respond to Tor Browser vs other browsers. +1. Track and publish these details publicly + +There are two interesting metrics to track over time: + +- the fraction of exit relays that are getting hit with Captchas and failures, and +- the chance that a Tor client, choosing an exit relay in the normal weighted faction, will get hit by a Captcha or a failure. + +Then there are other interesting patterns to look for: + +- Are certain IP addresses punished consistently and others never punished? +- Is whether you get a failure much more probabilistic and transient? +- Does that pattern change over time? + +# Getting Started + +As this project builds upon an existing project, in order to demonstrate your skills and familiarise yourself with this project you may want to: + +1. Familiarise yourself and start experimenting with various web clients to fetch pages via Tor, bearing in mind you may need to adapt them to your needs if they are lacking the required functionality. +1. Check out the existing [Captcha Scanner](https://dashboard.captcha.wtf/) and [code](https://gitlab.torproject.org/woswos/CAPTCHA-Monitor) +1. Read the comments in ticket [40013](https://gitlab.torproject.org/tpo/community/support/-/issues/40013) and the [original project ticket](https://gitlab.torproject.org/legacy/trac/-/issues/33010) for more ideas. + +# Resources + +There is pre-existing research by the Berkeley ICSI group which includes these sorts of checks: + +- https://www.freehaven.net/anonbib/#differential-ndss2016 +- https://www.freehaven.net/anonbib/#exit-blocking2017

1 0

[community/staging] Merge branch 'onion-guide-fanzine'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 860810f51271ae7b389a571e210de47bd33c4ffe Merge: a351353 f876026 Author: gus <gus(a)torproject.org> Date: Thu Mar 4 09:04:01 2021 -0500 Merge branch 'onion-guide-fanzine' .../outreach/print/onion-guide-fanzine-EN.pdf | Bin 0 -> 343902 bytes .../outreach/print/onion-guide-fanzine-ES.pdf | Bin 0 -> 342504 bytes .../outreach/print/onion-guide-fanzine-PT_BR.pdf | Bin 0 -> 345662 bytes .../images/outreach/print/onion-guide-fanzine.pdf | Bin 346542 -> 0 bytes databags/outreach-materials.ini | 22 +++++++++++++++++---- 5 files changed, 18 insertions(+), 4 deletions(-)

1 0