Opened 6 days ago
Last modified 5 days ago
#31701 new defect
Reachability tests for new obfs4 bridges
| Reported by: | cohosh | Owned by: | |
|---|---|---|---|
| Priority: | Medium | Milestone: | |
| Component: | Circumvention/Obfs4 | Version: | |
| Severity: | Normal | Keywords: | reachability, measurement |
| Cc: | phw | Actual Points: | |
| Parent ID: | Points: | ||
| Reviewer: | Sponsor: |
Description
As a follow up to #29279, we can now set up some new reachability tests on a subset of the bridges we've gotten through our bridge campaign \o/
We probably don't want to test all of the new bridges in case these tests cause a bunch of bridges to get blocked when they otherwise wouldn't.
As mentioned in #29279:comment:9, we should sample bridges from our various distribution mechanisms (email, private, and HTTPS), and also from any finer grained partitions we have (email provider, subnet, etc.).
Child Tickets
Note: See
TracTickets for help on using
tickets.
Sounds good to me. I will extract a few and send them your way. I'm particularly interested in learning if our moat bucket is being scraped too.