Opened 6 months ago

Last modified 4 weeks ago

#32716 new task

Understand where gettor distribution providers are blocked

Reported by: cohosh Owned by:
Priority: Medium Milestone:
Component: Applications/GetTor Version:
Severity: Normal Keywords: anti-censorship-roadmap-2020
Cc: traumschule, hiro, gaba, phw, cohosh Actual Points:
Parent ID: Points: 3
Reviewer: Sponsor:

Description

We should get a better understanding of where our different gettor providers are blocked. Right now we use four different providers:

  • gitlab.com
  • github.com
  • archive.org
  • docs.google.com

However, some of these domains resolve to a different URL in the process of downloading the file. For example, binaries uploaded to github used to retrieved from raw.githubusercontent.com and now it redirects to github-production-release-asset-2e65be.s3.amazonaws.com.

Perhaps we can use OONI data to stay on track of when gettor becomes unavailable due to blocking these URLs?

Child Tickets

Change History (4)

comment:1 Changed 6 months ago by phw

These are fairly uncontroversial domains, so it should be fine to use RIPE's Atlas network to periodically measure what probes can connect to these sites. Atlas allows pings, traceroutes, DNS requests, SSL requests, and HTTP requests, so it may give us a good idea of where our providers work. We probably want Atlas in addition to OONI, and not instead of.

comment:2 Changed 4 months ago by cohosh

Points: 3

comment:3 Changed 4 months ago by gaba

Keywords: anti-censorship-roadmap-2020Q1 added

comment:4 Changed 4 weeks ago by gaba

Keywords: anti-censorship-roadmap-2020 added; anti-censorship-roadmap-2020Q1 removed

No more Q1 for 2020.

Note: See TracTickets for help on using tickets.