<div dir="ltr"><div><div>Thanks for the update.<br><br></div>I hope you are well and have no lingering problems!<br><br></div>Donald<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 4, 2013 at 7:00 AM, <span dir="ltr"><<a href="mailto:tor-reports-request@lists.torproject.org" target="_blank">tor-reports-request@lists.torproject.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send tor-reports mailing list submissions to<br>
<a href="mailto:tor-reports@lists.torproject.org">tor-reports@lists.torproject.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-reports" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-reports</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:tor-reports-request@lists.torproject.org">tor-reports-request@lists.torproject.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:tor-reports-owner@lists.torproject.org">tor-reports-owner@lists.torproject.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of tor-reports digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Arturo's February (Arturo Filast?)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Sun, 3 Mar 2013 21:53:03 +0100<br>
From: Arturo Filast? <<a href="mailto:art@torproject.org">art@torproject.org</a>><br>
To: "<a href="mailto:tor-reports@lists.torproject.org">tor-reports@lists.torproject.org</a>"<br>
<<a href="mailto:tor-reports@lists.torproject.org">tor-reports@lists.torproject.org</a>><br>
Subject: [tor-reports] Arturo's February<br>
Message-ID: <<a href="mailto:226A1818-95B5-41CC-8C05-470B3821ECAD@torproject.org">226A1818-95B5-41CC-8C05-470B3821ECAD@torproject.org</a>><br>
Content-Type: text/plain; charset=us-ascii<br>
<br>
In February I ended up getting chicken pox and was out of order for about a<br>
week, that said this is what I did:<br>
<br>
# Top 5 things I did in February:<br>
<br>
> * Work on debugging #8123<br>
<br>
Not much progress was done here as I am not able to reproduce the bug. If somebody is able to reproduce this bug help in debugging it and fixing it is greatly appreciated.<br>
<br>
> * Finish speccing out the currently implemented ooniprobe tests<br>
(<a href="https://github.com/TheTorProject/ooni-spec" target="_blank">https://github.com/TheTorProject/ooni-spec</a>)<br>
<br>
Wrote the specification for all the base test template formats and for the following ooniprobe core tests:<br>
<br>
* DNS Consistency<br>
<br>
* HTTP Requests<br>
<br>
* HTTP Host<br>
<br>
Still missing the specification of:<br>
<br>
* TCP Connect<br>
<br>
* Traceroute<br>
<br>
* Invalid Request Line<br>
<br>
* HTTP Header Field manipulation<br>
<br>
<br>
> * Consolidate the reporting format of the various ooniprobe tests with the<br>
goal of having the least amount of key nesting as possible.<br>
<br>
Done here: <a href="https://github.com/TheTorProject/ooni-probe/pull/59" target="_blank">https://github.com/TheTorProject/ooni-probe/pull/59</a><br>
<br>
> * Add support for exposing the oonib collector also over SSL and pin the SSL<br>
certificates of the ooniprobe backend colllector in the client<br>
(ooniprobe).<br>
<br>
Not done yet.<br>
<br>
> * Make the running of Tor a soft dependency and come up with an acceptable<br>
strategy for determining the probes IP address.<br>
<br>
Not done yet, but some ideas of how to do this have been identified here:<br>
<a href="https://trac.torproject.org/projects/tor/ticket/7348" target="_blank">https://trac.torproject.org/projects/tor/ticket/7348</a><br>
<a href="https://trac.torproject.org/projects/tor/ticket/8191" target="_blank">https://trac.torproject.org/projects/tor/ticket/8191</a><br>
<br>
In addition to the above tasks I also did:<br>
<br>
* Fix multiple inheritance in test #7999<br>
<a href="https://github.com/TheTorProject/ooni-probe/pull/52" target="_blank">https://github.com/TheTorProject/ooni-probe/pull/52</a><br>
<br>
* Fixed up the setup.py script for ooniprobe<br>
<a href="https://github.com/TheTorProject/ooni-probe/pull/56" target="_blank">https://github.com/TheTorProject/ooni-probe/pull/56</a><br>
<br>
* Fixed some bugs in the DNS lookup test<br>
<a href="https://github.com/TheTorProject/ooni-probe/pull/32" target="_blank">https://github.com/TheTorProject/ooni-probe/pull/32</a><br>
<br>
* Fix some bugs in the HTTP Request test:<br>
<a href="https://github.com/TheTorProject/ooni-probe/pull/37" target="_blank">https://github.com/TheTorProject/ooni-probe/pull/37</a><br>
<br>
# Top things I plan to do in March:<br>
<br>
* Make ooniprobe into a daemon<br>
<br>
* Start working on the ooniprobe HTTP API<br>
<br>
* Start working on the ooniprobe User Interface<br>
<br>
* Finish specifying the tests that are not specified<br>
<br>
<br>
~ Art.<br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
tor-reports mailing list<br>
<a href="mailto:tor-reports@lists.torproject.org">tor-reports@lists.torproject.org</a><br>
<a href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-reports" target="_blank">https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-reports</a><br>
<br>
<br>
End of tor-reports Digest, Vol 9, Issue 4<br>
*****************************************<br>
</blockquote></div><br></div>