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

[community/staging] Add some tips for students on how to contribute
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 677d5451ef28fa5a46cb0641640f1c057f035522 Author: Pili Guerra <pili(a)piliguerra.com> Date: Mon Mar 2 17:38:45 2020 +0100 Add some tips for students on how to contribute --- content/gsoc/cloudflare-captcha-monitoring/contents.lr | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/cloudflare-captcha-monitoring/contents.lr index c311934..f511683 100644 --- a/content/gsoc/cloudflare-captcha-monitoring/contents.lr +++ b/content/gsoc/cloudflare-captcha-monitoring/contents.lr @@ -60,6 +60,14 @@ Then there are other interesting patterns to look for: - 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:

1 0

[community/staging] better order and change of link. also please check if your ticket exists before opening it :D
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 5c0fc54f59ba5d8d04871d4695ac8f06bd166c45 Author: emma peel <emma.peel(a)riseup.net> Date: Fri Jan 10 15:37:33 2020 +0100 better order and change of link. also please check if your ticket exists before opening it :D --- content/localization/translation-problem/contents.lr | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/localization/translation-problem/contents.lr b/content/localization/translation-problem/contents.lr index 242c109..26ce65a 100644 --- a/content/localization/translation-problem/contents.lr +++ b/content/localization/translation-problem/contents.lr @@ -20,5 +20,6 @@ body: * 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. -* You can report such issues on [irc](https://webchat.oftc.net/), on the #tor-l10n channel (you may need to be registered to log in). + Before opening a ticket, see the currently [open tickets for Translations](https://trac.torproject.org/projects/tor/query?status=accepte… 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).

1 0

[community/staging] Adding more details to the Salmon gsoc project
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit e0b892e569c4f5c5c905d6dc4c37683e4689087b Author: Pili Guerra <pili(a)piliguerra.com> Date: Fri Mar 20 16:01:15 2020 +0000 Adding more details to the Salmon gsoc project --- .../gsoc/salmon-bridge-distribution/contents.lr | 28 +++++++++++++++++++--- 1 file changed, 25 insertions(+), 3 deletions(-) diff --git a/content/gsoc/salmon-bridge-distribution/contents.lr b/content/gsoc/salmon-bridge-distribution/contents.lr index 8ec5614..fb9e7ab 100644 --- a/content/gsoc/salmon-bridge-distribution/contents.lr +++ b/content/gsoc/salmon-bridge-distribution/contents.lr @@ -15,6 +15,7 @@ color: primary key: 8 --- languages: +Python --- org: Tor --- @@ -41,8 +42,29 @@ Bridges are Tor relays that are not publicly listed and therefore allow access t 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/AntiCensor… to discuss your findings and ask any questions. + # Resources -- Original Paper: [Salmon: Robust Proxy Distribution for -Censorship Circumvention](https://petsymposium.org/2016/files/papers/Salmon__Robust_Pr… -- Salmon Project on github: https://github.com/SalmonProject \ No newline at end of file +## Academic papers + +- Original Paper: [Salmon: Robust Proxy Distribution for Censorship Circumvention](https://petsymposium.org/2016/files/papers/Salmon__Robust_Pr… +- [Design of a blocking-resistant anonymity system](https://svn-archive.torproject.org/svn/projects/design-paper/blocki… +- [Nymble: Blocking Misbehaving Users in Anonymizing Networks](https://www.freehaven.net/anonbib/#proximax11) + +## Blog posts +- [Strategies for getting more bridge addresses](https://blog.torproject.org/strategies-getting-more-bridge-addre… +- [Ten ways to discover Tor bridges](https://blog.torproject.org/research-problems-ten-ways-discover-to… +- [Five ways to test bridge reachability](https://blog.torproject.org/research-problem-five-ways-test-b… +- [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

1 0

[community/staging] Update Tor Weather details
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit fdf68d8adcc81d228e01d91218c7bc7d1b3c37bf Author: Pili Guerra <pili(a)piliguerra.com> Date: Mon Mar 2 17:17:02 2020 +0100 Update Tor Weather details --- content/gsoc/tor-weather/contents.lr | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/gsoc/tor-weather/contents.lr b/content/gsoc/tor-weather/contents.lr index 3023237..cc6b997 100644 --- a/content/gsoc/tor-weather/contents.lr +++ b/content/gsoc/tor-weather/contents.lr @@ -39,8 +39,8 @@ If a relay disappears today, it is unlikely that anyone will notice or even send The entire Tor network would benefit from a "Tor Weather" service to notify relay and bridge operators when the state of their relays has changed. This has a number of benefits, including: - increasing the likelihood that relay operators notice problems and actually mitigate them. -- showing relay operators that someone actually cares if their relays go down or become outdated or have another problems -- giving relay operators information about best-practices, e.g not running outdated versions, fixing their DNs, etc... +- showing relay operators that someone actually cares if their relays go down or become outdated or have other problems +- giving relay operators information about best-practices, e.g not running outdated versions, fixing their DNS, etc... Right now, there is very little direct feedback given to relay operators. This can mean that operators become discouraged and stop running relays. @@ -58,7 +58,7 @@ Once a basic email notification service is implemented, these are some ideas for - Email me when my relay runs an end-of-life version of tor - Email me when my relay runs an outdated tor version - Email me when my exit relay fails to resolve hostnames (DNS failure) -- Email me when my relay looses the stable/guard/exit flag +- Email me when my relay loses the stable/guard/exit flag - Email me when my MyFamily configuration is broken - Email me when you detect issues with my relay - Email me with suggestions for configuration improvements for my relay

1 0

[community/staging] Updating papers for salmon gsoc project
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit fb66b21ee1514ad7e74b33749edd360536ff54df Author: Pili Guerra <pili(a)piliguerra.com> Date: Fri Mar 20 16:32:04 2020 +0000 Updating papers for salmon gsoc project --- content/gsoc/salmon-bridge-distribution/contents.lr | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/content/gsoc/salmon-bridge-distribution/contents.lr b/content/gsoc/salmon-bridge-distribution/contents.lr index fb9e7ab..99a5bbf 100644 --- a/content/gsoc/salmon-bridge-distribution/contents.lr +++ b/content/gsoc/salmon-bridge-distribution/contents.lr @@ -56,7 +56,9 @@ Our goal is to distribute bridges to users in censored regions when they need th - Original Paper: [Salmon: Robust Proxy Distribution for Censorship Circumvention](https://petsymposium.org/2016/files/papers/Salmon__Robust_Pr… - [Design of a blocking-resistant anonymity system](https://svn-archive.torproject.org/svn/projects/design-paper/blocki… -- [Nymble: Blocking Misbehaving Users in Anonymizing Networks](https://www.freehaven.net/anonbib/#proximax11) +- [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-addre…

1 0

[community/staging] Adding Getting Started section for ipv6 project
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit d8ebc74f779e08f176fa7fd7180ec2600bc037ff Author: Pili Guerra <pili(a)piliguerra.com> Date: Thu Mar 5 12:25:14 2020 +0100 Adding Getting Started section for ipv6 project --- content/gsoc/tor-relay-ipv6-support/contents.lr | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/content/gsoc/tor-relay-ipv6-support/contents.lr b/content/gsoc/tor-relay-ipv6-support/contents.lr index fdc3f78..e94d0b7 100644 --- a/content/gsoc/tor-relay-ipv6-support/contents.lr +++ b/content/gsoc/tor-relay-ipv6-support/contents.lr @@ -61,6 +61,17 @@ Recommended: * 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/GettingStar… document for more information. + ## Links/Resources ### Technical Proposals

1 0

[community/staging] tor-relay-ipv6: Update GSoC Info
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 92e837fc290a7da71b4de30a3f90f4f61e541409 Author: teor <teor(a)torproject.org> Date: Wed Feb 5 22:35:00 2020 +1000 tor-relay-ipv6: Update GSoC Info --- content/gsoc/tor-relay-ipv6-support/contents.lr | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/gsoc/tor-relay-ipv6-support/contents.lr b/content/gsoc/tor-relay-ipv6-support/contents.lr index 86518a2..fdc3f78 100644 --- a/content/gsoc/tor-relay-ipv6-support/contents.lr +++ b/content/gsoc/tor-relay-ipv6-support/contents.lr @@ -19,7 +19,8 @@ C --- mentors: teor -ahf (to be confirmed) +ahf +nickm --- difficulty: Medium ---

1 0

[community/staging] Add tor-keygen to the list of projects
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 1de7797dc617c4bfe6317d6b6de50938c5017511 Author: Pili Guerra <pili(a)piliguerra.com> Date: Thu Feb 6 12:35:47 2020 +0100 Add tor-keygen to the list of projects --- content/gsoc/tor-keygen/contents.lr | 49 +++++++++++++++++++++++++++++++++++++ 1 file changed, 49 insertions(+) diff --git a/content/gsoc/tor-keygen/contents.lr b/content/gsoc/tor-keygen/contents.lr new file mode 100644 index 0000000..f32192f --- /dev/null +++ b/content/gsoc/tor-keygen/contents.lr @@ -0,0 +1,49 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +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/e34d963c4453ceac7ff378ce0044d1046198… +- Original tor-keygen repo on github: https://github.com/haxxpop/torkeygen \ No newline at end of file

1 0

[community/staging] Merge remote-tracking branch 'gus-github/patch-9'
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 64b63b36a1376e1e999e3ea753c2716fd13cfb30 Merge: 9a126f1 928c075 Author: emma peel <emma.peel(a)riseup.net> Date: Tue Mar 24 20:11:10 2020 +0100 Merge remote-tracking branch 'gus-github/patch-9' .../relay-operations/community-resources/eff-tor-legal-faq/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

1 0

[community/staging] Update the OONI related GSoC proposals
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 9a126f1fc3924b8f151d1ea37fc9e2db0717e1fe Author: Arturo Filastò <arturo(a)filasto.net> Date: Fri Mar 20 17:44:07 2020 +0100 Update the OONI related GSoC proposals --- .../gsoc/ooni-explorer-advanced-search/contents.lr | 61 ----------------- content/gsoc/ooni-explorer-findings/contents.lr | 78 ++++++++++++++++++++++ content/gsoc/ooni-explorer-testing/contents.lr | 53 +++++++++++++++ .../ooni-probe-desktop-custom-urls/contents.lr | 72 ++++++++++++++++++++ 4 files changed, 203 insertions(+), 61 deletions(-) diff --git a/content/gsoc/ooni-explorer-advanced-search/contents.lr b/content/gsoc/ooni-explorer-advanced-search/contents.lr deleted file mode 100644 index be381fd..0000000 --- a/content/gsoc/ooni-explorer-advanced-search/contents.lr +++ /dev/null @@ -1,61 +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: -Federico Ceratto -Arturo Filastò ---- -difficulty: Medium ---- -title: OONI Explorer Advanced Search ---- -subtitle: - -OONI Explorer is an open data resource on internet censorship around the world. This project is about enriching the OONI Explorer search functionality with the ability to visualize an analysis of metadata pertaining to filtered measurements. ---- -body: - -# Background - -OONI Explorer is an open data resource on internet censorship around the world. This project is about enriching the OONI Explorer search functionality with the ability to visualize an analysis of metadata pertaining to filtered measurements. - -# Proposal - -This project is about enriching the OONI Explorer search functionality with the ability to visualize an analysis of metadata pertaining to filtered measurements. - -This would involve adding the ability to filter on multiple axis: country, ASN, time range, anomaly, confirmed, failure, domain or input, citizenlab category code. - -The results would then be presented in an aggregate form, such as showing: - -- The total measurement count -- The anomaly vs total ratio -- Confirmed vs total -- Failure vs total - -These results could then be presented as a table or some other charts, such as a heatmat. - -Some other more detailed, drill-down views could also be implemented. - -A potential applicant should also have some prior design experience - -# Resources - -- OONI Explorer repo on github: https://github.com/ooni/explorer - diff --git a/content/gsoc/ooni-explorer-findings/contents.lr b/content/gsoc/ooni-explorer-findings/contents.lr new file mode 100644 index 0000000..270ccd4 --- /dev/null +++ b/content/gsoc/ooni-explorer-findings/contents.lr @@ -0,0 +1,78 @@ +_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 +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 new file mode 100644 index 0000000..1345807 --- /dev/null +++ b/content/gsoc/ooni-explorer-testing/contents.lr @@ -0,0 +1,53 @@ +_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 new file mode 100644 index 0000000..6b09396 --- /dev/null +++ b/content/gsoc/ooni-probe-desktop-custom-urls/contents.lr @@ -0,0 +1,72 @@ +_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%2F… +

1 0