Drop commented out project ideas
Damian Johnson

Damian Johnson commited on 2016-02-23 18:30:20
Zeige 1 geänderte Dateien mit 0 Einfügungen und 149 Löschungen.


They're invisible anyway, why burden page load with these? We can always
resurrect them later if we want - that's what revision control is for after
all!
... ...
@@ -1089,55 +1089,6 @@ information see ticket 7416.</a></b>
1089 1089
     </p>
1090 1090
     </li>
1091 1091
 
1092
-<!--
1093
-    <a id="orbotVPN"></a>
1094
-    <li>
1095
-    <b>Orbot Android VPN</b>
1096
-    <br>
1097
-    Effort Level: <i>Medium</i>
1098
-    <br>
1099
-    Skill Level: <i>High</i>
1100
-    <br>
1101
-    Likely Mentors: <i>Nathan (n8fr8)</i>
1102
-    <p>
1103
-Android offers the ability for any application to establish a
1104
-VPNService through which all traffic on the device is sent. We want to
1105
-implement this type of service in order to route all traffic through
1106
-the Tor network. This is a feature that will be implemented directly
1107
-into Orbot: Tor for Android if successfully implemented.
1108
-    </p>
1109
-
1110
-    <p>
1111
-The deliverables for the project will be a working Android VPN
1112
-implementation that routes traffic through Tor, and integration of VPN
1113
-code into the Orbot app. There must also be time made for reporting on
1114
-the project through blog posts, network auditing of tracking to ensure
1115
-leakage is not occurring.
1116
-    </p>
1117
-
1118
-    <p>
1119
-Useful links and documentation to study:
1120
-    </p>
1121
-
1122
-    <ul>
1123
-      <li><a href="https://gitweb.torproject.org/orbot.git">Orbot</a></li>
1124
-      <li><a href="http://developer.android.com/reference/android/net/VpnService.html">Android VPNService API</a></li>
1125
-      <li><a href="https://github.com/guardianproject/OrbotVPN">Existing work on Orbot VPN</a></li>
1126
-    </ul>
1127
-
1128
-    <p>
1129
-Applicant should have the ability to build Orbot application from
1130
-source using Android SDK and NDK tools. A solid understanding of IP
1131
-routing, iptables, netfilter and VPN protocols would also be very
1132
-helpful. The ability to use Wireshark or other network monitoring
1133
-software to test and verify solution is something that can be taught,
1134
-but if you already know how, bonus! Finally, understanding how the
1135
-exiting Tor software can be used with various transparent proxying
1136
-configurations is a good first step to understanding this problem.
1137
-    </p>
1138
-    </li>
1139
--->
1140
-
1141 1092
     <a id="improveTorTestCoverage"></a>
1142 1093
     <li>
1143 1094
     <b>Improve test coverage in Tor</b>
... ...
@@ -1420,106 +1371,6 @@ tampering.  Third, unit tests should be added for existing and new code
1420 1371
 in order to make the code base more robust.
1421 1372
     </p>
1422 1373
     </li>
1423
-<!--
1424
-    <a id="improveStegotorus"></a>
1425
-    <li>
1426
-    <b>Improve Stegotorus</b>
1427
-    <br>
1428
-    Effort Level: <i>Medium</i>
1429
-    <br>
1430
-    Skill Level: <i>Medium</i>
1431
-    <br>
1432
-    Likely Mentors: <i>vmon</i>
1433
-    <p>
1434
-Stegotorus is a fork of obfsproxy which helps developers to write more intelligent pluggable transports which can hide easier from deep packet inspector (DPI) system.
1435
-    </p>
1436
-
1437
-    <p>
1438
-For example, Stegotorus is equipped with a "chopper module" which takes care of following aspects:
1439
-    </p>
1440
-
1441
-    <ol>
1442
-      <li>It randomize the packet size so it is harder for the DPI system to detect the traffic base on the distribution of the packet size.</li>
1443
-      <li>It makes sure that it only handle as much (or as less) information as the transport module can handle.</li>
1444
-      <li>Chopper is equipped with it is own acknowledge/retransmit protocol. If the censor trying to disturb the connection by dropping or disturbing some of packets, it can recover the data by sending them many times.</li>
1445
-    </ol>
1446
-
1447
-    <p>
1448
-More importantly, Stegotorus is coming with its own HTTP transport module which obfuscates Tor or any other encrypted traffic in HTTP content such as Javascript code or images. HTTP transport module is also written in a way which new module developers can easily add new obfuscation modules for new contents or improve current obfuscation algorithms without the need of dealing with networking aspect of the problem.
1449
-    </p>
1450
-
1451
-    <p>
1452
-Stegotorus is written in C++. you can find the latest code <a href="https://github.com/zackw/stegotorus/tree/tor-improve">here</a>.
1453
-    </p>
1454
-
1455
-    <p>
1456
-In this regard, Stegotorus is offering one of the most complete and sophisticated platforms for writing stealthy pluggable transports.
1457
-    </p>
1458
-
1459
-    <p>
1460
-If you know C++ and interested in Stegotorus and excited about battling censorship, there are many ways that you can contribute to Stegotorus. Here are few important tasks. Your proposal might contain a good number of them:
1461
-    </p>
1462
-
1463
-    <ol>
1464
-      <li>Currently Stegotorus handshake is encrypted using the symmetric secret key of the Stegotorus bridge. However, we would like to implement a totally random handshake and considering that some transports suffer badly from "bandwidth shortage", our best choice currently is to implement <a href="http://elligator.cr.yp.to/">this algorithm</a>.</li>
1465
-      <li>Stegotorus defense against active probing is to authenticate the header of the received packet. If the authentication fails Stegotorus turns into a transparent proxy. The capability of Stegotorus as a transparent proxy needs improvement and further testing.</li>
1466
-      <li>Stegotorus has a new framework for writing Steg module. However some of the Steg modules (PDF, SWF and JS) are written in the old framework, we need to refactor their code in the new framework.</li>
1467
-      <li>As writting new Steg modules in python is easier and safer, it is desirable to write an Steg module interface for Stegotorus which can accept and interact with Steg modules written in python/cython.</li>
1468
-      <li>To make detection of anomalies in the traffic harder, Stegotorus hands a noise-to-signal ratio to each Steg modules. Steg modules' algorithms need to use more intelligent way of embedding to use this ratio.</li>
1469
-      <li>Stegotorus has several parameters to tweak its behavior. Currently all these parameters are given in command line. We would like to have a config file to store these parameters as an alternative method.</li>
1470
-      <li>The general security of the code needs to be reviewed and audited for buffer overflow, memory leak etc.</li>
1471
-      <li>Steg modules for new file format for the HTTP transport are always welcome to reflect the actual traffic of the Internet.</li>
1472
-      <li>Packaging Stegotorus for windows.</li>
1473
-      <li>There is a parallel efforts to improve Stegotorus at SRI. We would like to merge the useful feature developed by SRI in our branch of Stegotorus.</li>
1474
-      <li>Stegotorus needs to support SOCKS protocol to be able to receive the initial parameters from Tor through SOCKS handshake.</li>
1475
-    </ol>
1476
-
1477
-    <p>
1478
-You can find a list of open issues concerning Stegotorus <a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_information&status=needs_review&status=needs_revision&status=new&status=reopened&component=Stegotorus&order=priority">here</a>.
1479
-    </p>
1480
-
1481
-    <p>
1482
-You also can think of lots of other awesome creative ways of improving Stegotorus and include those in your proposal.
1483
-    </p>
1484
-    </li>
1485
--->
1486
-
1487
-<!--
1488
-    <a id="newBridgedbDistributor"></a>
1489
-    <li>
1490
-    <b>New BridgeDB Distributor</b>
1491
-    <br>
1492
-    Effort Level: <i>Medium</i>
1493
-    <br>
1494
-    Skill Level: <i>Medium to High</i>
1495
-    <br>
1496
-    Likely Mentors: <i>isis, sysrqb</i>
1497
-    <p>
1498
-BridgeDB is a Twisted Python system which runs a number of servers, in order
1499
-to distribute Tor bridge relays to users in potentially censored regions. Each
1500
-of BridgeDB's Distributors uses some unique channel to communicate bridge
1501
-addresses to users, currently there is an <a href="https://bridges.torproject.org">
1502
-HTTPS Distributor</a>, and an Email Distributor. This project would involve
1503
-designing and creating a new Distributor for BridgeDB. Some ideas for new
1504
-Distributors:
1505
-    </p>
1506
-
1507
-    <ul>
1508
-      <li>A Twitter bot which interacts with Chinese and Farsi speaking Twitter users through PMs.</li>
1509
-      <li>A distributor which uses XMPP+OTR to give bridges to users.</li>
1510
-    </ul>
1511
-
1512
-    <p>
1513
-It's helpful if you already have some knowledge of Twisted. As part of your
1514
-application, please submit a design for a Distributor, as well as supply a
1515
-patch for a ticket which demonstrates knowledge of Twisted and Python ―
1516
-preferably for BridgeDB, see the
1517
-<a href="https://trac.torproject.org/projects/tor/query?status=!closed&keywords=~bridgedb-gsoc-application">
1518
-'bridgedb-gsoc-application' Trac tag</a> for some examples of good tickets to
1519
-try, or contact isis or sysrqb on IRC to ask for ticket suggestions or advice.
1520
-    </p>
1521
-    </li>
1522
--->
1523 1374
 <!--
1524 1375
     <a id=""></a>
1525 1376
     <li>
1526 1377