Changes between Initial Version and Version 6 of Ticket #29297


Ignore:
Timestamp:
Mar 4, 2019, 9:41:51 PM (6 months ago)
Author:
cohosh
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #29297

    • Property Status changed from new to assigned
    • Property Component changed from - Select a component to Obfuscation/Obfsproxy
    • Property Summary changed from Add any necessary metrics to verify if obfs4 is working or not to Write reachability tests to verify if obfs4 is working or not
    • Property Points changed from to 2
    • Property Sponsor changed from to Sponsor19
    • Property Actual Points changed from 2 to
    • Property Owner set to cohosh
    • Property Type changed from defect to task
  • Ticket #29297 – Description

    initial v6  
    1 Ensure that we have all necessary metrics to verify if obfs4 is working for users.
     1The main goal of this is to determine whether obfs4 bridges are being blocked due to bridge IP enumeration, or if there is something blockable about the obfs4 protocol.
    22
    3 TODO: Determine what these metrics should be, where they should be added, methods for aggregating them and analyzing them.
     3These tests will use new, private (unpublished) obfs4 IP addresses that have not been used for censorship circumvention prior to these tests.
    44
     5The outcome should be a script that users we reach out to in censored can run from which we can collect metrics about their ability to connect and bandwidth measurements. Before we send out the script we should figure out:
     6
     7- Whether we have all necessary metrics on the bridge side to verify if obfs4 is working and whether it is being throttled
     8
     9- How we are going to collect the client-side measurement data