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

[community/staging] Rewrote and reviewed Gettor distribution methods GSoC project
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit fdd0886a289e357d010cedb8d050564d66fafccf Author: Pili Guerra <pili(a)piliguerra.com> Date: Tue Feb 4 12:05:52 2020 +0100 Rewrote and reviewed Gettor distribution methods GSoC project --- content/gsoc/gettor-distribution/contents.lr | 25 ++++++++++++++++++++----- 1 file changed, 20 insertions(+), 5 deletions(-) diff --git a/content/gsoc/gettor-distribution/contents.lr b/content/gsoc/gettor-distribution/contents.lr index 19213f2..b39c92e 100644 --- a/content/gsoc/gettor-distribution/contents.lr +++ b/content/gsoc/gettor-distribution/contents.lr @@ -14,22 +14,37 @@ color: primary --- key: 2 --- -languages: python +languages: +python +ansible --- org: Tor --- -mentors: cohos, hiro +mentors: +cohosh +hiro --- difficulty: --- -title: Implement a new distribution methods for GetTor +title: Implement new distribution methods for GetTor --- subtitle: -This project would implement a feature to distribute Tor Browser downloads through Telegram or Facebook messenger. +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. GetTor 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 these binaries. This project would implement a feature to distribute Tor Browser downloads through Telegram or Facebook messenger. \ No newline at end of file +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

1 0

[community/staging] Add some more projects
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 3b8d7d9c8c9e97145972678666fe124b5b1e97d8 Author: Pili Guerra <pili(a)piliguerra.com> Date: Thu Jan 30 16:08:11 2020 +0100 Add some more projects --- content/gsoc/gettor-distribution/contents.lr | 35 +++++++++++++++ .../gsoc/ooni-explorer-advanced-search/contents.lr | 51 ++++++++++++++++++++++ content/gsoc/ooni-probe-experiments/contents.lr | 41 +++++++++++++++++ content/gsoc/privacy-aware-geo-lookup/contents.lr | 43 ++++++++++++++++++ .../gsoc/salmon-bridge-distribution/contents.lr | 37 ++++++++++++++++ content/gsoc/snowflake-android-proxy/contents.lr | 38 ++++++++++++++++ 6 files changed, 245 insertions(+) diff --git a/content/gsoc/gettor-distribution/contents.lr b/content/gsoc/gettor-distribution/contents.lr new file mode 100644 index 0000000..d0b7030 --- /dev/null +++ b/content/gsoc/gettor-distribution/contents.lr @@ -0,0 +1,35 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 1 +--- +languages: python +--- +org: Tor +--- +mentors: cohos, hiro +--- +difficulty: +--- +title: Implement a new distribution methods for GetTor +--- +subtitle: + +This project would implement a feature to distribute Tor Browser downloads through Telegram or Facebook messenger. + +--- +body: + + +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. GetTor 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 these binaries. This project would implement a feature to distribute Tor Browser downloads through Telegram or Facebook messenger. \ No newline at end of file diff --git a/content/gsoc/ooni-explorer-advanced-search/contents.lr b/content/gsoc/ooni-explorer-advanced-search/contents.lr new file mode 100644 index 0000000..bcb3cd4 --- /dev/null +++ b/content/gsoc/ooni-explorer-advanced-search/contents.lr @@ -0,0 +1,51 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 1 +--- +languages: React +--- +org: OONI +--- +mentors: Federico Ceratto, Arturo Filastò +--- +difficulty: Medium +--- +title: OONI Explorer Advanced Search +--- +subtitle: + +This project is about enriching the OONI Explorer search functionality with the ability to visualize an analysis of metadata pertaining to filtered measurements. + +--- +body: + +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 + +- *Prerequisites:* API call to be implemented by Federico +- *Links/Resource:* https://github.com/ooni/explorer + diff --git a/content/gsoc/ooni-probe-experiments/contents.lr b/content/gsoc/ooni-probe-experiments/contents.lr new file mode 100644 index 0000000..45dc216 --- /dev/null +++ b/content/gsoc/ooni-probe-experiments/contents.lr @@ -0,0 +1,41 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 1 +--- +languages: Golang +--- +org: OONI +--- +mentors: Simone Basso, Arturo Filastò +--- +difficulty: low-high +--- +title: OONI Probe network experiments +--- +subtitle: + +As part of this project you would be working on researching and developing new OONI Probe network experiments. + +--- +body: + +These experiments would be integrated inside of probe-engine and could eventually make their way into the OONI Probe desktop client. + +The GSoC project is only about researching and implementing a working test in probe-engine, not the UI and client integration of the test. + +For some inspiration on some ideas for new experiments, see: https://github.com/ooni/probe-engine/issues?q=is%3Aopen+is%3Aissue+label%3A… + +Prerequisites: Knowledge of network programming +Links/Resources: https://github.com/ooni/probe-engine \ No newline at end of file diff --git a/content/gsoc/privacy-aware-geo-lookup/contents.lr b/content/gsoc/privacy-aware-geo-lookup/contents.lr new file mode 100644 index 0000000..4fd5451 --- /dev/null +++ b/content/gsoc/privacy-aware-geo-lookup/contents.lr @@ -0,0 +1,43 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 1 +--- +languages: Golang, Java +--- +org: OONI +--- +mentors: Simone Basso, Arturo Filastò +--- +difficulty: Medium +--- +title: OONI Probe network experiments +--- +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: + +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. + +See: https://github.com/ooni/probe-engine/issues/249 + +Prerequisites: familiarity with Android development and aptitude for research +Links/Resource: https://github.com/ooni/probe-engine/issues/249 \ No newline at end of file diff --git a/content/gsoc/salmon-bridge-distribution/contents.lr b/content/gsoc/salmon-bridge-distribution/contents.lr new file mode 100644 index 0000000..4952c99 --- /dev/null +++ b/content/gsoc/salmon-bridge-distribution/contents.lr @@ -0,0 +1,37 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 1 +--- +languages: +--- +org: Tor +--- +mentors: +--- +difficulty: +--- +title: +--- +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: + +Short description: Many users rely on bridges, or anti-censorship proxies, to connect to the Tor network. We need a way of distributing bridge information to users so that they are able to connect. However, when censors learn this information the bridges quickly become blocked and can no longer be used. 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. + +For more information on Salmon, see the related paper and source code. + diff --git a/content/gsoc/snowflake-android-proxy/contents.lr b/content/gsoc/snowflake-android-proxy/contents.lr new file mode 100644 index 0000000..f99b301 --- /dev/null +++ b/content/gsoc/snowflake-android-proxy/contents.lr @@ -0,0 +1,38 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 1 +--- +languages: +--- +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: + +Snowflake 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. + +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. 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. + +Skills Needed: Development experience on Android. \ No newline at end of file

1 0

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

21 Mar '21

commit ecc8c373f8b995afba19dec227545f81f59df876 Author: Pili Guerra <pili(a)piliguerra.com> Date: Tue Feb 4 12:56:17 2020 +0100 Update Tor Weather description --- content/gsoc/tor-weather/contents.lr | 86 +++++++++++++++--------------------- 1 file changed, 36 insertions(+), 50 deletions(-) diff --git a/content/gsoc/tor-weather/contents.lr b/content/gsoc/tor-weather/contents.lr index 01bb416..3023237 100644 --- a/content/gsoc/tor-weather/contents.lr +++ b/content/gsoc/tor-weather/contents.lr @@ -15,9 +15,12 @@ color: primary key: 11 --- languages: -TBD +python +java --- -mentors: karsten +mentors: +GeKo +karsten --- difficulty: medium --- @@ -25,67 +28,50 @@ title: Tor Weather --- subtitle: -Tor Weather is the most efficient way to achieve and maintain a healthy Tor network on the long run. - +This project would implement a notification system for relay operators to alert them when the state of their relay has changed. This is the most efficient way to achieve and maintain a healthy Tor network on the long run. --- body: -Tor Weather was [discontinued on 2016-04-04](https://lists.torproject.org/pipermail/tor-relays/2016-April/00…, however "Tor Weather is still a good idea, it just needs somebody to implement it." - -How Tor Weather looked like: -https://web.archive.org/web/20141004055709/https://weather.torproject.org/subscribe/ - -## Motivation - -If a relay disappears today, it is unlikely that anyone will notice or even send an email to the operator unless it is a big one. - -Relay operators and the entire tor network would benefit from a Tor Weather service because it notifies relay operators when the state of their relays changed (and more). This will increase the likelihood that relay operators notice problems and actually mitigate the problem otherwise there is no "user feedback" since tor can cope with disappearing relays quite well. - -It also: -- shows the relay operator that someone actually cares if their relays go down or become outdated or have another problem -- gives the operator relay best-practices information. +# Problem -## Expected Effects +If a relay disappears today, it is unlikely that anyone will notice or even send an email to the operator. -If enough operators subscribe to such a service: -- relays might become more long lived / the churn rate might decrease -- the fraction of relays running outdated tor versions might decrease -- the fraction of exits with broken DNS might decrease +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: -It also has the benefit of being able to contact relay operators: -- completely automatically -- even if they choose to not set a public ContactInfo string in their torrc files. +- 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... -## Ideas for Notification Types +Right now, there is very little direct feedback given to relay operators. This can mean that operators become discouraged and stop running relays. -_(sorted by importance)_ +# Proposal -Support subscribing via single relay FP or MyFamily groups (should not need any subscription change if a relay gets added to the family). +This project would involve the implementation of an email notification service that relay operators can subscribe to and choose which notifications they want to receive about their relay. -- [ ] Email me when my node is down -_How long before we send a notification?_ -- [ ] email me when my relay is affected by a security vulnerability -- [ ] email me when my relay runs an end-of-life version of tor -- [ ] email me when my relay runs an outdated tor version (note: this should depend on the related onionoo bugs to avoid emailing alpha relay people) -- [ ] 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 MyFamily configuration is broken (meaning: non-mutual config detected or relay with same contactInfo but no MyFamily) -- [ ] email me when you detect issues with my relay -- [ ] email me with suggestions for configuration improvements for my relay (only once per improvement) -- [ ] email me when my relay is on the top [ ] 20 [ ] 50 [ ] 100 relays list -- [ ] email me with monthly/quarterly status information that includes information like what my position in the overall relay list is (sorted by CW), how much traffic my relay did during the last month and what fraction of the months time your relay was included in consensus as running (this shows information on how many % of the months' consensuses this relay has been included and running) -- [ ] aggregate emails for all my relays into a single digest email -- [ ] email me about new relay requirements -- [ ] email me about tor relay operator events +This project already existed and was known as "Tor Weather". It was unfortunately [discontinued](https://lists.torproject.org/pipermail/tor-relays/2016-April/… due to lack of maintenance and resources to keep the project alive. However, we think that this is still a great idea and the most efficient way to achieve and maintain a healthy Tor network on the long run. The resulting service should conform to our current [styleguide](https://styleguide.torproject.org/). +This notification service should support subscribing via single relay fingerprint or MyFamily groups. Additionally, it should not need any subscription change if a new relay gets added to the family. As this service would store email addresses of potential tor relay operators, they should be kept private and safeguarded. However, a passive observer can collect them by watching outbound email traffic if no TLS is used. As such, this service should suggest using a dedicated email address for this service. -*Task:* Write a specification describing the meaning of each checkbox +Once a basic email notification service is implemented, these are some ideas for potential notification types that could be implemented within it: +- Email me when my node is down - Here we should decide how long before we send a notification? +- Email me when my relay is affected by a security vulnerability +- 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 MyFamily configuration is broken +- Email me when you detect issues with my relay +- Email me with suggestions for configuration improvements for my relay +- Email me when my relay is on the top 20/50/100 relays list +- Email me with monthly/quarterly status information, e.g what is my position in the overall relay list, how much traffic did my relay do during the last month, etc... +- Email me about new relay requirements +- Email me about tor relay operator events -## Security and Privacy Implications +For each notification implemented, there should be a corresponding specification written to describe the meaning of each notification type. -The service stores email addresses of potential tor relay operators, they should be kept private and safeguarded, but a passive observer can collect them by watching outbound email traffic if no TLS is used. Suggest to use a dedicated email address for this service. +# Resources -## Additional Ideas +- What Tor Weather looked like: https://web.archive.org/web/20141004055709/https://weather.torproject.org/s… +- Tor Weather repo: https://gitweb.torproject.org/weather.git/ -- easy: integration into tor: show the URL pointing to the new Tor Weather service like the current link to the lifecycle blogpost when tor starts and detects to be a new relay -- Provide an uptimerobot-style status page for relay operators using onionoo data +For the original ticket and discussion, please see ticket [#26124](http://bugs.torproject.org/26124) \ No newline at end of file

1 0

[community/staging] more updates for l10n section.
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit e7672f4557448337624e6de90f36f3e3869b4972 Author: emma peel <emma.peel(a)riseup.net> Date: Wed Jan 15 19:13:01 2020 +0100 more updates for l10n section. closes: https://dip.torproject.org/torproject/web/community/merge_requests/27 --- content/localization/pick-a-project/contents.lr | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/content/localization/pick-a-project/contents.lr b/content/localization/pick-a-project/contents.lr index d5fe0af..c5b5860 100644 --- a/content/localization/pick-a-project/contents.lr +++ b/content/localization/pick-a-project/contents.lr @@ -15,12 +15,13 @@ key: 3 html: two-columns-page.html --- body: -We want our tools to be available and localized for anyone who wants to use them and appreciate your help. To find out where your knowledge may be most helpful, take a look at the translation progress for the Tor ecosystem of tools so far: +We want our tools to be available and localized for anyone who wants to use them, and we appreciate your help doing so. To find out where your knowledge may be most helpful, take a look at the translation progress for the Tor ecosystem of tools so far: <img class="col-lg-6" src="../../static/images/localization/stats.png"> -Although we would value your contribution to any of the projects above, the most critical are Tor Browser, the Tor Browser User Manual, and our Support Portal: +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…. -* The Support Portal 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… +* 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. +* 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] Fix style and order issues
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 0e0fbe73f9045e1eb862258a72ab27f1811d17b6 Author: Pili Guerra <pili(a)piliguerra.com> Date: Tue Feb 4 11:01:01 2020 +0100 Fix style and order issues --- content/gsoc/cloudflare-captcha-monitoring/contents.lr | 2 +- content/gsoc/gettor-distribution/contents.lr | 2 +- content/gsoc/onion-toolbox/contents.lr | 2 +- content/gsoc/ooni-explorer-advanced-search/contents.lr | 2 +- content/gsoc/ooni-probe-experiments/contents.lr | 2 +- content/gsoc/privacy-aware-geo-lookup/contents.lr | 6 ++++-- content/gsoc/privacy-friendly-web/contents.lr | 2 +- content/gsoc/salmon-bridge-distribution/contents.lr | 4 ++-- content/gsoc/snowflake-android-proxy/contents.lr | 3 ++- content/gsoc/tor-relay-ipv6-support/contents.lr | 2 +- content/gsoc/tor-weather/contents.lr | 2 +- 11 files changed, 16 insertions(+), 13 deletions(-) diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/cloudflare-captcha-monitoring/contents.lr index 2263ecc..c5daeb4 100644 --- a/content/gsoc/cloudflare-captcha-monitoring/contents.lr +++ b/content/gsoc/cloudflare-captcha-monitoring/contents.lr @@ -17,7 +17,7 @@ key: 1 languages: javascript --- -mentors: arma, gk +mentors: GeKo, arma --- difficulty: medium --- diff --git a/content/gsoc/gettor-distribution/contents.lr b/content/gsoc/gettor-distribution/contents.lr index d0b7030..19213f2 100644 --- a/content/gsoc/gettor-distribution/contents.lr +++ b/content/gsoc/gettor-distribution/contents.lr @@ -12,7 +12,7 @@ section_id: gsoc --- color: primary --- -key: 1 +key: 2 --- languages: python --- diff --git a/content/gsoc/onion-toolbox/contents.lr b/content/gsoc/onion-toolbox/contents.lr index 7968f31..ed8b5e4 100644 --- a/content/gsoc/onion-toolbox/contents.lr +++ b/content/gsoc/onion-toolbox/contents.lr @@ -12,7 +12,7 @@ section_id: gsoc --- color: primary --- -key: 1 +key: 3 --- languages: Python diff --git a/content/gsoc/ooni-explorer-advanced-search/contents.lr b/content/gsoc/ooni-explorer-advanced-search/contents.lr index bcb3cd4..99b9484 100644 --- a/content/gsoc/ooni-explorer-advanced-search/contents.lr +++ b/content/gsoc/ooni-explorer-advanced-search/contents.lr @@ -12,7 +12,7 @@ section_id: gsoc --- color: primary --- -key: 1 +key: 4 --- languages: React --- diff --git a/content/gsoc/ooni-probe-experiments/contents.lr b/content/gsoc/ooni-probe-experiments/contents.lr index 45dc216..8f18dcc 100644 --- a/content/gsoc/ooni-probe-experiments/contents.lr +++ b/content/gsoc/ooni-probe-experiments/contents.lr @@ -12,7 +12,7 @@ section_id: gsoc --- color: primary --- -key: 1 +key: 5 --- languages: Golang --- diff --git a/content/gsoc/privacy-aware-geo-lookup/contents.lr b/content/gsoc/privacy-aware-geo-lookup/contents.lr index 4fd5451..d0ba616 100644 --- a/content/gsoc/privacy-aware-geo-lookup/contents.lr +++ b/content/gsoc/privacy-aware-geo-lookup/contents.lr @@ -12,9 +12,11 @@ section_id: gsoc --- color: primary --- -key: 1 +key: 6 --- -languages: Golang, Java +languages: +Golang +Java --- org: OONI --- diff --git a/content/gsoc/privacy-friendly-web/contents.lr b/content/gsoc/privacy-friendly-web/contents.lr index fb32b0f..c56e209 100644 --- a/content/gsoc/privacy-friendly-web/contents.lr +++ b/content/gsoc/privacy-friendly-web/contents.lr @@ -12,7 +12,7 @@ section_id: gsoc --- color: primary --- -key: 1 +key: 7 --- languages: javascript diff --git a/content/gsoc/salmon-bridge-distribution/contents.lr b/content/gsoc/salmon-bridge-distribution/contents.lr index 4952c99..11855dc 100644 --- a/content/gsoc/salmon-bridge-distribution/contents.lr +++ b/content/gsoc/salmon-bridge-distribution/contents.lr @@ -12,7 +12,7 @@ section_id: gsoc --- color: primary --- -key: 1 +key: 8 --- languages: --- @@ -22,7 +22,7 @@ mentors: --- difficulty: --- -title: +title: Implementing Salmon as a bridge distribution mechanism --- subtitle: diff --git a/content/gsoc/snowflake-android-proxy/contents.lr b/content/gsoc/snowflake-android-proxy/contents.lr index f99b301..96f802b 100644 --- a/content/gsoc/snowflake-android-proxy/contents.lr +++ b/content/gsoc/snowflake-android-proxy/contents.lr @@ -12,9 +12,10 @@ section_id: gsoc --- color: primary --- -key: 1 +key: 9 --- languages: +Android --- org: Tor --- diff --git a/content/gsoc/tor-relay-ipv6-support/contents.lr b/content/gsoc/tor-relay-ipv6-support/contents.lr index 1300b87..4aff974 100644 --- a/content/gsoc/tor-relay-ipv6-support/contents.lr +++ b/content/gsoc/tor-relay-ipv6-support/contents.lr @@ -12,7 +12,7 @@ section_id: gsoc --- color: primary --- -key: 1 +key: 10 --- languages: C diff --git a/content/gsoc/tor-weather/contents.lr b/content/gsoc/tor-weather/contents.lr index 0c69dec..01bb416 100644 --- a/content/gsoc/tor-weather/contents.lr +++ b/content/gsoc/tor-weather/contents.lr @@ -12,7 +12,7 @@ section_id: gsoc --- color: primary --- -key: 2 +key: 11 --- languages: TBD

1 0

[community/staging] Fix template tags and homepage for gsoc
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit c7e7da927b6f8ff8e8b8359f230b0047da0421e0 Author: hiro <hiro(a)torproject.org> Date: Thu Jan 30 15:42:56 2020 +0100 Fix template tags and homepage for gsoc --- content/gsoc/cloudflare-captcha-monitoring/contents.lr | 3 ++- content/gsoc/contents.lr | 2 ++ content/gsoc/onion-toolbox/contents.lr | 5 ++++- content/gsoc/privacy-friendly-web/contents.lr | 6 +++++- content/gsoc/tor-relay-ipv6-support/contents.lr | 3 ++- content/gsoc/tor-weather/contents.lr | 3 ++- lego | 2 +- models/project.ini | 6 +++--- templates/home.html | 2 +- templates/macros/projects.html | 4 +++- templates/project.html | 4 ++-- 11 files changed, 27 insertions(+), 13 deletions(-) diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/cloudflare-captcha-monitoring/contents.lr index e5b71a5..2263ecc 100644 --- a/content/gsoc/cloudflare-captcha-monitoring/contents.lr +++ b/content/gsoc/cloudflare-captcha-monitoring/contents.lr @@ -14,7 +14,8 @@ color: primary --- key: 1 --- -languages: javascript +languages: +javascript --- mentors: arma, gk --- diff --git a/content/gsoc/contents.lr b/content/gsoc/contents.lr index 1e973f0..25d1562 100644 --- a/content/gsoc/contents.lr +++ b/content/gsoc/contents.lr @@ -1,5 +1,7 @@ _template: layout.html --- +_undiscoverable: true +--- section: GSoC --- section_id: gsoc diff --git a/content/gsoc/onion-toolbox/contents.lr b/content/gsoc/onion-toolbox/contents.lr index b9f50bc..7968f31 100644 --- a/content/gsoc/onion-toolbox/contents.lr +++ b/content/gsoc/onion-toolbox/contents.lr @@ -14,7 +14,10 @@ color: primary --- key: 1 --- -languages: Python, Docker, PythonQt5 +languages: +Python +Docker +PythonQt5 --- mentors: hiro, asn --- diff --git a/content/gsoc/privacy-friendly-web/contents.lr b/content/gsoc/privacy-friendly-web/contents.lr index be886de..fb32b0f 100644 --- a/content/gsoc/privacy-friendly-web/contents.lr +++ b/content/gsoc/privacy-friendly-web/contents.lr @@ -14,7 +14,11 @@ color: primary --- key: 1 --- -languages: javascript, CSS, HTML, Python +languages: +javascript +CSS +HTML +Python --- mentors: hiro --- diff --git a/content/gsoc/tor-relay-ipv6-support/contents.lr b/content/gsoc/tor-relay-ipv6-support/contents.lr index 3b0cd0f..1300b87 100644 --- a/content/gsoc/tor-relay-ipv6-support/contents.lr +++ b/content/gsoc/tor-relay-ipv6-support/contents.lr @@ -14,7 +14,8 @@ color: primary --- key: 1 --- -languages: C +languages: +C --- mentors: teor, ahf, dgoulet, catalyst --- diff --git a/content/gsoc/tor-weather/contents.lr b/content/gsoc/tor-weather/contents.lr index 95aa94a..0c69dec 100644 --- a/content/gsoc/tor-weather/contents.lr +++ b/content/gsoc/tor-weather/contents.lr @@ -14,7 +14,8 @@ color: primary --- key: 2 --- -languages: TBD +languages: +TBD --- mentors: karsten --- diff --git a/lego b/lego index f0ea955..e9dd081 160000 --- a/lego +++ b/lego @@ -1 +1 @@ -Subproject commit f0ea955c50f147813fd7735d226e7f4689e94523 +Subproject commit e9dd081027132aa21f6abd74be708323ff3b9180 diff --git a/models/project.ini b/models/project.ini index 2ee985e..17c3260 100644 --- a/models/project.ini +++ b/models/project.ini @@ -15,7 +15,7 @@ label = Active type = boolean [fields.subtitle] -label = Summary +label = Subtitle type = markdown [fields.color] @@ -23,7 +23,7 @@ label = Color type = string [fields.body] -label = Description +label = body type = markdown [fields.mentors] @@ -32,7 +32,7 @@ type = string [fields.languages] label = Languages -type = string +type = strings [fields.mentors] label = Mentors diff --git a/templates/home.html b/templates/home.html index 8b6f12f..08d04c9 100644 --- a/templates/home.html +++ b/templates/home.html @@ -7,7 +7,7 @@ <section> <div class="container"> <div class="row"> - {% for child in this.children|sort(attribute='key') %} + {% for child in site.query('/').filter(F.section_id != 'gsoc')|sort(attribute='key') %} <div class="col-sm-6 col-md-4 col-sm-12 col-xl-4 py-4"> <div class="card h-100 p-2"> <div class="card-body"> diff --git a/templates/macros/projects.html b/templates/macros/projects.html index 8f26811..d4da228 100644 --- a/templates/macros/projects.html +++ b/templates/macros/projects.html @@ -4,7 +4,9 @@ <h5 class="mb-0"> <a href="{{ item.path|url }}">{{ item.title }}</a> </h5> - <span class="badge badge-primary">{{ item.languages }}</span> + {% for lang in item.languages %} + <span class="badge badge-primary">{{ lang }}</span> + {% endfor %} </div> <div> <div class="card-body"> diff --git a/templates/project.html b/templates/project.html index 1aaed71..f9c5623 100644 --- a/templates/project.html +++ b/templates/project.html @@ -17,13 +17,13 @@ <div class="container py-3 mt-5"> <h4>Project Summary:</h4> <p> - {{ this.summary }} + {{ this.subtitle }} </p> </div> <div class="container py-3"> <h4>Project Description:</h4> <p> - {{ this.description }} + {{ this.body }} </p> </div> <div class="container py-3">

1 0

[community/staging] Rewrote and reviewed cloudflare captcha monitoring project
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit fdb8ba63730ccbf9c1debfbae46f78030d11b7f8 Author: Pili Guerra <pili(a)piliguerra.com> Date: Tue Feb 4 11:29:13 2020 +0100 Rewrote and reviewed cloudflare captcha monitoring project --- .../gsoc/cloudflare-captcha-monitoring/contents.lr | 41 +++++++++++++++------- 1 file changed, 29 insertions(+), 12 deletions(-) diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/cloudflare-captcha-monitoring/contents.lr index c5daeb4..332ca2a 100644 --- a/content/gsoc/cloudflare-captcha-monitoring/contents.lr +++ b/content/gsoc/cloudflare-captcha-monitoring/contents.lr @@ -25,26 +25,43 @@ title: Cloudflare Captcha Monitoring --- subtitle: -We should track the rate that cloudflare gives captchas to Tor users over time. +This project should implement a mechanism to track the rate that Cloudflare fronted webpages return captchas to Tor users over time. --- body: -My suggested way of doing that tracking is to sign up a very simple static webpage to be fronted by cloudflare, and then fetch it via Tor over time, and record and graph the rates of getting a captcha vs getting the real page. +# Problem -The reason for the "simple static page" is to make it really easy to distinguish whether we're getting hit with a captcha. The "distinguishing one dynamic web page from another" challenge makes exitmap tricky in the general case, but we can remove that variable here. +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. -One catch is that Cloudflare currently gives alt-svc headers in response to fetches from Tor addresses. So that means we need a web client that can follow alt-srv headers -- maybe we need a full Selenium like client? +# Proposal -Once we get the infrastructure set up, we would be smart to run a second one which is just wget or curl or lynx or something, i.e. which doesn't behave like Tor Browser, in order to be able to track the difference between how Cloudflare responds to Tor Browser vs other browsers. +For this project we would like to track in practice how often Cloudflare fronted webpages return captchas to Tor clients. -I imagine that Cloudflare should be internally tracking how they're handling Tor requests, but having a public tracker (a) gives the data to everybody, and (b) helps Cloudflare have a second opinion in case their internal data diverges from the public version. +Our proposed approach consists of: -The Berkeley ICSI group did research that included this sort of check: -https://www.freehaven.net/anonbib/#differential-ndss2016 -https://www.freehaven.net/anonbib/#exit-blocking2017 -but what I have in mind here is essentially a simpler subset of this research, skipping the complicated part of "how do you tell what kind of response you got" and with an emphasis on automation and consistency. +1. Setting up a very simple static webpage to be fronted by Cloudflare +2. Write an application which small 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: one is the fraction of exit relays that are getting hit with captchas, and the other is the chance that a Tor client, choosing an exit relay in the normal weighted faction, will get hit by a captcha. +There are two interesting metrics to track over time: -Then there are other interesting patterns to look for, e.g. "are certain IP addresses punished consistently and others never punished, or is whether you get a captcha much more probabilistic and transient?" And does that pattern change 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? + +# 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

1 0

[community/staging] Update GSoC CF project details
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit ae31484c9b429b1f8b06c1869a6417a99b67f596 Author: Pili Guerra <pili(a)piliguerra.com> Date: Tue Feb 4 12:02:58 2020 +0100 Update GSoC CF project details --- .../gsoc/cloudflare-captcha-monitoring/contents.lr | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-) diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/cloudflare-captcha-monitoring/contents.lr index 332ca2a..dbdc7e4 100644 --- a/content/gsoc/cloudflare-captcha-monitoring/contents.lr +++ b/content/gsoc/cloudflare-captcha-monitoring/contents.lr @@ -15,46 +15,47 @@ color: primary key: 1 --- languages: +python javascript --- mentors: GeKo, arma --- difficulty: medium --- -title: Cloudflare Captcha Monitoring +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. +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. +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. +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 an application which small 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 +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. +- 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? +- Is whether you get a CAPTCHA much more probabilistic and transient? - Does that pattern change over time? # Resources

1 0

[community/staging] Add email address for discussing new GSoC projects
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 58249a90844f59ce85e50595d883d0a6193ff91c Author: Pili Guerra <pili(a)piliguerra.com> Date: Wed Feb 5 10:46:05 2020 +0100 Add email address for discussing new GSoC projects --- content/gsoc/contents.lr | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/gsoc/contents.lr b/content/gsoc/contents.lr index a74dc57..e56ab2b 100644 --- a/content/gsoc/contents.lr +++ b/content/gsoc/contents.lr @@ -20,4 +20,4 @@ title: Project Ideas --- body: -You may find some of these projects to be good ideas for Google Summer of Code. We have labelled each idea with which of our core developers would be good mentors. If one or more of these ideas looks promising to you, please contact us to discuss your plans rather than sending blind applications. +You may find some of these projects to be good ideas for Google Summer of Code. We have labelled each idea with which of our core developers would be good mentors. If one or more of these ideas looks promising to you, please [contact us](mailto:gso+c@torproject.org) to discuss your plans rather than sending blind applications.

1 0

[community/staging] Update content for OONI GSoC projects
by hiro＠torproject.org 21 Mar '21

21 Mar '21

commit 36511588e98db38b9bdc0030e4ea9b4ed5358fdc Author: Pili Guerra <pili(a)piliguerra.com> Date: Wed Feb 5 13:04:39 2020 +0100 Update content for OONI GSoC projects --- content/gsoc/ooni-probe-experiments/contents.lr | 14 +++++++++++++- content/gsoc/privacy-aware-geo-lookup/contents.lr | 17 +++++++++++++---- 2 files changed, 26 insertions(+), 5 deletions(-) diff --git a/content/gsoc/ooni-probe-experiments/contents.lr b/content/gsoc/ooni-probe-experiments/contents.lr index 4d5d2f7..1eb568e 100644 --- a/content/gsoc/ooni-probe-experiments/contents.lr +++ b/content/gsoc/ooni-probe-experiments/contents.lr @@ -33,7 +33,19 @@ OONI Probe is a free software project that aims to uncover internet censorship a --- body: -# Problem +# Background + +The Open Observatory of Network Interference (OONI) is a free software project which aims to empower decentralized efforts in increasing transparency of internet censorship around the world. + +We develop free and open source software, called OONI Probe, that users can run to measure: + +- Blocking of websites; +- Blocking of instant messaging apps (WhatsApp, Facebook Messenger and Telegram); +- Blocking of censorship circumvention tools (such as Tor); +- Presence of systems (middleboxes) in your network that might be responsible for censorship and/or surveillance; +- Speed and performance of your network. + +By running OONI Probe, users can collect data that can potentially serve as evidence of internet censorship since it shows how, when, where, and by whom it is implemented. # Proposal diff --git a/content/gsoc/privacy-aware-geo-lookup/contents.lr b/content/gsoc/privacy-aware-geo-lookup/contents.lr index 1a58eb2..e170747 100644 --- a/content/gsoc/privacy-aware-geo-lookup/contents.lr +++ b/content/gsoc/privacy-aware-geo-lookup/contents.lr @@ -17,6 +17,7 @@ key: 6 languages: Golang Java +Android --- org: OONI --- @@ -26,7 +27,7 @@ Arturo Filastò --- difficulty: Medium --- -title: OONI Probe network experiments +title: Privacy aware geo lookup --- subtitle: @@ -35,13 +36,21 @@ The idea for this project is to research a way to do a GPS based location lookup --- 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. -See: https://github.com/ooni/probe-engine/issues/249 +# 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 -Prerequisites: familiarity with Android development and aptitude for research -Links/Resource: https://github.com/ooni/probe-engine/issues/249 \ No newline at end of file +For the original ticket and discussion, please see ticket [249](https://github.com/ooni/probe-engine/issues/249) \ No newline at end of file

1 0