Damian Johnson commited on 2012-03-01 17:54:05
Zeige 1 geänderte Dateien mit 86 Einfügungen und 0 Löschungen.
Project ideas provided by George (I made a few minor tweaks so it would be more fitting with the current listing).
| ... | ... |
@@ -469,6 +469,13 @@ meetings around the world.</li> |
| 469 | 469 |
block Tor. |
| 470 | 470 |
</p> |
| 471 | 471 |
|
| 472 |
+ <p> |
|
| 473 |
+ <b>Project Ideas:</b><br /> |
|
| 474 |
+ <i><a href="#obfsproxy-new-transports">New and innovative pluggable transports</a></i><br /> |
|
| 475 |
+ <i><a href="#obfsproxy-scanning-measures">Defensive bridge active scanning measures</a></i><br /> |
|
| 476 |
+ <i><a href="#obfsproxy-fuzzer">Fuzzer for the Tor protocol</a></i> |
|
| 477 |
+ </p> |
|
| 478 |
+ |
|
| 472 | 479 |
<a id="project-thandy"></a> |
| 473 | 480 |
<h3>Thandy (<a |
| 474 | 481 |
href="https://gitweb.torproject.org/thandy.git">code</a>)</h3> |
| ... | ... |
@@ -763,6 +770,54 @@ meetings around the world.</li> |
| 763 | 770 |
on this so far.</p> |
| 764 | 771 |
</li> |
| 765 | 772 |
|
| 773 |
+ <a id="obfsproxy-new-transports"></a> |
|
| 774 |
+ <li> |
|
| 775 |
+ <b>New and innovative pluggable transports</b> |
|
| 776 |
+ <br> |
|
| 777 |
+ Priority: <i>High</i> |
|
| 778 |
+ <br> |
|
| 779 |
+ Effort Level: <i>High</i> |
|
| 780 |
+ <br> |
|
| 781 |
+ Skill Level: <i>High</i> |
|
| 782 |
+ <br> |
|
| 783 |
+ Likely Mentors: <i>asn</i> |
|
| 784 |
+ <p>Not-very-smart transports like ROT13 and base64 are nice but not super |
|
| 785 |
+ interesting. Other ideas like bittorrent transports might be relevant, |
|
| 786 |
+ but you will have to provide security proofs on why they are harder to |
|
| 787 |
+ detect and block than other less-sophisticated transports.</p> |
|
| 788 |
+ |
|
| 789 |
+ <p>The whole point of this project, though, is to come up with new |
|
| 790 |
+ transports that we haven't already thought of. Be creative.</p> |
|
| 791 |
+ |
|
| 792 |
+ <p>Bonus points if your idea is interesting and still implementable |
|
| 793 |
+ through the summer period.</p> |
|
| 794 |
+ |
|
| 795 |
+ <p>More bonus points if it's implemented on top of obfsproxy, or if your |
|
| 796 |
+ implementation has a pluggable transport interface on top of it (as |
|
| 797 |
+ specified <a href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/180-pluggable-transport.txt">here</a>).</p> |
|
| 798 |
+ </li> |
|
| 799 |
+ |
|
| 800 |
+ <a id="obfsproxy-scanning-measures"></a> |
|
| 801 |
+ <li> |
|
| 802 |
+ <b>Defensive bridge active scanning measures</b> |
|
| 803 |
+ <br> |
|
| 804 |
+ Priority: <i>High</i> |
|
| 805 |
+ <br> |
|
| 806 |
+ Effort Level: <i>High</i> |
|
| 807 |
+ <br> |
|
| 808 |
+ Skill Level: <i>High</i> |
|
| 809 |
+ <br> |
|
| 810 |
+ Likely Mentors: <i>asn</i> |
|
| 811 |
+ <p>Involves providing good answers to <a |
|
| 812 |
+ href="https://lists.torproject.org/pipermail/tor-dev/2011-November/003073.html">this |
|
| 813 |
+ thread</a> as well as concrete implementation plans for it.</p> |
|
| 814 |
+ |
|
| 815 |
+ <p>This also involves implementing proposals <a |
|
| 816 |
+ href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/189-authorize-cell.txt">189</a> |
|
| 817 |
+ and <a |
|
| 818 |
+ href="https://gitweb.torproject.org/torspec.git/blob/HEAD:/proposals/190-shared-secret-bridge-authorization.txt">190</a>.</p> |
|
| 819 |
+ </li> |
|
| 820 |
+ |
|
| 766 | 821 |
<a id="orbot-userInterface"></a> |
| 767 | 822 |
<li> |
| 768 | 823 |
<b>Build a better user interface for Orbot</b> |
| ... | ... |
@@ -1341,6 +1396,37 @@ meetings around the world.</li> |
| 1341 | 1396 |
</p> |
| 1342 | 1397 |
</li> |
| 1343 | 1398 |
|
| 1399 |
+ <a id="obfsproxy-fuzzer"></a> |
|
| 1400 |
+ <li> |
|
| 1401 |
+ <b>Fuzzer for the Tor protocol</b> |
|
| 1402 |
+ <br> |
|
| 1403 |
+ Priority: <i>Low to Medium</i> |
|
| 1404 |
+ <br> |
|
| 1405 |
+ Effort Level: <i>Medium to High</i> |
|
| 1406 |
+ <br> |
|
| 1407 |
+ Skill Level: <i>High</i> |
|
| 1408 |
+ <br> |
|
| 1409 |
+ Likely Mentors: <i>asn</i> |
|
| 1410 |
+ <p>Involves researching good and smart ways to fuzz stateful network |
|
| 1411 |
+ protocols, and also implementing the fuzzer.</p> |
|
| 1412 |
+ |
|
| 1413 |
+ <p>We are mostly looking for a fuzzer that fuzzes the Tor protocol |
|
| 1414 |
+ itself, and not the Tor directory protocol.</p> |
|
| 1415 |
+ |
|
| 1416 |
+ <p>Bonus points if it's extremely modular. Relevant research:</p> |
|
| 1417 |
+ |
|
| 1418 |
+ <ul> |
|
| 1419 |
+ <li>PROTOS - Security Testing of Protocol Implementations</li> |
|
| 1420 |
+ <li>INTERSTATE: A Stateful Protocol Fuzzer for SIP</li> |
|
| 1421 |
+ <li>Detecting Communication Protocol Security Flaws by Formal Fuzz |
|
| 1422 |
+ Testing and Machine Learning</li> |
|
| 1423 |
+ <li>SNOOZE: Toward a Stateful NetwOrk prOtocol fuzZE</li> |
|
| 1424 |
+ <li>Michal Zalewski's "bugger"</li> |
|
| 1425 |
+ <li>Also look at the concepts of "model checking" and |
|
| 1426 |
+ "symbolic execution" to get inspired.</li> |
|
| 1427 |
+ </ul> |
|
| 1428 |
+ </li> |
|
| 1429 |
+ |
|
| 1344 | 1430 |
<!-- |
| 1345 | 1431 |
<a id="armGui"></a> |
| 1346 | 1432 |
<li> |
| 1347 | 1433 |