[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
Re: [tor-bugs] #5866 [Ooni]: Research on test to write.
#5866: Research on test to write.
--------------------+-------------------------------------------------------
Reporter: phobos | Owner: hellais
Type: task | Status: needs_review
Priority: normal | Milestone: Sponsor H: June 2012
Component: Ooni | Version:
Keywords: | Parent:
Points: | Actualpoints:
--------------------+-------------------------------------------------------
Changes (by isis):
* status: needs_revision => needs_review
Comment:
I have been talking to Karsten and Roger, who have asked if I would be
interested in setting up continuous testing of bridge reachability, and if
they still would be interested in my doing so, I will be proposing
sometime this week a timeline for now through November 1st. Anyone who is
interested on testing bridge reachability should contact me, and all
feedback is appreciated.
As an OONI developer, I can either keep BridgeT up-to-date with the work I
am doing, or I can create a new bridge test specifically for the Sponsor F
deliverable.
The wiki looks good for now, though I will update it with progress. I
added a link to [https://blog.torproject.org/blog/research-problem-five-
ways-test-bridge-reachability Roger's TP blog post on the topic].
I think that we have specified all generalized censorship detection tests,
and though we may decide to specify further tests in the future, such
future tests will probably be specific to less commonly used protocols, or
constitute experiments on certain edge cases, which are beyond the scope
of the deliverable. In other words, while it would be hella sweet to test
for *all of the things*, we should be satisfied with (at least for this)
with testing for 99% of the things. We're done with this one, right?
--
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/5866#comment:17>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs