Drop project ideas done by successful students last year
Damian Johnson

Damian Johnson commited on 2015-02-03 17:13:57
Zeige 1 geänderte Dateien mit 0 Einfügungen und 231 Löschungen.


There's a few projects like 'tor daemon optimization' which I'm unsure if it
maps to something on this page. Just dropping the entries clearly the focus of
students we passed last year.
... ...
@@ -413,7 +413,6 @@ meetings around the world.</li>
413 413
     <i><a href="#improveTorTestCoverage">Improve test coverage in Tor</a></i><br />
414 414
     <i><a href="#useMoreCores">Have the Tor daemon use more cores</a></i><br />
415 415
     <i><a href="#improveHiddenServices">Help improve Tor hidden services</a></i><br />
416
-    <i><a href="#consensusDiffs">Implement consensus diffs</a></i><br />
417 416
     <i><a href="#improvedDnsSupport">Improved DNS support for Tor</a></i><br />
418 417
     <i><a href="#torSandboxing">Help improve Tor sandboxing</a></i>
419 418
     </p>
... ...
@@ -491,7 +490,6 @@ meetings around the world.</li>
491 490
     <p>
492 491
     <b>Project Ideas:</b><br />
493 492
     <i><a href="#orbotVPN">Orbot Android VPN</a></i><br />
494
-    <i><a href="#orfox">Orfox - Firefox/Gecko-based Android Browser for Tor</a></i>
495 493
     </p>
496 494
 
497 495
     <a id="project-tails"></a>
... ...
@@ -724,11 +722,6 @@ meetings around the world.</li>
724 722
     in early 2011.
725 723
     </p>
726 724
 
727
-    <p>
728
-    <b>Project Ideas:</b><br />
729
-    <i><a href="#rewriteWeather">Rewrite Tor Weather</a></i><br />
730
-    </p>
731
-
732 725
     <a id="project-gettor"></a>
733 726
     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/GetTor">GetTor</a> (<a
734 727
     href="https://gitweb.torproject.org/gettor.git">code</a>, <a
... ...
@@ -740,11 +733,6 @@ meetings around the world.</li>
740 733
     relatively unchanged for quite a while.
741 734
     </p>
742 735
 
743
-    <p>
744
-    <b>Project Ideas:</b><br />
745
-    <i><a href="#revamp_gettor">Revamp GetTor</a></i>
746
-    </p>
747
-
748 736
     <a id="project-torcheck"></a>
749 737
     <h3><a href="https://trac.torproject.org/projects/tor/wiki/org/roadmaps/TorCheck">TorCheck</a> (<a
750 738
     href="https://gitweb.torproject.org/check.git">code</a>, <a
... ...
@@ -1068,35 +1056,6 @@ meetings around the world.</li>
1068 1056
     </b>
1069 1057
     </p>
1070 1058
 
1071
-    <a id="hsSearchEngine"></a>
1072
-    <li>
1073
-    <b>Search Engine for Hidden Services</b>
1074
-    <br>
1075
-    Effort Level: <i>Medium</i>
1076
-    <br>
1077
-    Skill Level: <i>Medium</i>
1078
-    <br>
1079
-    Likely Mentors: <i>George (asn)</i>
1080
-    <p>
1081
-    This project involves researching and developing a search engine for
1082
-    Hidden Services.
1083
-    </p>
1084
-
1085
-    <p>
1086
-    The student is expected to develop a search engine that can index
1087
-    hidden services and reply to search queries. The student should also
1088
-    develop a crawler that can search both "clear web" and hidden service
1089
-    websites to find more addresses. The student is expected to use and
1090
-    improve already existing search engine frameworks (e.g. YaCy), and not
1091
-    reinvent the wheel when it's possible.
1092
-    </p>
1093
-
1094
-    <p>
1095
-    The student should have a decent understanding of how search engines
1096
-    work, what algorithms they use, and of any related open source tools
1097
-    that are currently available.
1098
-    </p>
1099
-
1100 1059
     <a id="profileUDPTransport"></a>
1101 1060
     <li>
1102 1061
     <b>Profile UDP transport protocols</b>
... ...
@@ -1301,60 +1260,6 @@ configurations is a good first step to understanding this problem.
1301 1260
     </p>
1302 1261
     </li>
1303 1262
 
1304
-    <a id="orfox"></a>
1305
-    <li>
1306
-    <b>Orfox - Firefox/Gecko-based Android Browser for Tor</b>
1307
-    <br>
1308
-    Effort Level: <i>High</i>
1309
-    <br>
1310
-    Skill Level: <i>Medium</i>
1311
-    <br>
1312
-    Likely Mentors: <i>Nathan (n8fr8)</i>
1313
-    <p>
1314
-With almost 1 million downloads, our Orweb browser has been a popular
1315
-solution for easily accessing the web via Tor or any other HTTP or
1316
-SOCKS proxy, while also ensuring local data caches are cleared and
1317
-cookies are properly managed. Orweb is based on WebView, which has its
1318
-limitations unfortunately. We would like to move to a
1319
-Firefox/Fennec/GeckoView based browser, and have created a prototype
1320
-for it. Mozilla has begun releasing GeckoView as a standalone
1321
-component, as well, but it needs more testing, debugging and work on
1322
-integration into our streamlined browser app model. Our end goal is to
1323
-have a mobile browser that matches Tor Browser in terms of privacy
1324
-enhancing features and security.
1325
-    </p>
1326
-
1327
-    <p>
1328
-The deliverables for the project are expected to be the creation of a
1329
-alpha quality release of Orfox, a GeckoView-based browser with feature
1330
-parity of Orweb browser. A bonus goal is to implement additional
1331
-features and capabilities based on Tor Browser patches for
1332
-Fennec/Mozilla core. Finally, as always, a required activity is a
1333
-network audit testing of implemented solution with write-ups, reports
1334
-posted publicly.
1335
-    </p>
1336
-
1337
-    <p>
1338
-Useful links to review:
1339
-    </p>
1340
-
1341
-    <ul>
1342
-      <li><a href="https://github.com/guardianproject/orfox">Orfox (gecko prototype)</a></li>
1343
-      <li><a href="https://github.com/guardianproject/orweb">Orweb (production browser on WebView)</a></li>
1344
-      <li><a href="http://starkravingfinkle.org/blog/2013/10/geckoview-embedding-gecko-in-your-android-application/">GeckoView info</a></li>
1345
-      <li><a href="<page projects/torbrowser>">Tor Browser (desktop)</a></li>
1346
-    </ul>
1347
-
1348
-    <p>
1349
-Applicant should have the ability to build Fennec and GeckoView
1350
-libraries from source using Android SDK and NDK. Some experince with
1351
-browser security models and threats would be a useful background to
1352
-have. Ability to do network audits to ensure browser proxying is not
1353
-leaking DNS, media streams or other network traffic, as well as tests
1354
-against common browser de-anonymizing attacks are necessary.
1355
-    </p>
1356
-    </li>
1357
-
1358 1263
     <a id="improveTorTestCoverage"></a>
1359 1264
     <li>
1360 1265
     <b>Improve test coverage in Tor</b>
... ...
@@ -1508,51 +1413,6 @@ the codebase that you want to work on.
1508 1413
     </p>
1509 1414
     </li>
1510 1415
 
1511
-    <a id="consensusDiffs"></a>
1512
-    <li>
1513
-    <b>Implement consensus diffs</b>
1514
-    <br>
1515
-    Effort Level: <i>Medium</i>
1516
-    <br>
1517
-    Skill Level: <i>Medium</i>
1518
-    <br>
1519
-    Likely Mentors: <i>Nick (nickm)</i>
1520
-    <p>
1521
-Right now, every few hours, a Tor client downloads a new signed "consensus
1522
-document" that describes the state of the network.  Even though these
1523
-documents are compressed, thisstill takes almost half a megabyte.
1524
-    </p>
1525
-
1526
-    <p>
1527
-<a
1528
-href="https://gitweb.torproject.org/torspec.git/blob_plain/refs/heads/master:/proposals/140-consensus-diffs.txt">Proposal
1529
-140</a> describes a design to save a lot of bandwidth by transferring
1530
-compressed <a href="http://en.wikipedia.org/wiki/Diff">diff</a>s instead
1531
-of transferring the entire consensus document.
1532
-    </p>
1533
-
1534
-    <p>
1535
-That's an attractive idea, but it presents some programming challenges.
1536
-We probably don't want to ship a 'diff' and 'patch' along with Tor.  Is
1537
-there a free, <strong>safe</strong>, robust implementation of one of the
1538
-good diff algorithms that we can use?
1539
-    </p>
1540
-
1541
-    <p>
1542
-Alternatively, can we take advantage of regularities in the descriptor
1543
-format in order to generate diffs more simply?
1544
-    </p>
1545
-
1546
-    <p>
1547
-As part of the application process for this project, please contribute a
1548
-nontrivial patch to Tor -- ideally, one that will affect some part of
1549
-the codebase that you want to work on.  Make sure that your application
1550
-describes which implementations of the diff and patch algorithms you
1551
-intend to use, and that your coding samples show strong evidence that
1552
-you can do secure string manipulation in C.
1553
-    </p>
1554
-    </li>
1555
-
1556 1416
     <a id="improvedDnsSupport"></a>
1557 1417
     <li>
1558 1418
     <b>Improved DNS support for Tor</b>
... ...
@@ -1712,97 +1572,6 @@ implementation.
1712 1572
     </p>
1713 1573
     </li>
1714 1574
 
1715
-    <a id="revamp_gettor"></a>
1716
-    <li>
1717
-    <b>Revamp GetTor</b>
1718
-    <br>
1719
-    Effort Level: <i>High</i>
1720
-    <br>
1721
-    Skill Level: <i>Medium</i>
1722
-    <br>
1723
-    Likely Mentors: <i>Sukhbir Singh (sukhe), Nima Fatemi (mrphs)</i>
1724
-    <p>
1725
-GetTor is a program that serves Tor bundles and related components over SMTP.
1726
-Users request the Tor Browser by sending an email to GetTor, which sends
1727
-back Tor Browser as email attachments. In countries where the Tor Project
1728
-website is blocked, GetTor is a convenient way for users to get access to Tor
1729
-Browser.
1730
-    </p>
1731
-
1732
-    <p>
1733
-GetTor has been unmaintained for a while and needs a revamp. The main issue is
1734
-that because the Tor Browser size exceeds 25 MB, sending it through
1735
-GetTor no longer works as most email providers don't support attachments
1736
-exceeding 25 MB. To alleviate this issue, Tor Browsers are now uploaded on
1737
-cloud-based services such as Google Drive and Dropbox and links are sent
1738
-out in the email body instead of attachments. This current setup is far from
1739
-complete -- GetTor needs a lot of work to get it to a point where it can do
1740
-smart things again and do them in the right way.
1741
-    </p>
1742
-
1743
-    <p>
1744
-As part of this project, you should:
1745
-    </p>
1746
-
1747
-    <ul>
1748
-      <li>Have some understanding of what GetTor does in general and the current state of its operation.</li>
1749
-      <li>Come up with ideas on how to make it better.</li>
1750
-      <li>Convince us if you would like to fix the existing code or want to rewrite GetTor from scratch.</li>
1751
-    </ul>
1752
-
1753
-    <p>
1754
-In addition to the above points, applications should be familiar with Python.
1755
-As part of the application process, study the <a
1756
-href="https://gitweb.torproject.org/gettor.git">GetTor code</a> and submit a
1757
-patch for returning the SHA1 checksum of the package instead of the text in
1758
-sendSorrySize() in response.py. (since you cannot test the patch, as long as it
1759
-is clear that you had some idea of what you were doing, it should be fine)
1760
-    </p>
1761
-
1762
-    <p>
1763
-Note: Please do not submit an application without talking to the mentors: #sukhe and #mrphs on IRC. IRC is preferred but if for any reason you don't want/can't use it, please email the mentors.
1764
-    </p>
1765
-    </li>
1766
-
1767
-    <a id="rewriteWeather"></a>
1768
-    <li>
1769
-    <b>Rewrite Tor Weather</b>
1770
-    <br>
1771
-    Effort Level: <i>Medium</i>
1772
-    <br>
1773
-    Skill Level: <i>Medium</i>
1774
-    <br>
1775
-    Likely Mentors: <i>Karsten (karsten)</i>
1776
-    <p>
1777
-<a href="https://weather.torproject.org/">Tor Weather</a> provides an
1778
-email notification service to any users who want to monitor the status
1779
-of a Tor node.  Its favorite feature is to notify relay operators when
1780
-their relay has earned them a Tor t-shirt.  Tor Weather is written in
1781
-Python/Django.
1782
-    </p>
1783
-
1784
-    <p>
1785
-The Tor Weather codebase is pretty much unmaintained these days.  The
1786
-first part of this project would be to simplify the code by fetching Tor
1787
-network status data from <a
1788
-href="https://onionoo.torproject.org/">Onionoo</a> rather than running a
1789
-local tor client and keeping an own relay history database.  See the
1790
-related <a
1791
-href="https://trac.torproject.org/projects/tor/wiki/doc/weather-in-2014">community
1792
-effort to rewrite Weather</a> that started in January 2014.  After that,
1793
-there's a <a
1794
-href="https://trac.torproject.org/projects/tor/query?status=!closed&component=Tor+Weather">long
1795
-list of open tickets</a> to be resolved.
1796
-    </p>
1797
-
1798
-    <p>
1799
-Ideally, the student would become the new Weather maintainer after the
1800
-summer.  If that doesn't work out, the codebase should have become a lot
1801
-smaller by end of summer, so that it becomes easier to find somebody
1802
-else as new maintainer.
1803
-    </p>
1804
-    </li>
1805
-
1806 1575
     <a id="improveStegotorus"></a>
1807 1576
     <li>
1808 1577
     <b>Improve Stegotorus</b>
1809 1578