[tor-commits] [community/translations] update contents
emmapeel at torproject.org
emmapeel at torproject.org
Sat Mar 27 06:41:12 UTC 2021
commit 340a371e3e661ad72815aea476e9aa2112aae6db
Author: emma peel <emma.peel at riseup.net>
Date: Fri Mar 26 16:01:24 2021 +0100
update contents
---
.../overview/tor-onion-services-1.png | Bin 17222 -> 0 bytes
.../overview/tor-onion-services-4.png | Bin 21419 -> 0 bytes
.../images/outreach/print/onion-guide-fanzine.pdf | Bin 346542 -> 0 bytes
.../gsoc/cloudflare-captcha-monitoring/contents.lr | 82 --------------
content/gsoc/gettor-distribution/contents.lr | 50 ---------
content/gsoc/onion-toolbox/contents.lr | 67 ------------
content/gsoc/ooni-explorer-findings/contents.lr | 82 --------------
content/gsoc/ooni-explorer-testing/contents.lr | 53 ---------
.../ooni-probe-desktop-custom-urls/contents.lr | 72 -------------
content/gsoc/privacy-aware-geo-lookup/contents.lr | 56 ----------
content/gsoc/privacy-friendly-web/contents.lr | 59 ----------
.../gsoc/salmon-bridge-distribution/contents.lr | 72 -------------
content/gsoc/snowflake-android-proxy/contents.lr | 72 -------------
content/gsoc/tor-keygen/contents.lr | 49 ---------
content/gsoc/tor-relay-ipv6-support/contents.lr | 120 ---------------------
.../localization/translation-problem/contents.lr | 4 +-
databags/training-resources.json | 14 ++-
17 files changed, 14 insertions(+), 838 deletions(-)
diff --git a/assets/static/images/onion-services/overview/tor-onion-services-1.png b/assets/static/images/onion-services/overview/tor-onion-services-1.png
deleted file mode 100644
index 75de366..0000000
Binary files a/assets/static/images/onion-services/overview/tor-onion-services-1.png and /dev/null differ
diff --git a/assets/static/images/onion-services/overview/tor-onion-services-4.png b/assets/static/images/onion-services/overview/tor-onion-services-4.png
deleted file mode 100644
index 88db970..0000000
Binary files a/assets/static/images/onion-services/overview/tor-onion-services-4.png and /dev/null differ
diff --git a/assets/static/images/outreach/print/onion-guide-fanzine.pdf b/assets/static/images/outreach/print/onion-guide-fanzine.pdf
deleted file mode 100644
index dd446d9..0000000
Binary files a/assets/static/images/outreach/print/onion-guide-fanzine.pdf and /dev/null differ
diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/cloudflare-captcha-monitoring/contents.lr
index b8e3346..e69de29 100644
--- a/content/gsoc/cloudflare-captcha-monitoring/contents.lr
+++ b/content/gsoc/cloudflare-captcha-monitoring/contents.lr
@@ -1,82 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: False
----
-completed: True
----
-url: https://gitlab.torproject.org/woswos/CAPTCHA-Monitor
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 1
----
-languages:
-python
-javascript
----
-mentors:
-GeKo
-arma
----
-difficulty: medium
----
-title: Cloudflare Captcha Monitoring
----
-subtitle:
-
-This project should implement a mechanism to track the rate that Cloudflare fronted webpages return Captchas to Tor users over time.
-
----
-body:
-
-# Problem
-
-A large number of Tor users report getting hit by infinite Captcha loops when visiting webpages fronted by Cloudflare. 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 Cloudflare fronted webpages return Captchas to Tor clients.
-
-Our proposed approach consists of:
-
-1. Setting up a very simple static webpage to be fronted by Cloudflare
-2. Write a web client to periodically fetch this static webpage via Tor and record how often a Captcha is returned
-3. Record and graph Captcha vs real page rates
-4. 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 Cloudflare responds to Tor Browser vs other browsers.
-5. 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
-- the chance that a Tor client, choosing an exit relay in the normal weighted faction, will get hit by a Captcha.
-
-Then there are other interesting patterns to look for:
-
-- Are certain IP addresses punished consistently and others never punished?
-- Is whether you get a Captcha much more probabilistic and transient?
-- Does that pattern change over time?
-
-# Getting Started
-
-As this is a new project, in order to demonstrate your skills and familiarise yourself with this project you may want to:
-
-1. Set up the required infrastructure for this project e.g by setting up a very simple static webpage to be fronted by Cloudflare.
-2. 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.
-3. Read the comments in ticket [#33010](https://trac.torproject.org/projects/tor/ticket/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
-
-For the original ticket and discussion, please see ticket [#33010](http://bugs.torproject.org/33010)
\ No newline at end of file
diff --git a/content/gsoc/gettor-distribution/contents.lr b/content/gsoc/gettor-distribution/contents.lr
deleted file mode 100644
index 5639af3..0000000
--- a/content/gsoc/gettor-distribution/contents.lr
+++ /dev/null
@@ -1,50 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: False
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 2
----
-languages:
-python
-ansible
----
-org: Tor
----
-mentors:
-cohosh
-hiro
----
-difficulty:
----
-title: Implement new distribution methods for GetTor
----
-subtitle:
-
-This project should implement a feature to distribute Tor Browser downloads through Telegram or Facebook messenger.
-
----
-body:
-
-# Problem
-
-Tor Browser ships with a few different anti-censorship tools to allow people free and open access to Internet content. However, some places censor Tor Browser downloads, making it difficult for users to install it in the first place.
-
-#Â Proposal
-
-[GetTor](https://gettor.torproject.org/) is a system for distributing Tor Browser using alternative methods such as email or Twitter to send users authenticated links to Tor Browser binaries.
-
-We are looking to expand the ways in which GetTor distributes Tor Browser binaries to make it easier for people to download and install Tor Browser. This project would consist in implementing a feature in GetTor to distribute Tor Browser downloads through Telegram and/or Facebook messenger.
-
-# Resources
-
-- GetTor repo on github: https://github.com/torproject/gettor
\ No newline at end of file
diff --git a/content/gsoc/onion-toolbox/contents.lr b/content/gsoc/onion-toolbox/contents.lr
deleted file mode 100644
index f1c0b0e..0000000
--- a/content/gsoc/onion-toolbox/contents.lr
+++ /dev/null
@@ -1,67 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: False
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 3
----
-languages:
-Python
-Docker
-PythonQt5
----
-mentors:
-hiro
-asn
----
-difficulty: medium
----
-title: Onion Tool Box
----
-subtitle:
-
-Myonion is a developer tool box, providing a command line interface and a GUI to configure and deploy existing services via .onion. The idea behind myonion is to make onion services accessible to developers that might be interested to innovate in the privacy space, building applications that are designed for privacy and security.
----
-body:
-
-#Â Problem
-
-It is not necessarily difficult to use onion services, but it might be tricky to configure a web service to be offered via .onion so that it doesn’t leak sensitive information.
-
-There are detailed [guides](https://riseup.net/en/security/network-security/tor/onionservices-best-practices) available for users that would like to offer a web application via .onion and some tools have been developed to help service operators: discover known misconfiguration or [vulnerabilities](https://onionscan.org/) or deploy an [onion site](https://github.com/alecmuffett/eotk).
-
-Involving a wider developer community can help creating a better image of Tor and onion services, replacing the “dark net†narrative with the secure and private web one.
-
-Onion services can also be relevant to all those people interested in the “zero-trust†strategy. The concept behind zero-trust is to adopt strategies and tools to help prevent data breaches by eliminating the concept of trust from an organization’s network architecture, with the principle of never trust, always verify.
-
-Ultimately myonion is about creating a better experience for onion services developers and operators and therefore fostering a more legitimate onion service ecosystem.
-
-#Â Proposal
-
-Myonion is a developer tool box, providing a command line interface and a GUI to configure and deploy existing services via .onion. A minimal prototype for myonion already [exists](https://github.com/hiromipaw/myonion).
-
-Someone that may want to run an onion service can use the myonion wrapper app to start a .onion from their computer and share a static website or a web application.
-
-Myonion can also be used to deploy the resulting configured app to a defined set of cloud providers.
-
-Myonion provides a way to build and deploy onion ready applications, allowing developers to build and test web applications and easily share them with others, bundling the code and configuration in a lightweight, portable Docker container application that runs the same everywhere.
-
-The experience for developers will be similar to using other industry solutions, like the [Docker desktop app](https://www.docker.com/products/docker-desktop).
-
-Developers using myonion are provided with pre-defined and customizable application templates, with corresponding configuration and a test set, eliminating error-prone manual setup and known onion service configuration mistakes.
-
-The resulting application is therefore deployable via a set of endpoint management tools to known providers. Providing a way to deploy onion services at scale.
-
-# Resources
-
-- Myonion repo on github: https://github.com/hiromipaw/myonion
-
diff --git a/content/gsoc/ooni-explorer-findings/contents.lr b/content/gsoc/ooni-explorer-findings/contents.lr
deleted file mode 100644
index b04887e..0000000
--- a/content/gsoc/ooni-explorer-findings/contents.lr
+++ /dev/null
@@ -1,82 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: False
----
-completed: True
----
-url: https://gist.github.com/kronaemmanuel/ae1ebafa039a3361fb422462109ae035
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 4
----
-languages: React
----
-org: OONI
----
-mentors:
-Sarath
-Federico Ceratto
-Arturo Filastò
----
-difficulty: Medium
----
-title: OONI Explorer findings: Improvements related to social media sharing
----
-subtitle:
-
-OONI Explorer is an open data resource on internet censorship around the world.
-OONI Probe is the software used to collect network measurements which are then
-shown on OONI Explorer. This project is about making improvements to how
-findings from OONI Probe tests are displayed on OONI Explorer when shared on
-social media.
-
----
-body:
-
-# Background
-
-OONI Explorer is an open data resource on internet censorship around the world.
-OONI Probe is the software used to collect network measurements which are then
-shown on OONI Explorer. This project is about making improvements to how
-findings from OONI Probe tests are displayed on OONI Explorer when shared on
-social media.
-
-# Proposal
-
-Currently, when an OONI Probe user wants to share their network measurement findings from their mobile app, the only option they have is to take screenshots and to share them on social media.
-
-As part of this activity, the student is asked to improve how OONI measurements are displayed when they are shared on social media.
-
-This includes:
-* Setting the appropriate meta tags to measurement page headers: https://github.com/ooni/explorer/issues/202
-* Generating a screenshot preview to display on the various social media platforms
-* Validating that the measurements are displayed well
-* Improving the indexing of OONI Explorer by search engines: https://github.com/ooni/ooni.org/issues/328
-* Adding some Call to Action functionality to encourage users to install OONI Probe
-
-Moreover, the student is encouraged to explore other ways through which OONI
-Probe users may be interested in sharing findings (such as a measurement result
-set) and how these can be presented in OONI Explorer and embedded in social
-media.
-
-Other relevant github issues include:
-
-Add support for native sharing capability in OONI Probe
-https://github.com/ooni/probe/issues/1070
-
-Easier exploration of reports by a specific probe
-https://github.com/ooni/explorer/issues/344
-
-# Resources
-
-- OONI Explorer repo on github: https://github.com/ooni/explorer
-- OONI Explorer issues github: https://github.com/ooni/explorer/issues
diff --git a/content/gsoc/ooni-explorer-testing/contents.lr b/content/gsoc/ooni-explorer-testing/contents.lr
deleted file mode 100644
index 1345807..0000000
--- a/content/gsoc/ooni-explorer-testing/contents.lr
+++ /dev/null
@@ -1,53 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: True
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 4
----
-languages: React
----
-org: OONI
----
-mentors:
-Sarath
-Arturo Filastò
----
-difficulty: Medium
----
-title: OONI Explorer: Improvements to testing
----
-subtitle:
-
-OONI Explorer is an open data resource on internet censorship around the world. This project is about making improvements to the end to end tests of OONI Explorer.
----
-body:
-
-# Background
-
-OONI Explorer is an open data resource on internet censorship around the world. This project is about making improvements to the end to end tests of OONI Explorer.
-
-# Proposal
-
-Currently, we only have a very basic set of end-to-end tests inside of OONI Explorer, which have been developed using the Cypress end-to-end testing tool. See: https://github.com/ooni/explorer/tree/master/cypress
-
-As part of this project, the student will work together with the OONI team to define a list of actions and operations that we would like to automate and test. Based on this, they will write end-to-end integration tests using Cypress.
-
-Currently, OONI Explorer does not have any unit tests. The student is therefore encouraged to explore and look into adding unit testing to the Explorer components.
-
-Moreover, the student is encouraged to research other ways to improve the quality and testing coverage of the OONI Explorer application, such as visual testing tools like percy: https://percy.io/
-
-# Resources
-
-- OONI Explorer repo on github: https://github.com/ooni/explorer
-- OONI Explorer issues github: https://github.com/ooni/explorer/issues
-
diff --git a/content/gsoc/ooni-probe-desktop-custom-urls/contents.lr b/content/gsoc/ooni-probe-desktop-custom-urls/contents.lr
deleted file mode 100644
index 6b09396..0000000
--- a/content/gsoc/ooni-probe-desktop-custom-urls/contents.lr
+++ /dev/null
@@ -1,72 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: True
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 4
----
-languages: React
----
-org: OONI
----
-mentors:
-Sarath
-Arturo Filastò
----
-difficulty: Medium
----
-title: OONI Probe Desktop support for OONI Run and custom URLs
----
-subtitle:
-
-OONI Probe Desktop is the next generation electron desktop client for running
-OONI tests on windows, macOS and Linux. This project is about adding
-capabilities related to custom URL testing.
-
----
-body:
-
-# Background
-
-OONI Probe Desktop is the next generation electron desktop client for running
-OONI tests on windows, macOS and Linux. This project is about adding
-capabilities related to custom URL testing.
-
-# Proposal
-
-Currently the OONI Probe Desktop app does not support specifying a custom URL
-for testing.
-
-As part of this project, the student will add UI support for specifying a
-custom URL inside of the OONI Probe desktop app. See:
-https://github.com/ooni/probe/issues/936
-
-The student will also look into adding support for the handling of OONI Run
-links on desktop as well. This will involve creating a deep link handler on
-desktop to trigger OONI Run links in OONI Probe desktop too. See:
-https://github.com/ooni/probe/issues/1071
-
-The OONI Probe Desktop app is an electron based desktop app, and the source
-code is available here: https://github.com/ooni/probe-desktop
-
-Issues for OONI Probe Desktop are tracked here:
-https://github.com/ooni/probe/issues?q=is%3Aopen+is%3Aissue+label%3Aooni%2Fprobe-desktop
-
-Under the hood, the OONI Probe desktop app is controlling a golang-based
-command line interface, called probe-cli: https://github.com/ooni/probe-cli
-
-# Resources
-
-- OONI Probe Desktop repo on github: https://github.com/ooni/probe-desktop
-- OONI Probe CLI repo on github: https://github.com/ooni/probe-cli
-- OONI Probe Desktop issues on github: https://github.com/ooni/probe/issues?q=is%3Aopen+is%3Aissue+label%3Aooni%2Fprobe-desktop
-
diff --git a/content/gsoc/privacy-aware-geo-lookup/contents.lr b/content/gsoc/privacy-aware-geo-lookup/contents.lr
deleted file mode 100644
index e170747..0000000
--- a/content/gsoc/privacy-aware-geo-lookup/contents.lr
+++ /dev/null
@@ -1,56 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: True
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 6
----
-languages:
-Golang
-Java
-Android
----
-org: OONI
----
-mentors:
-Simone Basso
-Arturo Filastò
----
-difficulty: Medium
----
-title: Privacy aware geo lookup
----
-subtitle:
-
-The idea for this project is to research a way to do a GPS based location lookup which resolves the location of the user to a granularity which is useful for qualifying measurements, but that doesn’t compromise users safety and privacy.
-
----
-body:
-
-# Problem
-
-When looking at OONI Probe measurements we often face a challenge in properly understanding what country (or more granular location) they are telling us things about.
-
-Often times the location information (since it's based on geoip) is inaccurate, because the underlying GeoIP database we used was old.
-
-On the other hand we also have a responsibility to protect user privacy to the extent that it's possible and therefore we don't collect IPs or store location information that is more granular than country level.
-
-# Proposal
-*Prerequisites:* familiarity with Android development and aptitude for research
-
-The idea for this project is to research a way to do a GPS based location lookup which resolves the location of the user to a granularity which is useful for qualifying measurements, but that doesn’t compromise users safety and privacy.
-
-# Resources
-
-- OONI Probe engine repo on github: https://github.com/ooni/probe-engine
-
-For the original ticket and discussion, please see ticket [249](https://github.com/ooni/probe-engine/issues/249)
\ No newline at end of file
diff --git a/content/gsoc/privacy-friendly-web/contents.lr b/content/gsoc/privacy-friendly-web/contents.lr
deleted file mode 100644
index 6d8a8e1..0000000
--- a/content/gsoc/privacy-friendly-web/contents.lr
+++ /dev/null
@@ -1,59 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: False
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 7
----
-languages:
-javascript
-CSS
-HTML
-Python
----
-mentors:
-hiro
----
-difficulty: medium
----
-title: Privacy Friendly Web
----
-subtitle:
-
-The scope of this project is creating a open-source community-driven browsable list of patterns and release a css/js framework that web developers can extend and use in their work.
----
-body:
-
-# Problem
-
-Security concerned web users take conscious steps to limit the amount of data they share with the websites visited and third party services.
-
-There are a number of security enhancing tools available. Some come in the form of browser extensions and javascript blockers, others are full fledged web browsers designed with providing extra security to their users.
-
-One of these is the Tor Browser. The Tor Browser was designed to provide privacy while surfing the web and defend users against both network and local forensic adversaries. There are two main categories of requirements that have been considered: Security Requirements, and Privacy Requirements.
-
-Security Requirements are the minimum properties in order for a browser to be able to support Tor and similar privacy proxies safely. Privacy requirements are primarily concerned with reducing linkability: the ability for a user's activity on one site to be linked with their activity on another site without their knowledge or explicit consent.
-
-# Proposal
-
-Websites can work seamlessly with the Tor Browser and other privacy enhancing browsers and tools if they adopt a series of respectful and ethical patterns.
-
-The Tor Browser is in fact, based on Mozilla's Extended Support Release (ESR) Firefox branch. We have a series of patches against this browser to enhance privacy and security. Browser behavior is additionally augmented through the Torbutton extension, and we also change a number of Firefox preferences from their defaults.
-
-The Tor Project has developed over the years a set of web development guidelines that allow websites to work with security enhanced browsers without causing any or minimal functionality disruption to their users. These guidelines have been shaped in an internal styleguide that has been adopted across all torproject.org websites.
-
-We are now formalizing these web development patterns and some security concerns that need to be considered when developing websites for users surfing the web with security enhanced browsers and tools. The scope of this project is creating a open-source community-driven browsable list of patterns and release a css/js framework that web developers can extend and use in their work.
-
-# Resources
-
-- Tor Project [styleguide](https://styleguide.torproject.org/)
-- Styleguide repo on github: https://github.com/torproject/styleguide
diff --git a/content/gsoc/salmon-bridge-distribution/contents.lr b/content/gsoc/salmon-bridge-distribution/contents.lr
deleted file mode 100644
index bb33777..0000000
--- a/content/gsoc/salmon-bridge-distribution/contents.lr
+++ /dev/null
@@ -1,72 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: False
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 8
----
-languages:
-Python
----
-org: Tor
----
-mentors:
-cohosh
-ahf
----
-difficulty:
----
-title: Implementing Salmon as a bridge distribution mechanism
----
-subtitle:
-
-This project entails implementing Salmon, a bridge distribution mechanism that partitions and distributes bridges using reputation to give well-behaved users access to "better" bridges and add a penalty when their bridges get censored.
-
----
-body:
-
-# Problem
-
-Bridges are Tor relays that are not publicly listed and therefore allow access to the Tor network in places where access to the public Tor relays, and therefore access to the Tor network, is blocked. Many users rely on bridges, or anti-censorship proxies, to connect to the Tor network. However, when censors learn this information, the bridges quickly become blocked and can no longer be used. We need a way of distributing bridge information to users so that they are able to connect without these bridges being discovered by the censors.
-
-# Proposal
-
-Our goal is to distribute bridges to users in censored regions when they need them, while also limiting the amount of bridge information that is leaked to censors. This project entails implementing Salmon, a bridge distribution mechanism that partitions and distributes bridges using reputation to give well-behaved users access to "better" bridges and add a penalty when their bridges get censored.
-
-# Getting started
-
-1. Read the blog posts to get an introduction to the problem space.
-1. Play around with [bridgedb](https://bridges.torproject.org/) to request a bridge and try understand how it works.
-1. Checkout the existing [code](#Code-repos).
-1. Read the [papers](#academic-papers) listed under [Resources](#Resources).
-1. Join the [next anti-censorship team meeting](https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam#IRCmeetingsschedule) to discuss your findings and ask any questions.
-
-# Resources
-
-## Academic papers
-
-- Original Paper: [Salmon: Robust Proxy Distribution for Censorship Circumvention](https://petsymposium.org/2016/files/papers/Salmon__Robust_Proxy_Distribution_for_Censorship_Circumvention.pdf)
-- [Design of a blocking-resistant anonymity system](https://svn-archive.torproject.org/svn/projects/design-paper/blocking.html)
-- [Enemy At the Gateways: Censorship-Resilient Proxy Distribution Using Game Theory](https://people.cs.umass.edu/~amir/papers/TorGame.pdf)
-- [rBridge: User Reputation based Tor Bridge Distribution with Privacy Preservation](https://www-users.cs.umn.edu/~hoppernj/rbridge_ndss13.pdf)
-- [HYPHAE: Social Secret Sharing](https://patternsinthevoid.net/hyphae/hyphae.pdf)
-
-##Â Blog posts
-- [Strategies for getting more bridge addresses](https://blog.torproject.org/strategies-getting-more-bridge-addresses)
-- [Ten ways to discover Tor bridges](https://blog.torproject.org/research-problems-ten-ways-discover-tor-bridges)
-- [Five ways to test bridge reachability](https://blog.torproject.org/research-problem-five-ways-test-bridge-reachability)
-- [The Next Chapter in Anti-Censorship](https://blog.torproject.org/next-chapter-anti-censorship)
-
-## Code repos
-
-- Salmon Project on github: https://github.com/SalmonProject
-- BridgeDB Source code: https://gitweb.torproject.org/bridgedb.git
diff --git a/content/gsoc/snowflake-android-proxy/contents.lr b/content/gsoc/snowflake-android-proxy/contents.lr
deleted file mode 100644
index 0b188f6..0000000
--- a/content/gsoc/snowflake-android-proxy/contents.lr
+++ /dev/null
@@ -1,72 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: False
----
-completed: True
----
-url: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake-mobile
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 9
----
-languages:
-Android
----
-org: Tor
----
-mentors:
-cohosh
----
-difficulty:
----
-title: Snowflake proxy on Android
----
-subtitle:
-
-This project entails implementing a Snowflake proxy app that will run on Android and relay a user's Tor traffic to the Tor network in the background.
-
----
-body:
-
-# Background
-
-[Snowflake](https://snowflake.torproject.org/) is a circumvention system in which volunteers can run proxies to help users connect to the Tor network. Users make WebRTC connections to the proxies, who then relay this data to a Snowflake bridge and then on to the Tor network. The advantage of using WebRTC is that Snowflake proxies can frequently change IP address or operate behind a NAT. At the moment, we have implemented the Snowflake proxy code as a web extension or a web badge, but we have not yet implemented a proxy that will run smoothly on Android.
-
-# Proposal
-
-This project entails implementing a Snowflake proxy app that will run on Android and relay a user's Tor traffic to the Tor network in the background. This application does not use Tor itself, it will relay Tor traffic from censored users to the Snowflake bridge. It will do this by copying Tor traffic between a WebRTC connection to the user and a WebSocket connection to the Snowflake bridge.
-
-There is an implementation component as well as an exploration and testing component while we figure out how to achieve good performance from a background application without using too much of the volunteer proxy's data or resources. We'd like to build in the ability for multiple users to connect through
-a proxy, but we'll start with just one user at first. This project is experimental in the sense that we don't yet know how many resources it will take and whether the proxies will be reliable enough for clients to use.
-
-# Getting Started
-
-A good way to get started is to read the resources provided below and familiarize yourself with how Snowflake works. You can then:
-
-1. Take a look at the existing WebExtension proxy code, and
-2. Install the WebExtension to try it out for yourself: https://snowflake.torproject.org/
-
-Once you feel ready to get started on some tickets, you can search for webextension (proxy) based tickets on our bug tracking system by looking for the keyword ["webextension"](https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_revision&status=new&status=reopened&keywords=~webextension&component=%5ECircumvention%2FSnowflake&group=type&col=id&col=summary&col=component&col=status&col=type&col=priority&col=milestone&order=priority) in the Snowflake component.
-
-# Resources
-
-We already have the proxy implemented as a WebExtension in javascript. You can take a look at that implementation for a more detailed idea of what exactly we're trying to do:
-
-- https://gitweb.torproject.org/pluggable-transports/snowflake.git/tree/proxy
-
-Some other links that will be useful are:
-
-- the technical writeup: https://keroserene.net/snowflake/technical/
-- deployment details and open tickets: https://trac.torproject.org/projects/tor/wiki/doc/Snowflake
-
-- [Snowflake](https://snowflake.torproject.org/)
-- Snowflake repo: https://gitweb.torproject.org/pluggable-transports/snowflake.git/
\ No newline at end of file
diff --git a/content/gsoc/tor-keygen/contents.lr b/content/gsoc/tor-keygen/contents.lr
deleted file mode 100644
index 8b138bf..0000000
--- a/content/gsoc/tor-keygen/contents.lr
+++ /dev/null
@@ -1,49 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: False
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 12
----
-languages:
-C
-Python
-Golang
-Rust
----
-mentors:
-asn
-dgoulet
----
-difficulty: medium/hard
----
-title: tor-keygen
----
-subtitle:
-
-The scope of this project is to write an application that generates cryptographic keys for Tor relays, dirauths and onion services.
----
-body:
-
-# Problem
-
-
-# Proposal
-
-Prerequisites: Understanding of Tor protocol and tor codebase
-
-# Resources
-
-- https://trac.torproject.org/projects/tor/ticket/18098
-- https://trac.torproject.org/projects/tor/ticket/14389
-- https://github.com/torproject/tor/blob/e34d963c4453ceac7ff378ce0044d10461980c8e/src/app/main/main.c#L1282
-- Original tor-keygen repo on github: https://github.com/haxxpop/torkeygen
\ No newline at end of file
diff --git a/content/gsoc/tor-relay-ipv6-support/contents.lr b/content/gsoc/tor-relay-ipv6-support/contents.lr
deleted file mode 100644
index db89d66..0000000
--- a/content/gsoc/tor-relay-ipv6-support/contents.lr
+++ /dev/null
@@ -1,120 +0,0 @@
-_model: project
----
-_template: layout.html
----
-html: two-columns-page.html
----
-active: False
----
-completed: True
----
-section: GSoC
----
-section_id: gsoc
----
-color: primary
----
-key: 10
----
-languages:
-C
----
-mentors:
-teor
-ahf
-nickm
----
-difficulty: Medium
----
-title: Improve Tor Relay IPv6 Support
----
-subtitle:
-
-Tor helps people stay safe on the internet, by keeping their internet use secure and anonymous. More Tor clients are running on IPv6-only or dual-stack networks. But only 20% of Tor’s available relay bandwidth supports IPv6. We want to automate relay IPv6 address discovery and reachability checks, so that it is easier for relay operators to run IPv6 relays.
-
----
-body:
-
-The Tor Project will be improving tor relay IPv6 support in 2020.
-
-Students may choose to focus on:
- * designing and implementing tor relay IPv6 features,
- * tor relay IPv6 testing, or
- * diagnosing and fixing bugs in tor's IPv6 code.
-
-## Prerequisites
-
-* Network configuration skills
-* Basic understanding of IPv4 and IPv6
-
-Recommended:
-
-* Experience testing network software
-* Experience running Internet-connected servers
-
-## Programming skills needed:
-
-* C coding
-* Building Unix-based (Linux, *BSD, macOS) software
-
-Recommended:
-
-* Experience with Unix network programming
-* Python coding (for testing)
-* Access to a server with public IPv4 and IPv6 addresses (to run a test relay)
-
-## Getting Started
-
-1. Clone tor using [git](https://github.com/torproject/tor)
-2. Build tor from source
-3. Run the tor unit tests using "make check". Let us know if they fail, and we'll help fix them.
-4. Clone [chutney]( https://github.com/torproject/chutney) using git. Chutney is a tor integration test tool.
-5. Run the tor integration tests using "make test-network". Let us know if they fail, and we'll help fix them.
-6. Make sure you have a GitHub account, so you can submit pull requests to tor's [GitHub repository](https://github.com/torproject/tor)
-
-See our [Getting Started](https://gitweb.torproject.org/tor.git/tree/doc/HACKING/GettingStarted.md) document for more information.
-
-Once you have completed the above tasks, you may wish to move on to the following initial tasks for the project.
-
-### Initial Tasks
-
-* [Use Authority Addresses for Socket-Based Address Detection](https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt#n1397).
-* [Add IPv6 Support to is_local_addr()](https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt#n1099).
-* [Add a BandwidthStatistics option](https://gitweb.torproject.org/torspec.git/tree/proposals/313-relay-ipv6-stats.txt#n298).
-* [Close Existing Connections Before Testing Reachability](https://gitweb.torproject.org/torspec.git/tree/proposals/311-relay-ipv6-reachability.txt#n465).
-* [Add unit tests or chutney tests for IPv6Traffic](https://trac.torproject.org/projects/tor/ticket/31543).
-
-### Main Tasks
-
-* [Add IPv6 Support to AuthDirMaxServersPerAddr](https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt#n1125).
-* [Use Authenticated NETINFO Cells to Discover Relay IP Addresses](https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt#n785).
-* [Chutney tests for IPv6-only bridge clients](https://trac.torproject.org/projects/tor/ticket/20068).
-* [IPv6 Exits succeed on Travis Linux, but Travis Linux doesn't support IPv6](https://trac.torproject.org/projects/tor/ticket/30182).
-
-### Stretch Goals
-
-* [Close Existing Connections Before Testing Reachability](https://gitweb.torproject.org/torspec.git/tree/proposals/311-relay-ipv6-reachability.txt#n465).
-* [Use Add IPv6 DNS Support via the Libevent DNS API](https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt#n1189).
-* [Discovered Addresses as the Default OutboundBindAddress](https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt#n1256).
-* [Make chutney check for relay microdescriptors before verifying](https://trac.torproject.org/projects/tor/ticket/33428).
-* [chutney doesn't verify using IPv6 addresses](https://trac.torproject.org/projects/tor/ticket/17011).
-
-## Links/Resources
-
-### Technical Proposals
-
-Tor Relay IPv6 Reachability
-https://gitweb.torproject.org/torspec.git/tree/proposals/311-relay-ipv6-reachability.txt
-
-Tor Relay Automatic IPv6 Address Discovery
-https://gitweb.torproject.org/torspec.git/tree/proposals/312-relay-auto-ipv6-addr.txt
-
-### Relay Operator Guides
-
-Tor Relay Guide: IPv6
-https://trac.torproject.org/projects/tor/wiki/TorRelayGuide#IPv6
-
-### Roadmaps
-
-Tor IPv6 Roadmap
-https://trac.torproject.org/projects/tor/wiki/org/roadmaps/Tor/IPv6Features
diff --git a/content/localization/translation-problem/contents.lr b/content/localization/translation-problem/contents.lr
index 26ce65a..430aafd 100644
--- a/content/localization/translation-problem/contents.lr
+++ b/content/localization/translation-problem/contents.lr
@@ -19,7 +19,7 @@ body:
### Reporting an error with a translation
* If you are already a [Tor translator](../becoming-tor-translator), you can simply find the string and fix it in [transifex](https://www.transifex.com/otf/torproject/).
-* If you don't know how to find the string to fix, you can [open a ticket on our Bugtracker](https://support.torproject.org/misc/bug-or-feedback/), under the **Community/Translations** component.
- Before opening a ticket, see the currently [open tickets for Translations](https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=merge_ready&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Community%2FTranslations&order=priority) because maybe it is already reported.
+* If you don't know how to find the string to fix, you can [open a ticket on our Bugtracker](https://support.torproject.org/misc/bug-or-feedback/), under the **Community/Localization** repository.
+ Before opening a ticket, see the currently [open tickets for Translations](https://github.com/torproject/community/tree/master/content/localization) because maybe it is already reported.
* You can send an email to the [tor localization mailing list](https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-l10n).
* You can report such issues on [irc](https://support.torproject.org/get-in-touch/#irc-help), on the #tor-l10n channel on the oftc network (you may need to be registered to log in).
diff --git a/databags/training-resources.json b/databags/training-resources.json
index f1e8b10..ba7f3ea 100644
--- a/databags/training-resources.json
+++ b/databags/training-resources.json
@@ -4,9 +4,9 @@
"label" : "All About Tor",
"name" : "all-about-tor",
"filename" : "all-about-tor-full-pack",
- "formats" : ["odp","md"],
+ "formats" : ["odp","pdf"],
"description" : "Full set of slides for Tor Trainings",
- "date" : "2019"
+ "date" : "2021"
},
"todo sobre tor" :
@@ -27,5 +27,15 @@
"formats" : ["odp","pdf"],
"description" : "Learn about the Tor network and how to run a relay",
"date" : "2019"
+ },
+
+ "Private bridges workshop" :
+ {
+ "label" : "Running Tor bridges",
+ "name" : "private-bridges",
+ "filename" : "private-bridges-workshop",
+ "formats" : ["odp","pdf"],
+ "description" : "Learn how to run a private unlisted Tor bridge",
+ "date" : "2021"
}
}
More information about the tor-commits
mailing list