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

[community/slideshow] Remove old projects so they don't appear in sidenav
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 0e16d7dcba183cd0a3d3c04cc1b66094a28be434 Author: Pili Guerra <pili(a)piliguerra.com> Date: Tue Mar 9 09:26:20 2021 +0100 Remove old projects so they don't appear in sidenav --- content/gsoc/{ => archive}/cloudflare-captcha-monitoring/contents.lr | 0 content/gsoc/{ => archive}/gettor-distribution/contents.lr | 0 content/gsoc/{ => archive}/onion-toolbox/contents.lr | 0 content/gsoc/{ => archive}/ooni-explorer-findings/contents.lr | 0 content/gsoc/{ => archive}/ooni-explorer-testing/contents.lr | 0 content/gsoc/{ => archive}/ooni-probe-desktop-custom-urls/contents.lr | 0 content/gsoc/{ => archive}/privacy-aware-geo-lookup/contents.lr | 0 content/gsoc/{ => archive}/privacy-friendly-web/contents.lr | 0 content/gsoc/{ => archive}/salmon-bridge-distribution/contents.lr | 0 content/gsoc/{ => archive}/snowflake-android-proxy/contents.lr | 0 content/gsoc/{ => archive}/tor-keygen/contents.lr | 0 content/gsoc/{ => archive}/tor-relay-ipv6-support/contents.lr | 0 12 files changed, 0 insertions(+), 0 deletions(-) diff --git a/content/gsoc/cloudflare-captcha-monitoring/contents.lr b/content/gsoc/archive/cloudflare-captcha-monitoring/contents.lr similarity index 100% rename from content/gsoc/cloudflare-captcha-monitoring/contents.lr rename to content/gsoc/archive/cloudflare-captcha-monitoring/contents.lr diff --git a/content/gsoc/gettor-distribution/contents.lr b/content/gsoc/archive/gettor-distribution/contents.lr similarity index 100% rename from content/gsoc/gettor-distribution/contents.lr rename to content/gsoc/archive/gettor-distribution/contents.lr diff --git a/content/gsoc/onion-toolbox/contents.lr b/content/gsoc/archive/onion-toolbox/contents.lr similarity index 100% rename from content/gsoc/onion-toolbox/contents.lr rename to content/gsoc/archive/onion-toolbox/contents.lr diff --git a/content/gsoc/ooni-explorer-findings/contents.lr b/content/gsoc/archive/ooni-explorer-findings/contents.lr similarity index 100% rename from content/gsoc/ooni-explorer-findings/contents.lr rename to content/gsoc/archive/ooni-explorer-findings/contents.lr diff --git a/content/gsoc/ooni-explorer-testing/contents.lr b/content/gsoc/archive/ooni-explorer-testing/contents.lr similarity index 100% rename from content/gsoc/ooni-explorer-testing/contents.lr rename to content/gsoc/archive/ooni-explorer-testing/contents.lr diff --git a/content/gsoc/ooni-probe-desktop-custom-urls/contents.lr b/content/gsoc/archive/ooni-probe-desktop-custom-urls/contents.lr similarity index 100% rename from content/gsoc/ooni-probe-desktop-custom-urls/contents.lr rename to content/gsoc/archive/ooni-probe-desktop-custom-urls/contents.lr diff --git a/content/gsoc/privacy-aware-geo-lookup/contents.lr b/content/gsoc/archive/privacy-aware-geo-lookup/contents.lr similarity index 100% rename from content/gsoc/privacy-aware-geo-lookup/contents.lr rename to content/gsoc/archive/privacy-aware-geo-lookup/contents.lr diff --git a/content/gsoc/privacy-friendly-web/contents.lr b/content/gsoc/archive/privacy-friendly-web/contents.lr similarity index 100% rename from content/gsoc/privacy-friendly-web/contents.lr rename to content/gsoc/archive/privacy-friendly-web/contents.lr diff --git a/content/gsoc/salmon-bridge-distribution/contents.lr b/content/gsoc/archive/salmon-bridge-distribution/contents.lr similarity index 100% rename from content/gsoc/salmon-bridge-distribution/contents.lr rename to content/gsoc/archive/salmon-bridge-distribution/contents.lr diff --git a/content/gsoc/snowflake-android-proxy/contents.lr b/content/gsoc/archive/snowflake-android-proxy/contents.lr similarity index 100% rename from content/gsoc/snowflake-android-proxy/contents.lr rename to content/gsoc/archive/snowflake-android-proxy/contents.lr diff --git a/content/gsoc/tor-keygen/contents.lr b/content/gsoc/archive/tor-keygen/contents.lr similarity index 100% rename from content/gsoc/tor-keygen/contents.lr rename to content/gsoc/archive/tor-keygen/contents.lr diff --git a/content/gsoc/tor-relay-ipv6-support/contents.lr b/content/gsoc/archive/tor-relay-ipv6-support/contents.lr similarity index 100% rename from content/gsoc/tor-relay-ipv6-support/contents.lr rename to content/gsoc/archive/tor-relay-ipv6-support/contents.lr

1 0

[community/slideshow] better lines for localization.
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 8c859d5bd156eaa98fb7deb0b786e17167f7860f Author: emma peel <emma.peel(a)riseup.net> Date: Fri Mar 5 09:12:04 2021 +0100 better lines for localization. --- .../tor-dmca-response/contents.lr | 23 +++++++++++++++++----- .../tor-abuse-templates/contents.lr | 9 +++------ .../technical-setup/bridge/docker/contents.lr | 16 ++++----------- 3 files changed, 25 insertions(+), 23 deletions(-) diff --git a/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr b/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr index 847ce19..f782b29 100644 --- a/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr +++ b/content/relay-operations/community-resources/eff-tor-legal-faq/tor-dmca-response/contents.lr @@ -30,15 +30,28 @@ Dear [ISP]: Thank you for forwarding me the notice you received from [copyright claimant] regarding [content]. I would like to assure you that I am not hosting the claimed infringing materials, and furthermore, the Digital Millennium Copyright Act's ("DMCA") safe harbors likely protect you from liability arising from this complaint. The notice is likely based upon misunderstandings about the law and about some of the software I run. -As you know, the DMCA creates four "safe harbors" for service providers to protect them from copyright liability for the acts of their users, when the ISPs fulfill certain requirements. (17 U.S.C. 512) The DMCA's requirements vary depending on the ISP's role. You may be familiar with the "notice and takedown" provisions of section 512(c) of the DMCA; however, those do not apply when an ISP merely acts as a conduit. Instead, the "conduit" safe harbor of section 512(a) of the DMCA has different and less burdensome eligibility requirements, as the D.C. Circuit Court of Appeals held in RIAA v. Verizon (see https://scholar.google.com/scholar_case?case=15815830240179540527) and the Eighth Circuit Court of Appeals confirmed in RIAA v. Charter (see https://scholar.google.com/scholar_case?case=11547531128234336420) +As you know, the DMCA creates four "safe harbors" for service providers to protect them from copyright liability for the acts of their users, when the ISPs fulfill certain requirements. (17 U.S.C. 512) +The DMCA's requirements vary depending on the ISP's role. You may be familiar with the "notice and takedown" provisions of section 512(c) of the DMCA; however, those do not apply when an ISP merely acts as a conduit. +Instead, the "conduit" safe harbor of section 512(a) of the DMCA has different and less burdensome eligibility requirements, as the D.C. Circuit Court of Appeals held in RIAA v. Verizon (see https://scholar.google.com/scholar_case?case=15815830240179540527) and the Eighth Circuit Court of Appeals confirmed in RIAA v. Charter (see https://scholar.google.com/scholar_case?case=11547531128234336420) -Under DMCA 512(a), service providers like you are typically protected from damages for copyright infringement claims if you also maintain "a policy that provides for termination in appropriate circumstances of subscribers and account holders of the service provider's system or network who are repeat infringers." If you have and implement such a policy, and you otherwise qualify for the safe harbor, you should be free from fear of copyright damages. +Under DMCA 512(a), service providers like you are typically protected from damages for copyright infringement claims if you also maintain "a policy that provides for termination in appropriate circumstances of subscribers and account holders of the service provider's system or network who are repeat infringers." +If you have and implement such a policy, and you otherwise qualify for the safe harbor, you should be free from fear of copyright damages. -The copyright notice you received was likely triggered by a program I run called Tor. Tor is network software that helps users to enhance their privacy, security, and safety online. It does not host any content. Rather, it is part of a network of nodes on the Internet that simply pass packets among themselves before sending them to their destinations, just as any Internet intermediary does. The difference is that Tor tunnels the connections such that no hop can learn both the source and destination of the packets, giving users protection from nefarious snooping on network traffic. The result is that, unlike most other Internet traffic, the final IP address that the recipient receives is not the IP address of the sender. Tor protects users against hazards such as harassment, spam, and identity theft. Initial development of Tor, including deployment of a public-use Tor network, was a project of the U.S. Naval Research Laboratory, with funding from ONR and DARPA. (For more on Tor, see https://www.torproject.org/.) I hope, as an organization committed to protecting the privacy of its customers, you'll agree that this is a valuable technology. +The copyright notice you received was likely triggered by a program I run called Tor. Tor is network software that helps users to enhance their privacy, security, and safety online. +It does not host any content. Rather, it is part of a network of nodes on the Internet that simply pass packets among themselves before sending them to their destinations, just as any Internet intermediary does. +The difference is that Tor tunnels the connections such that no hop can learn both the source and destination of the packets, giving users protection from nefarious snooping on network traffic. +The result is that, unlike most other Internet traffic, the final IP address that the recipient receives is not the IP address of the sender. +Tor protects users against hazards such as harassment, spam, and identity theft. Initial development of Tor, including deployment of a public-use Tor network, was a project of the U.S. Naval Research Laboratory, with funding from ONR and DARPA. (For more on Tor, see https://www.torproject.org/.) +I hope, as an organization committed to protecting the privacy of its customers, you'll agree that this is a valuable technology. -While the Tor node that I run may appear to be the source of material that is alleged to be copyright-infringing, I do not host that material. I do not select the material transmitted through the Tor node that I run, and I have no practical means of either identifying the source of such material or preventing its transmission. I do nothing to encourage or promote the use of the Tor network for copyright infringement. For these reasons, I am not an infringer of copyright in any materials that are transmitted through the Tor node that I run, either directly or under a theory of contributory or vicarious liability. Therefore, you should continue to be protected under the DMCA 512(a) safe harbor without taking any further action. +While the Tor node that I run may appear to be the source of material that is alleged to be copyright-infringing, I do not host that material. +I do not select the material transmitted through the Tor node that I run, and I have no practical means of either identifying the source of such material or preventing its transmission. +I do nothing to encourage or promote the use of the Tor network for copyright infringement. +For these reasons, I am not an infringer of copyright in any materials that are transmitted through the Tor node that I run, either directly or under a theory of contributory or vicarious liability. +Therefore, you should continue to be protected under the DMCA 512(a) safe harbor without taking any further action. -Thank you for working with me on this matter. As a loyal subscriber, I appreciate your notifying me of this issue and hope that the protections of DMCA 512 put any concerns you may have to rest. If not, please contact me with any further questions. +Thank you for working with me on this matter. As a loyal subscriber, I appreciate your notifying me of this issue and hope that the protections of DMCA 512 put any concerns you may have to rest. +If not, please contact me with any further questions. Very truly yours, Your customer, [User] diff --git a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr index 1cd12f9..3d2f00c 100644 --- a/content/relay-operations/community-resources/tor-abuse-templates/contents.lr +++ b/content/relay-operations/community-resources/tor-abuse-templates/contents.lr @@ -92,8 +92,7 @@ We're sorry your site is experiencing this heavy load from Tor. However, it is possible that your rate limiting alarms simply experienced a false positive due to the amount of traffic that flows through the router. We provide service to almost a gigabit of traffic per second, 98% of which is web traffic. -If the attack is real and ongoing, however, the Tor project provides an automated DNSRBL for you to query to block login attempts coming -from Tor nodes: https://www.torproject.org/projects/tordnsel.html.en +If the attack is real and ongoing, however, the Tor project provides an automated DNSRBL for you to query to block login attempts coming from Tor nodes: https://www.torproject.org/projects/tordnsel.html.en It is also possible to download a list of all Tor exit IPs that will connect to your server port: https://check.torproject.org/cgi-bin/TorBulkExitList.py?ip=YOUR_IP&port=80 @@ -175,11 +174,9 @@ Additionally, the Tor project provides an automated DNSRBL for you to query to f It also provides a Bulk Exit List service for retrieving the entire list: https://check.torproject.org/cgi-bin/TorBulkExitList.py -You can use this list to help you take a closer look at Tor orders, or to hold them temporarily for additional verification, without losing -legitimate customers. +You can use this list to help you take a closer look at Tor orders, or to hold them temporarily for additional verification, without losing legitimate customers. -In fact, in my experience, the fraud processing teams contracted by many ISPs simply mark all requests from Tor nodes as fraud using that -very list. +In fact, in my experience, the fraud processing teams contracted by many ISPs simply mark all requests from Tor nodes as fraud using that very list. So it is even possible this is a legitimate order, but was flagged as fraud solely based on IP, especially if you contract out fraud detection to a third party. ``` diff --git a/content/relay-operations/technical-setup/bridge/docker/contents.lr b/content/relay-operations/technical-setup/bridge/docker/contents.lr index eb449a8..00e26a1 100644 --- a/content/relay-operations/technical-setup/bridge/docker/contents.lr +++ b/content/relay-operations/technical-setup/bridge/docker/contents.lr @@ -9,11 +9,7 @@ body: ### 1. Deploy a container We provide a docker-compose file that helps you deploy the container. -First, -[download docker-compose.yml](https://dip.torproject.org/torproject/anti-censorship/d…, -and then write your bridge configuration to a new file, `.env`, which is in the -same directory as `docker-compose.yml`. Here's a -template: +First, [download docker-compose.yml](https://dip.torproject.org/torproject/anti-censorship/d…, and then write your bridge configuration to a new file, `.env`, which is in the same directory as `docker-compose.yml`. Here's a template: ``` # Your bridge's Tor port. @@ -24,18 +20,14 @@ PT_PORT=Y EMAIL=Z ``` -Replace `X` with your desired OR port, `Y` with your obfs4 port (make sure that -**both** ports are forwarded in your firewall), and `Z` with your email address, -which allows us to get in touch with you if there are problems with your bridge. -With your bridge configuration in place, you can now deploy the container by -running: +Replace `X` with your desired OR port, `Y` with your obfs4 port (make sure that **both** ports are forwarded in your firewall), and `Z` with your email address, which allows us to get in touch with you if there are problems with your bridge. +With your bridge configuration in place, you can now deploy the container by running: ``` docker-compose up -d obfs4-bridge ``` -This command will automatically load your `docker-compose.yml` file while -considering the environment variables in `.env`. +This command will automatically load your `docker-compose.yml` file while considering the environment variables in `.env`. You should now see output similar to the following:

1 0

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

24 Mar '21

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

1 0

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

24 Mar '21

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

1 0

[community/slideshow] better lines for l10n
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 6f3e367acaf16be7a94b13db95d642b20e598db9 Author: emma peel <emma.peel(a)riseup.net> Date: Fri Mar 5 08:17:04 2021 +0100 better lines for l10n --- content/relay-operations/technical-setup/bridge/freebsd/contents.lr | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr index e1cef75..29baea0 100644 --- a/content/relay-operations/technical-setup/bridge/freebsd/contents.lr +++ b/content/relay-operations/technical-setup/bridge/freebsd/contents.lr @@ -109,10 +109,8 @@ FreeBSDlatest: { ### 7. Final notes -If you are having trouble setting up your bridge, have a look at [our help -section](https://community.torproject.org/relay/getting-help/). If -your bridge is now running, check out the [post-install -notes](https://community.torproject.org/relay/setup/bridge/post-install/). +If you are having trouble setting up your bridge, have a look at [our help section](https://community.torproject.org/relay/getting-help/). +If your bridge is now running, check out the [post-install notes](https://community.torproject.org/relay/setup/bridge/post-install/). --- subtitle: How to deploy an obfs4 bridge on FreeBSD

1 0

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

24 Mar '21

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

1 0

[community/slideshow] Add GSoC 2021 OONI Projects
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 9a05fe9d348c40e779dae17c6cd65df7dfa4e0f2 Author: Pili Guerra <pili(a)piliguerra.com> Date: Tue Mar 9 10:11:35 2021 +0100 Add GSoC 2021 OONI Projects --- .../gsoc/ooni-explorer-code-quality/contents.lr | 61 ++++++++++++++++++++ content/gsoc/ooni-geoip-accuracy/contents.lr | 61 ++++++++++++++++++++ content/gsoc/ooni-probe-testing/contents.lr | 67 ++++++++++++++++++++++ content/gsoc/ooni-roaming-test/contents.lr | 64 +++++++++++++++++++++ 4 files changed, 253 insertions(+) diff --git a/content/gsoc/ooni-explorer-code-quality/contents.lr b/content/gsoc/ooni-explorer-code-quality/contents.lr new file mode 100644 index 0000000..a24f332 --- /dev/null +++ b/content/gsoc/ooni-explorer-code-quality/contents.lr @@ -0,0 +1,61 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 6 +--- +languages: +Javascript +ReactJS +Typescript +--- +org: OONI +--- +mentors: +Sarath +--- +difficulty: Advanced +--- +title: OONI: Improve OONI Explorer code quality +--- +subtitle: + +OONI Explorer is an open data resource on internet censorship around the world. As part of this project you would be working on helping to port OONI Explorer code to Typescript. +--- +body: + +# 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. + +OONI Explorer is an open data resource on internet censorship around the world. + +# Proposal + +Typescript has been adopted widely as a way to write more reliable JS applications and now has a well supported toolchain and an active and growing community. We could benefit from porting parts or all of the OONI Explorer code to Typescript especially to be able to handle unpredictable data in API responses. Next.js, the underlying react framework the project is built upon, also has first-class support for Typescript. The project involves: + +1. coming up with a strategy to incrementally port the codebase +1. ensuring integration with other projects in `ooni-components` +1. rewrite code +1. writing unit tests for critical react components in the projects +1. improve build process to leverage typescript features + +- **Prerequisites:** Experience in Typescript, nice to have knowledge of Next.js + +# Resources + +- OONI Explorer repo on github: https://github.com/ooni/explorer +- OONI Explorer issues github: https://github.com/ooni/explorer/issues +- https://github.com/ooni/design-system +- https://nextjs.org/docs/basic-features/typescript +- https://www.typescriptlang.org/ \ No newline at end of file diff --git a/content/gsoc/ooni-geoip-accuracy/contents.lr b/content/gsoc/ooni-geoip-accuracy/contents.lr new file mode 100644 index 0000000..1d7950d --- /dev/null +++ b/content/gsoc/ooni-geoip-accuracy/contents.lr @@ -0,0 +1,61 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 5 +--- +languages: +Java +Python +--- +org: OONI +--- +mentors: +Arturo +Federico +--- +difficulty: Medium +--- +title: OONI: Measure the accuracy of OONI GeoIP lookup +--- +subtitle: + +OONI Probe is a free software project that aims to uncover internet censorship around the world. As part of this project you would be working on developing a strategy and tooling for assessing the accuracy of our GeoIP databases. +--- +body: + +# 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 + +When attributing OONI Probe measurements to specific countries we rely on GeoIP databases (https://github.com/ooni/asn-db-generator) These database at times will attribute measurements to the wrong country. We don't currently have a good way of measuring how reliable this approach to geolocation is. +This project is about developing a strategy and tooling for assessing the accuracy of our GeoIP databases by comparing the GeoIP resolution to other location data from the probe, mostly cell tower information and GPS, while respecting user's privacy. + +- **Prerequisites:** Knowledge of Android development and ideally backend development in python + +# Resources + +- OONI Probe Engine repo on github: https://github.com/ooni/probe-engine +- Link to issue: https://github.com/ooni/probe-engine/issues/249 diff --git a/content/gsoc/ooni-probe-testing/contents.lr b/content/gsoc/ooni-probe-testing/contents.lr new file mode 100644 index 0000000..0a8d752 --- /dev/null +++ b/content/gsoc/ooni-probe-testing/contents.lr @@ -0,0 +1,67 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 7 +--- +languages: +Javascript +ReactJS +--- +org: OONI +--- +mentors: +Sarath +--- +difficulty: Medium +--- +title: OONI: Integration and unit testing of OONI Probe Desktop apps +--- +subtitle: + +OONI Probe is a free software project that aims to uncover internet censorship around the world. As part of this project you would be working on integration and unit testing of OONI Probe Desktop apps. + +--- +body: + +# 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 + +This project aims to: + +1. add support for automated testing of the desktop app to emulate the user stories end-to-end +1. add support for unit testing react components and javascript code running in electron's `main` process. + +It may be necessary to refactor parts of the codebase and upgrade dependencies to improve testability. The student is encouraged to research existing testing tools and propose solutions that can help complete the project. + +*Prerequisites:* None + +# Resources + +- https://github.com/ooni/probe-desktop/ +- http://electronjs.org/spectron +- https://docs.cypress.io/guides/component-testing/introduction.html +- https://testing-library.com/docs/react-testing-library/intro \ No newline at end of file diff --git a/content/gsoc/ooni-roaming-test/contents.lr b/content/gsoc/ooni-roaming-test/contents.lr new file mode 100644 index 0000000..fb0e4ac --- /dev/null +++ b/content/gsoc/ooni-roaming-test/contents.lr @@ -0,0 +1,64 @@ +_model: project +--- +_template: layout.html +--- +html: two-columns-page.html +--- +active: True +--- +section: GSoC +--- +section_id: gsoc +--- +color: primary +--- +key: 4 +--- +languages: +Python +--- +org: OONI +--- +mentors: +Federico +--- +difficulty: Medium/Advanced +--- +title: OONI: Implement roaming test helpers +--- +subtitle: + +OONI Probe is a free software project that aims to uncover internet censorship around the world. As part of this project you would be working on improving censorship detection while making the OONI infrastructure more resilient. +--- +body: + +# 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 + +Test helpers are endpoints used by the OONI Probes to detect censorship. The main goal of the project is to improve censorship detection while making the OONI infrastructure more resilient. The main activities are: + +1. Deploy and integrate new test helpers based on the probe codebase. +1. Automate deployment and rotation of test helpers on various public clouds. +1. Implement forwarding methods to use the test helpers as proxies for the collector API. +1. Safely serve metadata about the test collectors through the API. + +- **Prerequisites:** Understanding of Networking, Security, OS, basics of cloud services + +# Resources + + + +

1 0

[community/slideshow] Merge branch 'gsoc-archive'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit 91767c79cd2671b5f11df5f7c2b6e793915f395a Merge: 37c4986 0e16d7d Author: gus <gus(a)torproject.org> Date: Tue Mar 9 14:59:44 2021 -0300 Merge branch 'gsoc-archive' content/gsoc/{ => archive}/cloudflare-captcha-monitoring/contents.lr | 0 content/gsoc/{ => archive}/gettor-distribution/contents.lr | 0 content/gsoc/{ => archive}/onion-toolbox/contents.lr | 0 content/gsoc/{ => archive}/ooni-explorer-findings/contents.lr | 0 content/gsoc/{ => archive}/ooni-explorer-testing/contents.lr | 0 content/gsoc/{ => archive}/ooni-probe-desktop-custom-urls/contents.lr | 0 content/gsoc/{ => archive}/privacy-aware-geo-lookup/contents.lr | 0 content/gsoc/{ => archive}/privacy-friendly-web/contents.lr | 0 content/gsoc/{ => archive}/salmon-bridge-distribution/contents.lr | 0 content/gsoc/{ => archive}/snowflake-android-proxy/contents.lr | 0 content/gsoc/{ => archive}/tor-keygen/contents.lr | 0 content/gsoc/{ => archive}/tor-relay-ipv6-support/contents.lr | 0 12 files changed, 0 insertions(+), 0 deletions(-)

1 0

[community/slideshow] Merge branch 'gsoc-ooni-projects'
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit a038308793435d7239c2358ff69c8a963d445af5 Merge: 91767c7 9a05fe9 Author: gus <gus(a)torproject.org> Date: Tue Mar 9 15:00:07 2021 -0300 Merge branch 'gsoc-ooni-projects' .../gsoc/ooni-explorer-code-quality/contents.lr | 61 ++++++++++++++++++++ content/gsoc/ooni-geoip-accuracy/contents.lr | 61 ++++++++++++++++++++ content/gsoc/ooni-probe-testing/contents.lr | 67 ++++++++++++++++++++++ content/gsoc/ooni-roaming-test/contents.lr | 64 +++++++++++++++++++++ 4 files changed, 253 insertions(+)

1 0

[community/slideshow] clarify reverse DNS advice
by hiro＠torproject.org 24 Mar '21

24 Mar '21

commit f0b95049ba862bba074b72e1007663d6de2906de Author: anarcat <anarcat(a)torproject.org> Date: Mon Mar 15 14:56:36 2021 +0000 clarify reverse DNS advice We sometimes receive complaints we can't do anything about to abuse(a)torproject.org because people use the domain in the reverse DNS. This should be avoided because we (the torproject.org) are not actually responsible for the relays themselves. --- content/relay-operations/technical-setup/exit/contents.lr | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/relay-operations/technical-setup/exit/contents.lr b/content/relay-operations/technical-setup/exit/contents.lr index 69c19fc..5b17ec7 100644 --- a/content/relay-operations/technical-setup/exit/contents.lr +++ b/content/relay-operations/technical-setup/exit/contents.lr @@ -26,6 +26,8 @@ Before turning your non-exit relay into an exit relay, ensure that you have set If your provider offers it, make sure your WHOIS record contains clear indications that this is a Tor exit relay. +Do use a domain name that you own. Definitely do not use `torproject.org` as a domain name for your reverse DNS. + ## Exit Notice HTML page To make it even more obvious that this is a Tor exit relay you should serve a Tor exit notice HTML page.

1 0