Robert Ransom commited on 2011-02-23 14:15:41
Zeige 1 geänderte Dateien mit 51 Einfügungen und 0 Löschungen.
| ... | ... |
@@ -614,6 +614,36 @@ meetings around the world.</li> |
| 614 | 614 |
TBB, please contact Erinn.</p> |
| 615 | 615 |
</li> |
| 616 | 616 |
|
| 617 |
+ <a id="firewallProbeTool"></a> |
|
| 618 |
+ <li> |
|
| 619 |
+ <b>Develop a fully automatic firewall-probing system</b> |
|
| 620 |
+ <br> |
|
| 621 |
+ Priority: <i>High</i> |
|
| 622 |
+ <br> |
|
| 623 |
+ Effort Level: <i>Medium to High</i> |
|
| 624 |
+ <br> |
|
| 625 |
+ Skill Level: <i>High</i> |
|
| 626 |
+ <br> |
|
| 627 |
+ Likely Mentors: <i>Robert Ransom, Nick, Jacob</i> |
|
| 628 |
+ <p>We would like to have a fully automatic firewall-probing system for |
|
| 629 |
+ blocking systems with no long-term state (i.e. firewalls that can |
|
| 630 |
+ examine each connection, but do not change their behaviour for future |
|
| 631 |
+ connections based on the traffic they have seen).</p> |
|
| 632 |
+ <p>Ideally, volunteers would only need to set up one or more test servers, |
|
| 633 |
+ and run the probe client program on a publicly accessible computer |
|
| 634 |
+ behind the firewall.</p> |
|
| 635 |
+ <p>The test tool should:</p> |
|
| 636 |
+ <ul> |
|
| 637 |
+ <li>generate packet captures on both ends (and send them out to the |
|
| 638 |
+ extent possible),</li> |
|
| 639 |
+ <li>cycle through all the SSL configurations we might want to test |
|
| 640 |
+ through a censorship device, and</li> |
|
| 641 |
+ <li>also test some other protocols to see whether they are allowed |
|
| 642 |
+ through the firewall (IMAP and other mail protocols, BitTorrent, |
|
| 643 |
+ DTLS, etc.).</li> |
|
| 644 |
+ </ul> |
|
| 645 |
+ </li> |
|
| 646 |
+ |
|
| 617 | 647 |
<a id="tailsStartMenu"></a> |
| 618 | 648 |
<li> |
| 619 | 649 |
<b>Custom GDM3 startup menu, aka. tails-greeter</b> |
| ... | ... |
@@ -715,6 +745,27 @@ meetings around the world.</li> |
| 715 | 745 |
robustness.</p> |
| 716 | 746 |
</li> |
| 717 | 747 |
|
| 748 |
+ <a id="geoIPUpgrade"></a> |
|
| 749 |
+ <li> |
|
| 750 |
+ <b>Improve our GeoIP file format</b> |
|
| 751 |
+ <br> |
|
| 752 |
+ Priority: <i>Medium</i> |
|
| 753 |
+ <br> |
|
| 754 |
+ Effort Level: <i>Medium</i> |
|
| 755 |
+ <br> |
|
| 756 |
+ Skill Level: <i>Medium to High</i> |
|
| 757 |
+ <br> |
|
| 758 |
+ Likely Mentors: <i>Robert Ransom</i> |
|
| 759 |
+ <p>Currently, Tor bridges and relays read an entire IP->country database |
|
| 760 |
+ into memory from a text file during startup. We would like to |
|
| 761 |
+ distribute this database and store it on disk in a much more compact |
|
| 762 |
+ form if possible.</p> |
|
| 763 |
+ <p>We have <a href='https://trac.torproject.org/projects/tor/ticket/2506'>a |
|
| 764 |
+ sketch of a design</a> for a moderately optimized format for IPv4 GeoIP |
|
| 765 |
+ data; this project will involve both implementing the IPv4 format and |
|
| 766 |
+ designing and implementing a format for IPv6 GeoIP data.</p> |
|
| 767 |
+ </li> |
|
| 768 |
+ |
|
| 718 | 769 |
<a id="armClientMode"></a> |
| 719 | 770 |
<li> |
| 720 | 771 |
<b>Client Mode Use Cases for Arm</b> |
| 721 | 772 |