Jacob: >> As you know, I've been involved with >> ONI for the past decade, and I know you've taken a very keen interest >> in these issues in the last few years (by you, I also mean the TOR >> project). > > Well, I've tried for the better part of ten years to learn about the > internal methods of ONI.
I'm not sure what you mean here, the ONI methodology has been published in each report that we've put out, and can be found on the website here: http://opennet.net/oni-faq If you are referring to why rTurtle was never released as open source, that had more to do with its history, and the fact that ONI was a university-based project where we applied controlled measures over testing, and used a limited number of contracted testers/researchers. It was never meant as a publicly accessible tool for testing. That was not its purpose or use case. At present, rTurtle is getting long in the tooth. It was great as a testing tool in the early to mid 2000's when blocking was relatively straightforward, and we were testing mostly on dial-up and DSL and WIFI connections. Now, with complex blocking and shaping events becoming the norm, there is need for a new generation of testing tools. I'm not sure what direction rTurle will take from here on in. There are some test scheduled through to at least March 2013 using rTurtle, but since the Citizen Lab has formal leadership over the technical testing component of the ONI, these questions are best directed to them. I would stress, however, that Black Watch is a SecDev-only effort, and is not a ONI-sanctioned or related testing tool. Rafal
-- Unsubscribe, change to digest, or change password at: https://mailman.stanford.edu/mailman/listinfo/liberationtech
