Damn me. Teor asked for a couple small tweaks for the project page (noting that
it's in part rust and removing athena) almost two months ago. Unfortunately I
was ill at the time so got buried under a stack of todo notes. :/
... | ... |
@@ -109,9 +109,9 @@ meetings around the world.</li> |
109 | 109 |
<tr> |
110 | 110 |
<td><a href="#project-tor">Tor</a></td> |
111 | 111 |
<td>Core</td> |
112 |
- <td>C</td> |
|
112 |
+ <td>C, Rust</td> |
|
113 | 113 |
<td>Heavy</td> |
114 |
- <td>nickm, athena, arma, dgoulet, asn, teor</td> |
|
114 |
+ <td>nickm, arma, dgoulet, asn, teor</td> |
|
115 | 115 |
</tr> |
116 | 116 |
|
117 | 117 |
<tr> |
... | ... |
@@ -386,7 +386,6 @@ meetings around the world.</li> |
386 | 386 |
<p> |
387 | 387 |
<b>Project Ideas:</b><br /> |
388 | 388 |
<i><a href="#metadataremoval">Remove metadata from Tor Browser uploads</a></i><br /> |
389 |
- <i><a href="#fasterTorBrowser">Make Tor Browser Faster</a></i> |
|
390 | 389 |
</p> |
391 | 390 |
|
392 | 391 |
<a id="project-httpseverywhere"></a> |
... | ... |
@@ -1022,20 +1021,6 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/17 |
1022 | 1021 |
</p> |
1023 | 1022 |
</li> |
1024 | 1023 |
--> |
1025 |
- <a id="fasterTorBrowser"></a> |
|
1026 |
- <li> |
|
1027 |
- <b>Make Tor Browser Faster</b> |
|
1028 |
- <br> |
|
1029 |
- Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>, <i>Arthur Edelstein (arthuredelstein)</i> |
|
1030 |
- <p> |
|
1031 |
- This project will enable and take advantage of HTTP/2, the Alt-Srv |
|
1032 |
- header, and tor's new single hop .onion mode to enable websites to |
|
1033 |
- transparently move their traffic to a .onion address. In addition to |
|
1034 |
- improvements in security, we will benchmark page load and paint times |
|
1035 |
- under normal HTTP/1.1, HTTP/2, and when taking advantage of features |
|
1036 |
- such as Server Push. |
|
1037 |
- </p> |
|
1038 |
- </li> |
|
1039 | 1024 |
|
1040 | 1025 |
<a id="ahmiaSearch"></a> |
1041 | 1026 |
<li> |
Signed-off-by: hiro <hiro@torproject.org>
... | ... |
@@ -575,7 +575,7 @@ meetings around the world.</li> |
575 | 575 |
</p> |
576 | 576 |
|
577 | 577 |
<a id="project-onionoo"></a> |
578 |
- <h3><a href="https://onionoo.torproject.org/">Onionoo</a> (<a |
|
578 |
+ <h3><a href="https://metrics.torproject.org/onionoo.html">Onionoo</a> (<a |
|
579 | 579 |
href="https://gitweb.torproject.org/onionoo.git">code</a>, |
580 | 580 |
<a href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics%2FOnionoo&order=priority">bug tracker</a>)</h3> |
581 | 581 |
|
Signed-off-by: hiro <hiro@torproject.org>
... | ... |
@@ -555,7 +555,7 @@ meetings around the world.</li> |
555 | 555 |
</p> |
556 | 556 |
|
557 | 557 |
<a id="project-atlas"></a> |
558 |
- <h3><a href="https://atlas.torproject.org/">Relay Search</a> (<a |
|
558 |
+ <h3><a href="https://metrics.torproject.org/rs.html">Relay Search</a> (<a |
|
559 | 559 |
href="https://gitweb.torproject.org/atlas.git">code</a>)</h3> |
560 | 560 |
|
561 | 561 |
<p> |
... | ... |
@@ -64,7 +64,7 @@ meetings around the world.</li> |
64 | 64 |
href="https://media.torproject.org/video/">Tor's Media server</a>, |
65 | 65 |
<a |
66 | 66 |
href="http://www.howcast.com/videos/90601-How-To-Circumvent-an-Internet-Proxy/">Howcast</a>, |
67 |
- and <a href="http://www.youtube.com/c/thetorproject">YouTube</a>.</li> |
|
67 |
+ and <a href="https://www.youtube.com/user/TheTorProject">YouTube</a>.</li> |
|
68 | 68 |
<li>Create a poster around a theme, such as "Tor for Freedom!"</li> |
69 | 69 |
<li>Create a t-shirt design that incorporates "<a |
70 | 70 |
href="https://check.torproject.org/">Congratulations! You are using |
Signed-off-by: hiro <hiro@torproject.org>
... | ... |
@@ -358,7 +358,8 @@ meetings around the world.</li> |
358 | 358 |
|
359 | 359 |
<p> |
360 | 360 |
<b>Project Ideas:</b><br /> |
361 |
- <i><a href="#improveOnionServices">Help improve Tor onion services</a></i><br /> |
|
361 |
+ # <i><a href="#improveOnionServices">Help improve Tor onion services</a></i><br /> |
|
362 |
+ <i><a href="#pythonTorClient">Python Tor Client</a></i><br /> |
|
362 | 363 |
<i><a href="#torFuzzing">Fuzzing coverage of Tor</a></i><br /> |
363 | 364 |
<i><a href="#relayCryptoParallelism">Relay crypto parallelism</a></i><br /> |
364 | 365 |
<i><a href="#anonymousLocalCountStatistics">Anonymous local count statistics</a></i><br /> |
... | ... |
@@ -384,8 +385,7 @@ meetings around the world.</li> |
384 | 385 |
|
385 | 386 |
<p> |
386 | 387 |
<b>Project Ideas:</b><br /> |
387 |
- <i><a href="#feedbackExtension">Feedback Extension for Tor Browser</a></i><br /> |
|
388 |
- <i><a href="#torBrowserCrashReport">Crash Reporter for Tor Browser</a></i><br /> |
|
388 |
+ <i><a href="#metadataremoval">Remove metadata from Tor Browser uploads</a></i><br /> |
|
389 | 389 |
<i><a href="#fasterTorBrowser">Make Tor Browser Faster</a></i> |
390 | 390 |
</p> |
391 | 391 |
|
... | ... |
@@ -860,7 +860,7 @@ understand how our mocking system works, and what the challenges are, |
860 | 860 |
before you apply for this one. |
861 | 861 |
</p> |
862 | 862 |
</li> |
863 |
-<!-- |
|
863 |
+ |
|
864 | 864 |
<a id="relayCryptoParallelism"></a> |
865 | 865 |
<li> |
866 | 866 |
<b>Relay crypto parallelism</b> |
... | ... |
@@ -887,7 +887,7 @@ one. |
887 | 887 |
For more information <a href="https://trac.torproject.org/projects/tor/ticket/1749">see its ticket</a>. |
888 | 888 |
</p> |
889 | 889 |
</li> |
890 |
+ |
|
890 | 891 |
<a id="anonymousLocalCountStatistics"></a> |
891 | 892 |
<li> |
892 | 893 |
<b>Anonymous local count statistics</b> |
... | ... |
@@ -926,7 +926,7 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/12 |
926 | 926 |
</p> |
927 | 927 |
</li> |
928 | 928 |
|
929 |
-<!-- |
|
929 |
+ |
|
930 | 930 |
#Keep old ids in case of incoming links. |
931 | 931 |
<a id="onionServiceCryptoParallelism"></a><a id="hiddenServiceCryptoParallelism"></a> |
932 | 932 |
<li> |
... | ... |
@@ -971,7 +971,7 @@ this, but it might need some clean-up. |
971 | 971 |
For more information <a href="https://trac.torproject.org/projects/tor/ticket/7829">see its ticket</a>. |
972 | 972 |
</p> |
973 | 973 |
</li> |
974 |
+ |
|
974 | 975 |
<a id="improveIpv6Support"></a> |
975 | 976 |
<li> |
976 | 977 |
<b>Improve IPv6 support</b> |
... | ... |
@@ -771,7 +771,7 @@ meetings around the world.</li> |
771 | 771 |
<br> |
772 | 772 |
Language: <i>Python</i> |
773 | 773 |
<br> |
774 |
- Likely Mentors: <i>Damian (atagar), Tim (teor)</i> |
|
774 |
+ Likely Mentors: <i>Damian (atagar), teor</i> |
|
775 | 775 |
<br><br> |
776 | 776 |
<p> |
777 | 777 |
<b><a href="https://stem.torproject.org/">Stem</a></b> is our Python implementation of Tor's varous protocols. Traditionally this included <a href="https://stem.torproject.org/tutorials/the_little_relay_that_could.html">stem.control</a> for Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/control-spec.txt">ControlPort</a> and <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html">stem.descriptor</a> to download from Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt">DirPort</a>. But recently we added a third to this family, <b><a href="https://lists.torproject.org/pipermail/tor-dev/2018-February/012905.html">stem.client</a></b>, that speaks Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt">ORPort protocol</a>: the relay protocol for usage of the Tor network itself. |
... | ... |
@@ -798,7 +798,7 @@ And more! Applicants are encouraged to get a decent understanding of <a href="ht |
798 | 798 |
<b>As part of applying for this project please get your hands wet with the codebase by contributing some patches for <a href="https://stem.torproject.org/faq.html#how-do-i-get-started">Stem</a>!</b> |
799 | 799 |
</p> |
800 | 800 |
</li> |
801 |
- |
|
801 |
+<!-- |
|
802 | 802 |
<a id="improveOnionServices"></a><a id="improveHiddenServices"></a> |
803 | 803 |
<li> |
804 | 804 |
<b>Help improve Tor onion services</b> |
... | ... |
@@ -835,7 +835,7 @@ href="https://lists.torproject.org/pipermail/tor-dev/2016-October/011514.html">v |
835 | 835 |
ideas. |
836 | 836 |
</p> |
837 | 837 |
</li> |
838 |
- |
|
838 |
+--> |
|
839 | 839 |
<a id="torFuzzing"></a> |
840 | 840 |
<li> |
841 | 841 |
<b>Fuzzing coverage of Tor</b> |
... | ... |
@@ -860,7 +860,7 @@ understand how our mocking system works, and what the challenges are, |
860 | 860 |
before you apply for this one. |
861 | 861 |
</p> |
862 | 862 |
</li> |
863 |
- |
|
863 |
+<!-- |
|
864 | 864 |
<a id="relayCryptoParallelism"></a> |
865 | 865 |
<li> |
866 | 866 |
<b>Relay crypto parallelism</b> |
... | ... |
@@ -887,7 +887,7 @@ one. |
887 | 887 |
For more information <a href="https://trac.torproject.org/projects/tor/ticket/1749">see its ticket</a>. |
888 | 888 |
</p> |
889 | 889 |
</li> |
890 |
- |
|
890 |
+--> |
|
891 | 891 |
<a id="anonymousLocalCountStatistics"></a> |
892 | 892 |
<li> |
893 | 893 |
<b>Anonymous local count statistics</b> |
... | ... |
@@ -911,7 +911,7 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/75 |
911 | 911 |
<li> |
912 | 912 |
<b>Improved SOCKS5 variant</b> |
913 | 913 |
<br> |
914 |
- Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet)</i> |
|
914 |
+ Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet), meejah</i> |
|
915 | 915 |
<br><br> |
916 | 916 |
<p> |
917 | 917 |
In proposal 229, we describe a bunch of additional SOCKS extensions |
... | ... |
@@ -926,6 +926,7 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/12 |
926 | 926 |
</p> |
927 | 927 |
</li> |
928 | 928 |
|
929 |
+<!-- |
|
929 | 930 |
#Keep old ids in case of incoming links. |
930 | 931 |
<a id="onionServiceCryptoParallelism"></a><a id="hiddenServiceCryptoParallelism"></a> |
931 | 932 |
<li> |
... | ... |
@@ -970,7 +971,7 @@ this, but it might need some clean-up. |
970 | 971 |
For more information <a href="https://trac.torproject.org/projects/tor/ticket/7829">see its ticket</a>. |
971 | 972 |
</p> |
972 | 973 |
</li> |
973 |
- |
|
974 |
+--> |
|
974 | 975 |
<a id="improveIpv6Support"></a> |
975 | 976 |
<li> |
976 | 977 |
<b>Improve IPv6 support</b> |
... | ... |
@@ -996,7 +997,7 @@ network: are you up for it? |
996 | 997 |
For more information <a href="https://trac.torproject.org/projects/tor/ticket/17811">see its ticket</a>. |
997 | 998 |
</p> |
998 | 999 |
</li> |
999 |
- |
|
1000 |
+<!-- |
|
1000 | 1001 |
<a id="feedbackExtension"></a> |
1001 | 1002 |
<li> |
1002 | 1003 |
<b>Feedback Extension for Tor Browser</b> |
... | ... |
@@ -1020,36 +1021,12 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/17 |
1020 | 1021 |
feedback process. |
1021 | 1022 |
</p> |
1022 | 1023 |
</li> |
1023 |
- |
|
1024 |
- <a id="torBrowserCrashReport"></a> |
|
1025 |
- <li> |
|
1026 |
- <b>Crash Reporter for Tor Browser</b> |
|
1027 |
- <br> |
|
1028 |
- Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i> |
|
1029 |
- <p> |
|
1030 |
- Currently Tor Browser disables the Crash Reporter. We would like to |
|
1031 |
- build it reproducible, enable it, and configure it to report crashes |
|
1032 |
- containing non-detailed and impersonal information to Tor, on a .onion |
|
1033 |
- submission platform that would allow us to view and explore the |
|
1034 |
- crashes. |
|
1035 |
- </p> |
|
1036 |
- |
|
1037 |
- <p> |
|
1038 |
- The project will entail enabling the Crash Report on Tor Browser and |
|
1039 |
- creating a backend to receive reports from it. Once created, the crash |
|
1040 |
- reporter data will be analyzed and modified to fit Tor's requirements |
|
1041 |
- for personal data collection. As time permits, we will update the |
|
1042 |
- build system to ensure the crash reporter is built reproducibly and |
|
1043 |
- add data analysis tools for the crash report database to visualize top |
|
1044 |
- crashers and similar statistics. |
|
1045 |
- </p> |
|
1046 |
- </li> |
|
1047 |
- |
|
1024 |
+--> |
|
1048 | 1025 |
<a id="fasterTorBrowser"></a> |
1049 | 1026 |
<li> |
1050 | 1027 |
<b>Make Tor Browser Faster</b> |
1051 | 1028 |
<br> |
1052 |
- Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i> |
|
1029 |
+ Likely Mentors: <i>Tom Ritter (tjr)</i>, <i>Georg (GeKo)</i>, <i>Arthur Edelstein (arthuredelstein)</i> |
|
1053 | 1030 |
<p> |
1054 | 1031 |
This project will enable and take advantage of HTTP/2, the Alt-Srv |
1055 | 1032 |
header, and tor's new single hop .onion mode to enable websites to |
... | ... |
@@ -1089,37 +1066,6 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/17 |
1089 | 1066 |
search itself works without client-side JavaScript. |
1090 | 1067 |
</p> |
1091 | 1068 |
|
1092 |
- <p> |
|
1093 |
- There are several possible directions for this project, including... |
|
1094 |
- </p> |
|
1095 |
- |
|
1096 |
- <ol> |
|
1097 |
- <li>Automate blacklisting (very important)<br /> |
|
1098 |
- <ul> |
|
1099 |
- <li>Fetch a list of child abuse media sites</li> |
|
1100 |
- <li>Remove these sites from the search results</li> |
|
1101 |
- </ul> |
|
1102 |
- </li> |
|
1103 |
- <li>Add onion services function (very important)<br /> |
|
1104 |
- <ul> |
|
1105 |
- <li>You can add onions using HTML form</li> |
|
1106 |
- <li>Call the crawler immidiately when a new site is added</li> |
|
1107 |
- </ul> |
|
1108 |
- </li> |
|
1109 |
- <li>Elasticsearch<br /> |
|
1110 |
- <ul> |
|
1111 |
- <li>Must be updated to 5.X.X sooner or later</li> |
|
1112 |
- <li>Adjust the settings</li> |
|
1113 |
- <li>Automatically remove data older than, for instance, 90 days</li> |
|
1114 |
- </ul> |
|
1115 |
- </li> |
|
1116 |
- <li>Maintainance<br /> |
|
1117 |
- <ul> |
|
1118 |
- <li>Update all software dependencies</li> |
|
1119 |
- <li>Automate crash recovery for Tor, Elasticsearch and crawler</li> |
|
1120 |
- </ul> |
|
1121 |
- </li> |
|
1122 |
- </ol> |
|
1123 | 1069 |
</li> |
1124 | 1070 |
|
1125 | 1071 |
<!-- |
... | ... |
@@ -745,7 +745,8 @@ meetings around the world.</li> |
745 | 745 |
users around the world. We are looking for a programmer fluent in JS |
746 | 746 |
and C++ to implement new features to work closely with the Tor Browser |
747 | 747 |
team. |
748 |
- |
|
748 |
+ </p> |
|
749 |
+ <p> |
|
749 | 750 |
Image files, especially photos taken by smartphones, |
750 | 751 |
often carry hidden privacy-violating metadata, typically specified by |
751 | 752 |
the EXIF format. Such metadata can include the user's geolocation and |
... | ... |
@@ -756,10 +757,11 @@ meetings around the world.</li> |
756 | 757 |
implement this feature for both desktop and mobile Tor Browser. If |
757 | 758 |
there is time, we can envision sanitizing other kinds of uploaded |
758 | 759 |
files, including movies, audio, PDFs and Office documents. |
759 |
- |
|
760 | 760 |
</p> |
761 | 761 |
<p> |
762 | 762 |
For more information <a href="https://trac.torproject.org/projects/tor/ticket/24965">see its ticket</a>. |
763 |
+ Please also see <a href="https://mat.boum.org">the Metadata Anonymisation Toolkit (MAT)</a> for a |
|
764 |
+ similar project that could serve as inspiration. |
|
763 | 765 |
</p> |
764 | 766 |
</li> |
765 | 767 |
|
... | ... |
@@ -735,6 +735,34 @@ meetings around the world.</li> |
735 | 735 |
<ol> |
736 | 736 |
|
737 | 737 |
#Keep old ids in case of incoming links. |
738 |
+ <a id="metadataremoval"></a> |
|
739 |
+ <li> |
|
740 |
+ <b>Remove metadata from Tor Browser uploads</b> |
|
741 |
+ <br> |
|
742 |
+ Likely Mentors: <i>Arthur D. Edelstein (arthuredelstein)</i> |
|
743 |
+ <p> |
|
744 |
+ Tor Browser is a privacy-preserving web browser used by millions of |
|
745 |
+ users around the world. We are looking for a programmer fluent in JS |
|
746 |
+ and C++ to implement new features to work closely with the Tor Browser |
|
747 |
+ team. |
|
748 |
+ |
|
749 |
+ Image files, especially photos taken by smartphones, |
|
750 |
+ often carry hidden privacy-violating metadata, typically specified by |
|
751 |
+ the EXIF format. Such metadata can include the user's geolocation and |
|
752 |
+ various unique identifiers. In order to protect the user's identity, |
|
753 |
+ we would like the intern to modify the file-upload feature in Tor |
|
754 |
+ Browser such that metadata in image files is automatically removed |
|
755 |
+ before the image is uploaded to a server. Ideally, the summer intern would |
|
756 |
+ implement this feature for both desktop and mobile Tor Browser. If |
|
757 |
+ there is time, we can envision sanitizing other kinds of uploaded |
|
758 |
+ files, including movies, audio, PDFs and Office documents. |
|
759 |
+ |
|
760 |
+ </p> |
|
761 |
+ <p> |
|
762 |
+ For more information <a href="https://trac.torproject.org/projects/tor/ticket/24965">see its ticket</a>. |
|
763 |
+ </p> |
|
764 |
+ </li> |
|
765 |
+ |
|
738 | 766 |
<a id="pythonTorClient"></a><a id="pythonTorClient"></a> |
739 | 767 |
<li> |
740 | 768 |
<b>Python Tor Client</b> |
... | ... |
@@ -727,7 +727,7 @@ meetings around the world.</li> |
727 | 727 |
about/gsoc>">Google Summer of Code</a> or the Tor Summer of Privacy. We have labelled each idea with |
728 | 728 |
which of our <a href="<page about/corepeople>">core developers</a> would be |
729 | 729 |
good mentors. If one or more of these ideas looks promising to you, please |
730 |
- <a href="<page about/contact>">contact us</a> to discuss your plans rather |
|
730 |
+ <a href="mailto:tor-sop@lists.torproject.org">contact us</a> to discuss your plans rather |
|
731 | 731 |
than sending blind applications. You may also want to propose your own |
732 | 732 |
project idea — which often results in the best applications. |
733 | 733 |
</p> |
... | ... |
@@ -724,7 +724,7 @@ meetings around the world.</li> |
724 | 724 |
|
725 | 725 |
<p> |
726 | 726 |
You may find some of these projects to be good ideas for <a href="<page |
727 |
- about/gsoc>">Google Summer of Code</a>. We have labelled each idea with |
|
727 |
+ about/gsoc>">Google Summer of Code</a> or the Tor Summer of Privacy. We have labelled each idea with |
|
728 | 728 |
which of our <a href="<page about/corepeople>">core developers</a> would be |
729 | 729 |
good mentors. If one or more of these ideas looks promising to you, please |
730 | 730 |
<a href="<page about/contact>">contact us</a> to discuss your plans rather |
Neat idea from David so people can write a 'is my hidden service up?' check.
... | ... |
@@ -757,6 +757,7 @@ This opens interesting opportunities we've never had before such as... |
757 | 757 |
<li>Download hidden service descriptors. Unlike relays, the descriptors for hidden services are only available over the ORPort. Once <a href="https://trac.torproject.org/projects/tor/ticket/17945">ticket 17945</a> is merged v3 HS descriptor downloads will require a multi-hop circuit. This requires an understanding of Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt">hidden service</a> specifications, particularly the HSDir hash ring.</li> |
758 | 758 |
<li>Authenticate our ORPort connection, checking that ORPorts we connect to have the right key fingerprint.</li> |
759 | 759 |
<li>Add protocol level integration test of Tor's ORPort, for instance exercising edge cases in circuit construction and extension.</li> |
760 |
+ <li>Connect to a hidden service to check if it's up or not.</li> |
|
760 | 761 |
</ul> |
761 | 762 |
|
762 | 763 |
<p> |
Couple more subtasks, courtesy of Tim.
... | ... |
@@ -754,6 +754,8 @@ This opens interesting opportunities we've never had before such as... |
754 | 754 |
<ul> |
755 | 755 |
<li>Construct a full three-hop circuit that can make GET requests and DNS lookups. If done right this might allow simple usage of the Tor network without even having Tor installed!</li> |
756 | 756 |
<li>Expand <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html#where-can-i-get-the-current-descriptors">descriptor downloading</a> to use Tor's ORPort as an optional alternative for the DirPort. Following this we could adjust Tor so <a href="https://trac.torproject.org/projects/tor/ticket/19129">Fallback Directories no longer require a DirPort</a>.</li> |
757 |
+ <li>Download hidden service descriptors. Unlike relays, the descriptors for hidden services are only available over the ORPort. Once <a href="https://trac.torproject.org/projects/tor/ticket/17945">ticket 17945</a> is merged v3 HS descriptor downloads will require a multi-hop circuit. This requires an understanding of Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/rend-spec-v3.txt">hidden service</a> specifications, particularly the HSDir hash ring.</li> |
|
758 |
+ <li>Authenticate our ORPort connection, checking that ORPorts we connect to have the right key fingerprint.</li> |
|
757 | 759 |
<li>Add protocol level integration test of Tor's ORPort, for instance exercising edge cases in circuit construction and extension.</li> |
758 | 760 |
</ul> |
759 | 761 |
|
Posting the SoP project Tim and I have been brainstorming. This is just the
first draft - I still need to run this by Tim and hopefully come up with more
ideas on subtasks.
... | ... |
@@ -519,6 +519,11 @@ meetings around the world.</li> |
519 | 519 |
Tor. |
520 | 520 |
</p> |
521 | 521 |
|
522 |
+ <p> |
|
523 |
+ <b>Project Ideas:</b><br /> |
|
524 |
+ <i><a href="#pythonTorClient">Python Tor Client</a></i> |
|
525 |
+ </p> |
|
526 |
+ |
|
522 | 527 |
<a id="project-txtorcon"></a> |
523 | 528 |
<h3><a href="https://txtorcon.readthedocs.io/en/latest/">Txtorcon</a> (<a |
524 | 529 |
href="https://github.com/meejah/txtorcon">code</a>, <a |
... | ... |
@@ -730,6 +735,37 @@ meetings around the world.</li> |
730 | 735 |
<ol> |
731 | 736 |
|
732 | 737 |
#Keep old ids in case of incoming links. |
738 |
+ <a id="pythonTorClient"></a><a id="pythonTorClient"></a> |
|
739 |
+ <li> |
|
740 |
+ <b>Python Tor Client</b> |
|
741 |
+ <br> |
|
742 |
+ Language: <i>Python</i> |
|
743 |
+ <br> |
|
744 |
+ Likely Mentors: <i>Damian (atagar), Tim (teor)</i> |
|
745 |
+ <br><br> |
|
746 |
+ <p> |
|
747 |
+<b><a href="https://stem.torproject.org/">Stem</a></b> is our Python implementation of Tor's varous protocols. Traditionally this included <a href="https://stem.torproject.org/tutorials/the_little_relay_that_could.html">stem.control</a> for Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/control-spec.txt">ControlPort</a> and <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html">stem.descriptor</a> to download from Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/dir-spec.txt">DirPort</a>. But recently we added a third to this family, <b><a href="https://lists.torproject.org/pipermail/tor-dev/2018-February/012905.html">stem.client</a></b>, that speaks Tor's <a href="https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt">ORPort protocol</a>: the relay protocol for usage of the Tor network itself. |
|
748 |
+ </p> |
|
749 |
+ |
|
750 |
+ <p> |
|
751 |
+This opens interesting opportunities we've never had before such as... |
|
752 |
+ </p> |
|
753 |
+ |
|
754 |
+ <ul> |
|
755 |
+ <li>Construct a full three-hop circuit that can make GET requests and DNS lookups. If done right this might allow simple usage of the Tor network without even having Tor installed!</li> |
|
756 |
+ <li>Expand <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html#where-can-i-get-the-current-descriptors">descriptor downloading</a> to use Tor's ORPort as an optional alternative for the DirPort. Following this we could adjust Tor so <a href="https://trac.torproject.org/projects/tor/ticket/19129">Fallback Directories no longer require a DirPort</a>.</li> |
|
757 |
+ <li>Add protocol level integration test of Tor's ORPort, for instance exercising edge cases in circuit construction and extension.</li> |
|
758 |
+ </ul> |
|
759 |
+ |
|
760 |
+ <p> |
|
761 |
+And more! Applicants are encouraged to get a decent understanding of <a href="https://gitweb.torproject.org/torspec.git/tree/tor-spec.txt">Tor's ORPort protocol</a> and come up with ideas of their own for neat directions that we can take this. To be clear this is <b>not</b> a particularly easy beginner project as it involves expanding stem.client to support more of Tor's ORPort protocol and crypto. |
|
762 |
+ </p> |
|
763 |
+ |
|
764 |
+ <p> |
|
765 |
+<b>As part of applying for this project please get your hands wet with the codebase by contributing some patches for <a href="https://stem.torproject.org/faq.html#how-do-i-get-started">Stem</a>!</b> |
|
766 |
+ </p> |
|
767 |
+ </li> |
|
768 |
+ |
|
733 | 769 |
<a id="improveOnionServices"></a><a id="improveHiddenServices"></a> |
734 | 770 |
<li> |
735 | 771 |
<b>Help improve Tor onion services</b> |
Oops! First thought when I saw this was 'how the heck did this get here since
we weren't accepted?'. But then I realized it was leftover from *last year*.
... | ... |
@@ -75,18 +75,6 @@ meetings around the world.</li> |
75 | 75 |
different languages as conversation starter.</li> |
76 | 76 |
</ol> |
77 | 77 |
|
78 |
- <a id="gsoc"></a> |
|
79 |
- <h2><a class="anchor" href="#gsoc">Google Summer of Code</a></h2> |
|
80 |
- |
|
81 |
- <p> |
|
82 |
- Tor is also taking part in this year's <a |
|
83 |
- href="https://summerofcode.withgoogle.com/">Google |
|
84 |
- Summer of Code</a>! To apply but you need to be either <a |
|
85 |
- href="https://developers.google.com/open-source/gsoc/faq#what_are_the_eligibility_requirements_for_participation">a |
|
86 |
- present student or just graduated</a>. <b>See our page for <a href="<page |
|
87 |
- about/gsoc>">Google Summer of Code</a> for more information.</b> |
|
88 |
- </p> |
|
89 |
- |
|
90 | 78 |
<a id="Projects"></a> |
91 | 79 |
<h2><a class="anchor" href="#Projects">Projects</a></h2> |
92 | 80 |
|
* Atlas is now known as Relay Search
* Compass will soon no longer be running at compass.torproject.org
* Globe has been not running for a while now
... | ... |
@@ -247,21 +247,13 @@ meetings around the world.</li> |
247 | 247 |
</tr> |
248 | 248 |
|
249 | 249 |
<tr> |
250 |
- <td><a href="#project-atlas">Atlas</a></td> |
|
250 |
+ <td><a href="#project-atlas">Relay Search</a></td> |
|
251 | 251 |
<td>Client Service</td> |
252 | 252 |
<td>JavaScript</td> |
253 | 253 |
<td>Light</td> |
254 | 254 |
<td>irl</td> |
255 | 255 |
</tr> |
256 | 256 |
|
257 |
- <tr> |
|
258 |
- <td><a href="#project-compass">Compass</a></td> |
|
259 |
- <td>Client Service</td> |
|
260 |
- <td>Python</td> |
|
261 |
- <td>None</td> |
|
262 |
- <td></td> |
|
263 |
- </tr> |
|
264 |
- |
|
265 | 257 |
<tr> |
266 | 258 |
<td><a href="#project-onionoo">Onionoo</a></td> |
267 | 259 |
<td>Backend Service</td> |
... | ... |
@@ -570,13 +562,13 @@ meetings around the world.</li> |
570 | 562 |
</p> |
571 | 563 |
|
572 | 564 |
<a id="project-atlas"></a> |
573 |
- <h3><a href="https://atlas.torproject.org/">Atlas</a> (<a |
|
565 |
+ <h3><a href="https://atlas.torproject.org/">Relay Search</a> (<a |
|
574 | 566 |
href="https://gitweb.torproject.org/atlas.git">code</a>)</h3> |
575 | 567 |
|
576 | 568 |
<p> |
577 |
- Atlas is a web application to discover Tor relays and bridges. It provides |
|
578 |
- useful information on how relays are configured along with graphics about |
|
579 |
- their past usage. |
|
569 |
+ Relay Search is a web application to discover Tor relays and bridges. It |
|
570 |
+ provides useful information on how relays are configured along with graphics |
|
571 |
+ about their past usage. |
|
580 | 572 |
</p> |
581 | 573 |
|
582 | 574 |
<p> |
... | ... |
@@ -589,17 +581,6 @@ meetings around the world.</li> |
589 | 581 |
been discontinued. |
590 | 582 |
</p> |
591 | 583 |
|
592 |
- <a id="project-compass"></a> |
|
593 |
- <h3><a href="https://compass.torproject.org/">Compass</a> (<a |
|
594 |
- href="https://gitweb.torproject.org/compass.git">code</a>, <a |
|
595 |
- href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Metrics%2FCompass&order=priority">bug |
|
596 |
- tracker</a>)</h3> |
|
597 |
- |
|
598 |
- <p> |
|
599 |
- Compass is a web and command line application that filters and |
|
600 |
- aggregates the Tor relays based on various attributes. |
|
601 |
- </p> |
|
602 |
- |
|
603 | 584 |
<a id="project-onionoo"></a> |
604 | 585 |
<h3><a href="https://onionoo.torproject.org/">Onionoo</a> (<a |
605 | 586 |
href="https://gitweb.torproject.org/onionoo.git">code</a>, |
Some parts of this task are done, and others need to be updated. Still giving
thought about a good project to propose this year.
... | ... |
@@ -539,11 +539,6 @@ meetings around the world.</li> |
539 | 539 |
Tor. |
540 | 540 |
</p> |
541 | 541 |
|
542 |
- <p> |
|
543 |
- <b>Project Ideas:</b><br /> |
|
544 |
- <i><a href="#stemDescriptors">Stem Descriptors</a></i> |
|
545 |
- </p> |
|
546 |
- |
|
547 | 542 |
<a id="project-txtorcon"></a> |
548 | 543 |
<h3><a href="https://txtorcon.readthedocs.io/en/latest/">Txtorcon</a> (<a |
549 | 544 |
href="https://github.com/meejah/txtorcon">code</a>, <a |
... | ... |
@@ -1027,39 +1022,6 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/17 |
1027 | 1022 |
</p> |
1028 | 1023 |
</li> |
1029 | 1024 |
|
1030 |
- <a id="stemDescriptors"></a> |
|
1031 |
- <li> |
|
1032 |
- <b>Stem Descriptors</b> |
|
1033 |
- <br> |
|
1034 |
- Language: <i>Python</i> |
|
1035 |
- <br> |
|
1036 |
- Likely Mentors: <i>Damian Johnson (atagar), Philipp Winter (phw)</i> |
|
1037 |
- <p> |
|
1038 |
- <a href="https://stem.torproject.org/">Stem</a> is a Python library for working with tor. With it you can build applications on tor as well as learn information about the relay network. This project concerns this second capability. |
|
1039 |
- </p> |
|
1040 |
- |
|
1041 |
- <p> |
|
1042 |
- Information about relays are published hourly in documents called <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html">descriptors</a>. With Stem you can download, parse, and validate all kinds of descriptor documents. |
|
1043 |
- </p> |
|
1044 |
- |
|
1045 |
- <p> |
|
1046 |
- Ideas welcome! You're encouraged to brainstorm improvements we can make to this space but here's a few to get you started... |
|
1047 |
- </p> |
|
1048 |
- |
|
1049 |
- <ul> |
|
1050 |
- <li><p><b><a href="https://trac.torproject.org/projects/tor/ticket/11045">Validate signatures in the consensus</a></b>. Stem has the ability to validate cryptographic signatures in several descriptor types but not the consensus.</p></li> |
|
1051 |
- <li><p><b><a href="https://trac.torproject.org/projects/tor/ticket/21086">Migrate from pycrypto to a supported library</a></b>. Stem presently uses pycrypto for signature validation but it's no longer maintained. We should evaluate options and move to whatever whavever the cool kids are using nowadays.</p></li> |
|
1052 |
- <li><p><b><a href="https://trac.torproject.org/projects/tor/ticket/18856">Retrieve descriptors over tor's ORPort</a></b>. Tor relays commonly provide two ports, an <b>ORPort</b> which is used by clients and a <b>DirPort</b> which is obsolete nowadays but in the past was used by tor to download descriptors. Stem still uses tor's DirPort to retrieve descriptors, but it would be neat if we could download from the ORPort instead.</p> |
|
1053 |
- <p>This requires implementing part of tor's communication protocol. Depending how complicated this is it might be neat to expand this task to allow the full construction of circuits, allowing client usage of tor without the C executable. Keep in mind though that this later bit hasn't been investigated and might be a pipe dream. ;P</p></li> |
|
1054 |
- <li><p><b>Improve performance of reading descriptors</b>. Stem <a href="https://stem.torproject.org/tutorials/mirror_mirror_on_the_wall.html#are-there-any-other-parsing-libraries">isn't the only descriptor parsing library</a> and sadly is the slowest. Tricks like lazy loading have substantially improved our performance but no doubt a dedicated effort to profile Stem would find more low hanging fruit.</p></li> |
|
1055 |
- </ul> |
|
1056 |
- |
|
1057 |
- |
|
1058 |
- <p> |
|
1059 |
- <b>As part of applying for this project please get your hands wet with the codebase by contributing some patches for <a href="https://stem.torproject.org/faq.html#how-do-i-get-started">Stem</a>!</b> |
|
1060 |
- </p> |
|
1061 |
- </li> |
|
1062 |
- |
|
1063 | 1025 |
<a id="ahmiaSearch"></a> |
1064 | 1026 |
<li> |
1065 | 1027 |
<b>Ahmia - Onion Service Search</b> |
... | ... |
@@ -14,7 +14,7 @@ |
14 | 14 |
<ol> |
15 | 15 |
<li>Please consider <a href="<page docs/tor-doc-relay>">running |
16 | 16 |
a relay</a> to help the Tor network grow.</li> |
17 |
- <li>Tell your friends! Get them to run relays. Get them to run hidden |
|
17 |
+ <li>Tell your friends! Get them to run relays. Get them to run onion |
|
18 | 18 |
services. Get them to tell their friends.</li> |
19 | 19 |
<li>If you like Tor's goals, please <a href="<page donate/donate>">take a moment |
20 | 20 |
to donate to support further Tor development</a>. We're also looking |
... | ... |
@@ -378,12 +378,12 @@ meetings around the world.</li> |
378 | 378 |
|
379 | 379 |
<p> |
380 | 380 |
<b>Project Ideas:</b><br /> |
381 |
- <i><a href="#improveHiddenServices">Help improve Tor hidden services</a></i><br /> |
|
381 |
+ <i><a href="#improveOnionServices">Help improve Tor onion services</a></i><br /> |
|
382 | 382 |
<i><a href="#torFuzzing">Fuzzing coverage of Tor</a></i><br /> |
383 | 383 |
<i><a href="#relayCryptoParallelism">Relay crypto parallelism</a></i><br /> |
384 | 384 |
<i><a href="#anonymousLocalCountStatistics">Anonymous local count statistics</a></i><br /> |
385 | 385 |
<i><a href="#improveSocks5Variant">Improved SOCKS5 variant</a></i><br /> |
386 |
- <i><a href="#hiddenServiceCryptoParallelism">Hidden service crypto parallelism</a></i><br /> |
|
386 |
+ <i><a href="#onionServiceCryptoParallelism">Onion service crypto parallelism</a></i><br /> |
|
387 | 387 |
<i><a href="#supportAllDNS">Support all kinds of DNS in Tor</a></i><br /> |
388 | 388 |
<i><a href="#improveIpv6Support">Improve IPv6 support</a></i> |
389 | 389 |
</p> |
... | ... |
@@ -765,28 +765,29 @@ meetings around the world.</li> |
765 | 765 |
|
766 | 766 |
<ol> |
767 | 767 |
|
768 |
- <a id="improveHiddenServices"></a> |
|
768 |
+ #Keep old ids in case of incoming links. |
|
769 |
+ <a id="improveOnionServices"></a><a id="improveHiddenServices"></a> |
|
769 | 770 |
<li> |
770 |
- <b>Help improve Tor hidden services</b> |
|
771 |
+ <b>Help improve Tor onion services</b> |
|
771 | 772 |
<br> |
772 | 773 |
Language: <i>C</i> |
773 | 774 |
<br> |
774 | 775 |
Likely Mentors: <i>George (asn), David Goulet (dgoulet)</i> |
775 | 776 |
<br><br> |
776 | 777 |
<p> |
777 |
-The hidden services team is busy implementing <a |
|
778 |
+The onion services team is busy implementing <a |
|
778 | 779 |
href="https://gitweb.torproject.org/torspec.git/tree/proposals/224-rend-spec-ng.txt">proposal |
779 |
-224</a> but we are always open to mentoring fun and exciting hidden |
|
780 |
+224</a> but we are always open to mentoring fun and exciting onion |
|
780 | 781 |
service projects. |
781 | 782 |
</p> |
782 | 783 |
|
783 | 784 |
<p> |
784 |
-In the past, we've mentored a wide variety of projects related to hidden |
|
785 |
+In the past, we've mentored a wide variety of projects related to onion |
|
785 | 786 |
services, ranging from <a |
786 | 787 |
href="https://lists.torproject.org/pipermail/tor-dev/2016-April/010832.html">onion |
787 | 788 |
search engines</a>, <a |
788 | 789 |
href="https://lists.torproject.org/pipermail/tor-talk/2015-May/037966.html">to |
789 |
-scaling techniques for hidden services</a>, |
|
790 |
+scaling techniques for onion services</a>, |
|
790 | 791 |
and also various approaches |
791 | 792 |
of making onion services more <a |
792 | 793 |
href="https://lists.torproject.org/pipermail/tor-dev/2012-June/003588.html">usable</a> |
... | ... |
@@ -892,24 +893,25 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/12 |
892 | 893 |
</p> |
893 | 894 |
</li> |
894 | 895 |
|
895 |
- <a id="hiddenServiceCryptoParallelism"></a> |
|
896 |
+ #Keep old ids in case of incoming links. |
|
897 |
+ <a id="onionServiceCryptoParallelism"></a><a id="hiddenServiceCryptoParallelism"></a> |
|
896 | 898 |
<li> |
897 |
- <b>Hidden service crypto parallelism</b> |
|
899 |
+ <b>Onion service crypto parallelism</b> |
|
898 | 900 |
<br> |
899 | 901 |
Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet)</i> |
900 | 902 |
<br><br> |
901 | 903 |
<p> |
902 |
-Hidden services, hidden service clients, hidden service directories, |
|
904 |
+Onion services, onion service clients, onion service directories, |
|
903 | 905 |
and introduction points all need to do a few public-key operations as |
904 | 906 |
they operate. But right now, these operations are all done on the |
905 | 907 |
main thread. It would be good to have these run across multiple cores. |
906 | 908 |
</p> |
907 | 909 |
|
908 | 910 |
<p> |
909 |
-This could probably be done in a way similar to how we currently hand |
|
911 |
+This could probably be done in a way similar to how we currently handle |
|
910 | 912 |
circuit extension handshakes in onion.c and cpuworker.c, but we'd need |
911 |
-to extend the state machine for hidden services to add an additional |
|
912 |
-state. It could help hidden services operate much more efficiently. |
|
913 |
+to extend the state machine for onion services to add an additional |
|
914 |
+state. It could help onion services operate much more efficiently. |
|
913 | 915 |
</p> |
914 | 916 |
|
915 | 917 |
<p> |
... | ... |
@@ -1060,13 +1062,13 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/17 |
1060 | 1062 |
|
1061 | 1063 |
<a id="ahmiaSearch"></a> |
1062 | 1064 |
<li> |
1063 |
- <b>Ahmia - Hidden Service Search</b> |
|
1065 |
+ <b>Ahmia - Onion Service Search</b> |
|
1064 | 1066 |
<br> |
1065 | 1067 |
Language: <i>Python, Django</i> |
1066 | 1068 |
<br> |
1067 | 1069 |
Likely Mentors: <i>Juha Nurmi (numes), George (asn)</i> |
1068 | 1070 |
<p> |
1069 |
- Ahmia is open-source search engine software for Tor hidden service deep |
|
1071 |
+ Ahmia is open-source search engine software for Tor onion service deep |
|
1070 | 1072 |
dark web sites. You can test the running search engine at ahmia.fi. For |
1071 | 1073 |
more information see our <a |
1072 | 1074 |
href="https://blog.torproject.org/category/tags/ahmiafi">blog post about |
... | ... |
@@ -1075,7 +1077,7 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/17 |
1075 | 1077 |
|
1076 | 1078 |
<p> |
1077 | 1079 |
Ahmia is a working search engine that indexes, searches, and catalogs |
1078 |
- content published on Tor Hidden Services. Furthermore, it is an environment |
|
1080 |
+ content published on Tor Onion Services. Furthermore, it is an environment |
|
1079 | 1081 |
to share meaningful insights, statistics, insights, and news about the Tor |
1080 | 1082 |
network itself. In this context, there is a lot of work to do. |
1081 | 1083 |
</p> |
... | ... |
@@ -1098,7 +1100,7 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/17 |
1098 | 1100 |
<li>Remove these sites from the search results</li> |
1099 | 1101 |
</ul> |
1100 | 1102 |
</li> |
1101 |
- <li>Add hidden services funtion (very important)<br /> |
|
1103 |
+ <li>Add onion services function (very important)<br /> |
|
1102 | 1104 |
<ul> |
1103 | 1105 |
<li>You can add onions using HTML form</li> |
1104 | 1106 |
<li>Call the crawler immidiately when a new site is added</li> |
just use <specblob> everywhere now.
... | ... |
@@ -1146,7 +1146,7 @@ For more information <a href="https://trac.torproject.org/projects/tor/ticket/17 |
1146 | 1146 |
href="/press/presskit/2008-12-19-roadmap-full.pdf">Tor development |
1147 | 1147 |
roadmap</a> for more ideas, or just try out Tor and Tor Browser, |
1148 | 1148 |
and find out what you think needs fixing. |
1149 |
- Some of the <a href="<spectree>proposals">current proposals</a> |
|
1149 |
+ Some of the <a href="<specblob>proposals">current proposals</a> |
|
1150 | 1150 |
might also be short on developers. |
1151 | 1151 |
</li> |
1152 | 1152 |
|
Oops, missed that there was a link on
https://trac.torproject.org/projects/tor/ticket/24184
... | ... |
@@ -55,7 +55,8 @@ |
55 | 55 |
href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">tor-relays</a>, <a |
56 | 56 |
href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev">tor-dev</a>, or <a |
57 | 57 |
href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tbb-dev">tbb-dev</a>, |
58 |
- and summarize noteworthy changes into articles for our blog and newsletter.</li> |
|
58 |
+ and summarize noteworthy changes into articles for our blog and <a |
|
59 |
+ href="https://newsletter.torproject.org/">newsletter</a>.</li> |
|
59 | 60 |
<li>Create a presentation that can be used for various user group |
60 | 61 |
meetings around the world.</li> |
61 | 62 |
<li>Create a video about the positive uses of Tor, what Tor is, |
Request by Steph on...
https://trac.torproject.org/projects/tor/ticket/24184
... | ... |
@@ -55,9 +55,7 @@ |
55 | 55 |
href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-relays">tor-relays</a>, <a |
56 | 56 |
href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev">tor-dev</a>, or <a |
57 | 57 |
href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tbb-dev">tbb-dev</a>, |
58 |
- and summarize noteworthy exchanges into articles for <a |
|
59 |
- href="https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-news">Tor |
|
60 |
- Weekly News</a>.</li> |
|
58 |
+ and summarize noteworthy changes into articles for our blog and newsletter.</li> |
|
61 | 59 |
<li>Create a presentation that can be used for various user group |
62 | 60 |
meetings around the world.</li> |
63 | 61 |
<li>Create a video about the positive uses of Tor, what Tor is, |
Think I got 'em all. Now that Nyx is live we can aggressively start
dereferencing the old name.
... | ... |
@@ -423,7 +423,7 @@ meetings around the world.</li> |
423 | 423 |
</p> |
424 | 424 |
|
425 | 425 |
<a id="project-nyx"></a> |
426 |
- <h3><a href="https://www.atagar.com/arm/">Nyx</a> (<a |
|
426 |
+ <h3><a href="https://nyx.torproject.org/">Nyx</a> (<a |
|
427 | 427 |
href="https://gitweb.torproject.org/nyx.git">code</a>, <a |
428 | 428 |
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Core+Tor%2FNyx&order=priority">bug |
429 | 429 |
tracker</a>)</h3> |
David gave his ok on...
https://trac.torproject.org/projects/tor/ticket/19360
... | ... |
@@ -199,14 +199,6 @@ meetings around the world.</li> |
199 | 199 |
<td>sukhe</td> |
200 | 200 |
</tr> |
201 | 201 |
|
202 |
- <tr> |
|
203 |
- <td><a href="#project-flash-proxy">Flash Proxy</a></td> |
|
204 |
- <td>Client Add-on</td> |
|
205 |
- <td>Python, JavaScript, Go</td> |
|
206 |
- <td>Light</td> |
|
207 |
- <td>dcf, infinity0, Arlo Breault</td> |
|
208 |
- </tr> |
|
209 |
- |
|
210 | 202 |
<tr> |
211 | 203 |
<td><a href="#project-shadow">Shadow</a></td> |
212 | 204 |
<td>Simulator</td> |
... | ... |
@@ -513,17 +505,6 @@ meetings around the world.</li> |
513 | 505 |
TorBirdy is Torbutton for Thunderbird and related Mozilla mail clients. |
514 | 506 |
</p> |
515 | 507 |
|
516 |
- <a id="project-flash-proxy"></a> |
|
517 |
- <h3><a href="https://crypto.stanford.edu/flashproxy/">Flash Proxy</a> (<a |
|
518 |
- href="https://gitweb.torproject.org/flashproxy.git">code</a>, <a |
|
519 |
- href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Archived%2FFlashproxy&order=priority">bug |
|
520 |
- tracker</a>)</h3> |
|
521 |
- |
|
522 |
- <p> |
|
523 |
- Pluggable transport using proxies running in web browsers to defeat |
|
524 |
- address-based blocking. |
|
525 |
- </p> |
|
526 |
- |
|
527 | 508 |
<a id="project-shadow"></a> |
528 | 509 |
<h3><a href="http://shadow.github.io/">Shadow</a> (<a |
529 | 510 |
href="https://github.com/shadow">code</a>, <a |
... | ... |
@@ -343,14 +343,6 @@ meetings around the world.</li> |
343 | 343 |
<td>aagbsn</td> |
344 | 344 |
</tr> |
345 | 345 |
|
346 |
- <tr> |
|
347 |
- <td><a href="#project-tor2web">Tor2web</a></td> |
|
348 |
- <td>Client Service</td> |
|
349 |
- <td>Python</td> |
|
350 |
- <td>Heavy</td> |
|
351 |
- <td>evilaliv3, hellais</td> |
|
352 |
- </tr> |
|
353 |
- |
|
354 | 346 |
<tr> |
355 | 347 |
<td><a href="#project-collector">CollecTor</a></td> |
356 | 348 |
<td>Backend Service</td> |
... | ... |
@@ -749,18 +741,6 @@ meetings around the world.</li> |
749 | 741 |
has stopped. |
750 | 742 |
</p> |
751 | 743 |
|
752 |
- <a id="project-tor2web"></a> |
|
753 |
- <h3><a |
|
754 |
- href="https://www.tor2web.org">Tor2web</a> (<a |
|
755 |
- href="https://github.com/globaleaks/tor2web-3.0/wiki">code</a>)</h3> |
|
756 |
- |
|
757 |
- <p> |
|
758 |
- Tor2web allows Internet users to browse websites running in <a |
|
759 |
- href="<page docs/hidden-services>">Tor hidden services</a>. It trades |
|
760 |
- user anonymity for usability by allowing anonymous content to be |
|
761 |
- distributed to non-anonymous users. |
|
762 |
- </p> |
|
763 |
- |
|
764 | 744 |
<a id="project-collector"></a> |
765 | 745 |
<h3><a href="https://collector.torproject.org/">CollecTor</a> |
766 | 746 |
(<a href="https://gitweb.torproject.org/collector.git">code</a>, |
Nick has been leading discussions with core tor folks concerning some GSoC
project ideas. Adding what they've come up with...
https://storm.torproject.org/shared/Xh2gRt-Oy__EaM8_4DAIhrYFMXbOnC09AfLGbHx7TUG
... | ... |
@@ -395,7 +395,14 @@ meetings around the world.</li> |
395 | 395 |
|
396 | 396 |
<p> |
397 | 397 |
<b>Project Ideas:</b><br /> |
398 |
- <i><a href="#improveHiddenServices">Help improve Tor hidden services</a></i> |
|
398 |
+ <i><a href="#improveHiddenServices">Help improve Tor hidden services</a></i><br /> |
|
399 |
+ <i><a href="#torFuzzing">Fuzzing coverage of Tor</a></i><br /> |
|
400 |
+ <i><a href="#relayCryptoParallelism">Relay crypto parallelism</a></i><br /> |
|
401 |
+ <i><a href="#anonymousLocalCountStatistics">Anonymous local count statistics</a></i><br /> |
|
402 |
+ <i><a href="#improveSocks5Variant">Improved SOCKS5 variant</a></i><br /> |
|
403 |
+ <i><a href="#hiddenServiceCryptoParallelism">Hidden service crypto parallelism</a></i><br /> |
|
404 |
+ <i><a href="#supportAllDNS">Support all kinds of DNS in Tor</a></i><br /> |
|
405 |
+ <i><a href="#improveIpv6Support">Improve IPv6 support</a></i> |
|
399 | 406 |
</p> |
400 | 407 |
|
401 | 408 |
<a id="project-torbrowser"></a> |
... | ... |
@@ -835,6 +842,166 @@ ideas. |
835 | 842 |
</p> |
836 | 843 |
</li> |
837 | 844 |
|
845 |
+ <a id="torFuzzing"></a> |
|
846 |
+ <li> |
|
847 |
+ <b>Fuzzing coverage of Tor</b> |
|
848 |
+ <br> |
|
849 |
+ Likely Mentors: <i>Nick (nickm), ahf, teor</i> |
|
850 |
+ <br><br> |
|
851 |
+ <p> |
|
852 |
+Starting in 0.3.0.x, Tor supports a few fuzzing systems to check our |
|
853 |
+code for bugs. But as of now, we only support a few possible entry |
|
854 |
+points to Tor. It would be great to add fuzzing support for more of |
|
855 |
+our codebase -- ideally to include our whole network-facing interface. |
|
856 |
+That way, we could find more bugs in our code faster, and fix them |
|
857 |
+before they can get out of hand. |
|
858 |
+ </p> |
|
859 |
+ |
|
860 |
+ <p> |
|
861 |
+This won't be so easy, however: to fuzz effectively, we need to |
|
862 |
+refactor or mock the target function so that it doesn't change any |
|
863 |
+global state, or verify any signatures, or take too long to run. With |
|
864 |
+lots of our network code, that's not so easy. Make sure you |
|
865 |
+understand how our mocking system works, and what the challenges are, |
|
866 |
+before you apply for this one. |
|
867 |
+ </p> |
|
868 |
+ </li> |
|
869 |
+ |
|
870 |
+ <a id="relayCryptoParallelism"></a> |
|
871 |
+ <li> |
|
872 |
+ <b>Relay crypto parallelism</b> |
|
873 |
+ <br> |
|
874 |
+ Likely Mentors: <i>Isis, Nick (nickm)</i> |
|
875 |
+ <br><br> |
|
876 |
+ <p> |
|
877 |
+Tor relays spend a lot of time encrypting and decrypting relay |
|
878 |
+traffic, doing SHA1 and AES-CTR operations. But right now, all of |
|
879 |
+this is done in the main thread! It would be cool to split this |
|
880 |
+across multiple cores instead. |
|
881 |
+ </p> |
|
882 |
+ |
|
883 |
+ <p> |
|
884 |
+This won't be so easy though. The code today is written to expect |
|
885 |
+immediate results from its encryption operations, so you would need to |
|
886 |
+do some pretty tricky refactoring in order get performance and |
|
887 |
+correctness here. Make sure you understand how circuit crypto is |
|
888 |
+invoked today, and what the challenges are, before you apply for this |
|
889 |
+one. |
|
890 |
+ </p> |
|
891 |
+ |
|
892 |
+ <p> |
|
893 |
+For more information <a href="https://trac.torproject.org/projects/tor/ticket/1749">see its ticket</a>. |
|
894 |
+ </p> |
|
895 |
+ </li> |
|
896 |
+ |
|
897 |
+ <a id="anonymousLocalCountStatistics"></a> |
|
898 |
+ <li> |
|
899 |
+ <b>Anonymous local count statistics</b> |
|
900 |
+ <br> |
|
901 |
+ Likely Mentors: <i>Nick (nickm), teor</i> |
|
902 |
+ <br><br> |
|
903 |
+ <p> |
|
904 |
+There are some places in Tor where we count things (like distinct IPs) |
|
905 |
+to later report anonymized statistics. But if the local Tor instance |
|
906 |
+were compromised, this data would be exposed. There are statistical |
|
907 |
+methods which insteasd allow us to record this data in a way that's |
|
908 |
+already anonymous, before we ever summarize it. Interested? |
|
909 |
+ </p> |
|
910 |
+ |
|
911 |
+ <p> |
|
912 |
+For more information <a href="https://trac.torproject.org/projects/tor/ticket/7532">see its ticket</a>. |
|
913 |
+ </p> |
|
914 |
+ </li> |
|
915 |
+ |
|
916 |
+ <a id="improveSocks5Variant"></a> |
|
917 |
+ <li> |
|
918 |
+ <b>Improved SOCKS5 variant</b> |
|
919 |
+ <br> |
|
920 |
+ Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet)</i> |
|
921 |
+ <br><br> |
|
922 |
+ <p> |
|
923 |
+In proposal 229, we describe a bunch of additional SOCKS extensions |
|
924 |
+that Tor-aware applications could use to get more fine-grained control |
|
925 |
+over how Tor handles their streams. It would be cool to implement |
|
926 |
+this! If there's time remaining, you might want to add support to one |
|
927 |
+or more applications. Or maybe to torsocks? |
|
928 |
+ </p> |
|
929 |
+ |
|
930 |
+ <p> |
|
931 |
+For more information <a href="https://trac.torproject.org/projects/tor/ticket/12456">see its ticket</a>. |
|
932 |
+ </p> |
|
933 |
+ </li> |
|
934 |
+ |
|
935 |
+ <a id="hiddenServiceCryptoParallelism"></a> |
|
936 |
+ <li> |
|
937 |
+ <b>Hidden service crypto parallelism</b> |
|
938 |
+ <br> |
|
939 |
+ Likely Mentors: <i>Nick (nickm), David Goulet (dgoulet)</i> |
|
940 |
+ <br><br> |
|
941 |
+ <p> |
|
942 |
+Hidden services, hidden service clients, hidden service directories, |
|
943 |
+and introduction points all need to do a few public-key operations as |
|
944 |
+they operate. But right now, these operations are all done on the |
|
945 |
+main thread. It would be good to have these run across multiple cores. |
|
946 |
+ </p> |
|
947 |
+ |
|
948 |
+ <p> |
|
949 |
+This could probably be done in a way similar to how we currently hand |
|
950 |
+circuit extension handshakes in onion.c and cpuworker.c, but we'd need |
|
951 |
+to extend the state machine for hidden services to add an additional |
|
952 |
+state. It could help hidden services operate much more efficiently. |
|
953 |
+ </p> |
|
954 |
+ |
|
955 |
+ <p> |
|
956 |
+For more information <a href="https://trac.torproject.org/projects/tor/ticket/13738">see its ticket</a>. |
|
957 |
+ </p> |
|
958 |
+ </li> |
|
959 |
+ |
|
960 |
+ <a id="supportAllDNS"></a> |
|
961 |
+ <li> |
|
962 |
+ <b>Support all kinds of DNS in Tor</b> |
|
963 |
+ <br> |
|
964 |
+ Likely Mentors: <i>Nick (nickm), George (asn)</i> |
|
965 |
+ <br><br> |
|
966 |
+ <p> |
|
967 |
+Right now Tor can query for the kind of DNS information you'd find in |
|
968 |
+A records, AAAA records, and PTR records. It would be neat to be able |
|
969 |
+to support more general DNS queries to allow things like MX loopups, |
|
970 |
+DNSSEC lookups, and so on. We have a design proposal (number 219) for |
|
971 |
+this, but it might need some clean-up. |
|
972 |
+ </p> |
|
973 |
+ |
|
974 |
+ <p> |
|
975 |
+For more information <a href="https://trac.torproject.org/projects/tor/ticket/7829">see its ticket</a>. |
|
976 |
+ </p> |
|
977 |
+ </li> |
|
978 |
+ |
|
979 |
+ <a id="improveIpv6Support"></a> |
|
980 |
+ <li> |
|
981 |
+ <b>Improve IPv6 support</b> |
|
982 |
+ <br> |
|
983 |
+ Likely Mentors: <i>ahf, teor</i> |
|
984 |
+ <br><br> |
|
985 |
+ <p> |
|
986 |
+Tor works over IPv6, but require some manual configuration. |
|
987 |
+Clients and relays could automatically detect IPv6 availability, |
|
988 |
+and configure themselves appropriately. Implementing a |
|
989 |
+"happy eyeballs"-like algorithm is a challenge in an anonymity |
|
990 |
+network: are you up for it? |
|
991 |
+ </p> |
|
992 |
+ |
|
993 |
+ <ul> |
|
994 |
+ <li><a href="https://trac.torproject.org/projects/tor/ticket/6939">Missing IPv6 ORPort reachability check</a></li> |
|
995 |
+ <li><a href="https://trac.torproject.org/projects/tor/ticket/4847">Bridges binding only to an IPv6 address doesn't work</a></li> |
|
996 |
+ <li><a href="https://trac.torproject.org/projects/tor/ticket/5940">Figure out own IPv6 address</a></li> |
|
997 |
+ <li><a href="https://trac.torproject.org/projects/tor/ticket/17011">Teach chutney to verify over IPv6</a></li> |
|
998 |
+ </ul> |
|
999 |
+ |
|
1000 |
+ <p> |
|
1001 |
+For more information <a href="https://trac.torproject.org/projects/tor/ticket/17811">see its ticket</a>. |
|
1002 |
+ </p> |
|
1003 |
+ </li> |
|
1004 |
+ |
|
838 | 1005 |
<a id="feedbackExtension"></a> |
839 | 1006 |
<li> |
840 | 1007 |
<b>Feedback Extension for Tor Browser</b> |
This reverts commit dfca2029f35e01297434d5ba288f89cc312948f2.
... | ... |
@@ -399,7 +399,7 @@ meetings around the world.</li> |
399 | 399 |
</p> |
400 | 400 |
|
401 | 401 |
<a id="project-torbrowser"></a> |
402 |
- <h3>Tor Browser (<a |
|
402 |
+ <h3><a href="<page projects/torbrowser>">Tor Browser</a> (<a |
|
403 | 403 |
href="https://gitweb.torproject.org/tor-browser.git">code</a>, <a |
404 | 404 |
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Applications%2FTor+Browser&component=Applications%2FTorbutton&component=Applications%2FTor+Launcher&component=Applications%2FTor+bundles%2Finstallation&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority">bug |
405 | 405 |
tracker</a>, <a href="https://www.torproject.org/projects/torbrowser/design/">design doc</a>)</h3> |
introduced in commit d886c1470
this breakage was also the reason why commit dfca2029 happened
(which i'll revert next).
The EFF still doesn't know if they have anybody to mentor this summer.
... | ... |
@@ -931,41 +931,6 @@ ideas. |
931 | 931 |
</p> |
932 | 932 |
</li> |
933 | 933 |
|
934 |
- <a id="letsEncryptClient"></a> |
|
935 |
- <li> |
|
936 |
- <b>Expand the OS and Server Support of the Let's Encrypt Client</b> |
|
937 |
- <br> |
|
938 |
- Language: <i>Python, Bash</i> |
|
939 |
- <br> |
|
940 |
- Likely Mentors: <i>Brad Warren (bmw)</i> |
|
941 |
- <br><br> |
|
942 |
- <p> |
|
943 |
- <a href="https://letsencrypt.org/">Let's Encrypt</a> is a free and open |
|
944 |
- certificate authority that allows its users to setup HTTPS on their web |
|
945 |
- server in a matter of seconds. The project uses a new protocol called ACME |
|
946 |
- to automatically perform domain validation and certificate issuance. |
|
947 |
- </p> |
|
948 |
- |
|
949 |
- <p> |
|
950 |
- The Let's Encrypt client currently works on most Unix-like OSes and is |
|
951 |
- able to automatically set up HTTPS on many Apache configurations. The |
|
952 |
- purpose of this project is to expand Let's Encrypt support to new |
|
953 |
- systems. |
|
954 |
- </p> |
|
955 |
- |
|
956 |
- <p> |
|
957 |
- Potential targets include: |
|
958 |
- </p> |
|
959 |
- |
|
960 |
- <ul> |
|
961 |
- <li>Better OS X support including a port or Homebrew package</li> |
|
962 |
- <li>A Let's Encrypt client for Windows / IIS</li> |
|
963 |
- <li>Handling of more obscure Apache configurations</li> |
|
964 |
- <li>Automated HTTPS configuration for other web servers such as Nginx or lighttpd</li> |
|
965 |
- <li>Improved support people using shared hosting who are unable to use the full Let's Encrypt client on their server</li> |
|
966 |
- </ul> |
|
967 |
- </li> |
|
968 |
- |
|
969 | 934 |
<a id="ahmiaSearch"></a> |
970 | 935 |
<li> |
971 | 936 |
<b>Ahmia - Hidden Service Search</b> |
... | ... |
@@ -931,144 +931,6 @@ ideas. |
931 | 931 |
</p> |
932 | 932 |
</li> |
933 | 933 |
|
934 |
- <a id="stegotorus"></a> |
|
935 |
- <li> |
|
936 |
- <b>Make Stegotorus deployment ready</b> |
|
937 |
- <br> |
|
938 |
- Language: <i>C++</i> |
|
939 |
- <br> |
|
940 |
- Likely Mentors: <i>vmon</i> |
|
941 |
- <br><br> |
|
942 |
- <p> |
|
943 |
- <a |
|
944 |
- href="https://github.com/TheTorProject/stegotorus/tree/master/src">Stegotorus</a> |
|
945 |
- is a PT framework which streamline the development stealthier pluggable |
|
946 |
- transport. An HTTP pluggable transport is already implemented in Stegotorus |
|
947 |
- framework and can be used when encrypted payloads are throttled and only |
|
948 |
- ephemeral connections are tolerated. |
|
949 |
- </p> |
|
950 |
- |
|
951 |
- <p> |
|
952 |
- The majority of work on Stegotorus is done and it can be deployed with a relatively minor improvements including: |
|
953 |
- </p> |
|
954 |
- |
|
955 |
- <ul> |
|
956 |
- <li><b>#8098 A config file file for Stegotorus</b> |
|
957 |
- <p> |
|
958 |
- Stegotorus needs many configuration settings specially on the bridge |
|
959 |
- side. This include also the configuration required by each steg module. |
|
960 |
- Currently the configuration is fed to Stegotorus as command line |
|
961 |
- arguments but a file like torrc is needed so all tweaking can be read |
|
962 |
- from there. |
|
963 |
- </p> |
|
964 |
- |
|
965 |
- <p><i> |
|
966 |
- Current Status and work needed to be done: The code for reading the |
|
967 |
- config file is written by SRI but it is not yet used in the Stegotorus |
|
968 |
- to read the config. |
|
969 |
- </i></p> |
|
970 |
- </li> |
|
971 |
- |
|
972 |
- <li><b>#8101 Debugging the transparent proxy</b> |
|
973 |
- <p> |
|
974 |
- Stegotorus http module uses other websites payload to hide and serve |
|
975 |
- censored traffic. As such it needs to decide if the request is |
|
976 |
- genuinely to the auxiliary website, in that case becomes a transparent |
|
977 |
- proxy and serves the website content as requested, or if the request is |
|
978 |
- actually a request to serve censored material which should be delivered |
|
979 |
- to steg modules. |
|
980 |
- </p> |
|
981 |
- |
|
982 |
- <p><i> |
|
983 |
- Current Status: This is completely implemented. However, the transparent proxy sometimes crashes and need to be triaged, debugged and fixed. |
|
984 |
- </i></p> |
|
985 |
- </li> |
|
986 |
- |
|
987 |
- <li><b>#11337 refactoring the steg module code</b> |
|
988 |
- <p> |
|
989 |
- The http steg module code, although not essentials to the core of the |
|
990 |
- Stegotorus. needs some improvement and clean up. The solution is to |
|
991 |
- refactor the steg modules as children of FileStegMod. |
|
992 |
- </p> |
|
993 |
- |
|
994 |
- <p><i> |
|
995 |
- Current status and work needed to be done: This has already been done |
|
996 |
- but still needs testing and refactoring before it can be reliably merge |
|
997 |
- to the master branch. |
|
998 |
- </i></p> |
|
999 |
- </li> |
|
1000 |
- |
|
1001 |
- <li><b>#8089 Adding Elligator to Stegotorus handshake and test</b> |
|
1002 |
- <p> |
|
1003 |
- The current Stegotorus handshake is distinguishable from random byte |
|
1004 |
- string, which can be used to flag and detect Stegotorus traffic |
|
1005 |
- deterministically and need to be implemented similar to |
|
1006 |
- ScrambleSuite. Also because the capacity of client to server channel |
|
1007 |
- might be slim depending on the choice of steg module it is desirable |
|
1008 |
- to be implemented using Elliptic curve crypto. Hence, Elligator |
|
1009 |
- protocol is ideal solution for this situation. All we need is to replace Stegotorus handshake by Elligator. |
|
1010 |
- </p> |
|
1011 |
- |
|
1012 |
- <p><i> |
|
1013 |
- Current Status and work needed to be done: Elligator handshake code is |
|
1014 |
- included in stegotorus code base, it is only needed to be called by |
|
1015 |
- instead of the current handshake and be tested. |
|
1016 |
- </i></p> |
|
1017 |
- </li> |
|
1018 |
- |
|
1019 |
- <li><b>Make Stegotorus memory safe by using shared pointers</b> |
|
1020 |
- <p> |
|
1021 |
- Stegotorus has large code base and it is not written in a memory safe |
|
1022 |
- languages. To facilitate its audit, we need to replace (almost all) use |
|
1023 |
- of pointers to shared pointers. |
|
1024 |
- </p> |
|
1025 |
- |
|
1026 |
- <p><i> |
|
1027 |
- Current Status: No progress has not been done. |
|
1028 |
- </i></p> |
|
1029 |
- </li> |
|
1030 |
- |
|
1031 |
- <li><b>Security Audit and writing more unit test</b> |
|
1032 |
- <p> |
|
1033 |
- To be able to deploy Stegotorus for real world use we need to audit the |
|
1034 |
- code and write more unit test covering new aspects of the Stegotorus |
|
1035 |
- (new http transport, proxy server, Elligator handshake) |
|
1036 |
- </p> |
|
1037 |
- |
|
1038 |
- <p><i> |
|
1039 |
- Current Status: No progress has been done. |
|
1040 |
- </i></p> |
|
1041 |
- </li> |
|
1042 |
- |
|
1043 |
- <li><b>SRI branch merging</b> |
|
1044 |
- <p> |
|
1045 |
- Stegotorus has been forked from the initial development from SRI. Now |
|
1046 |
- that SRI is hosting Stegotorus publicly it is desirable to merge the |
|
1047 |
- two branches so we can benefit from both developments. |
|
1048 |
- </p> |
|
1049 |
- |
|
1050 |
- <p><i> |
|
1051 |
- Current Status: No progress has been done. |
|
1052 |
- </i></p> |
|
1053 |
- </li> |
|
1054 |
- |
|
1055 |
- <li><b>#8099 deterministic build</b> |
|
1056 |
- <p> |
|
1057 |
- To make deterministic build possible we need to build many of |
|
1058 |
- Stegotorus dependency from scratch. Boost library is a a huge |
|
1059 |
- dependency for Stegotorus to access the file system. As we are only |
|
1060 |
- planning to deploy Stegotorus bridges on Linux machines we can simplify |
|
1061 |
- such access without that dependency. By dropping such dependency, it |
|
1062 |
- should be straight forward to have deterministic build for Stegotorus. |
|
1063 |
- </p> |
|
1064 |
- |
|
1065 |
- <p><i> |
|
1066 |
- Current Status: No progress has been done. |
|
1067 |
- </i></p> |
|
1068 |
- </li> |
|
1069 |
- </ul> |
|
1070 |
- </li> |
|
1071 |
- |
|
1072 | 934 |
<a id="letsEncryptClient"></a> |
1073 | 935 |
<li> |
1074 | 936 |
<b>Expand the OS and Server Support of the Let's Encrypt Client</b> |
Didn't hear back if it was still relevant.
... | ... |
@@ -1104,46 +1104,6 @@ ideas. |
1104 | 1104 |
</ul> |
1105 | 1105 |
</li> |
1106 | 1106 |
|
1107 |
- <a id="ipHijacking"></a> |
|
1108 |
- <li> |
|
1109 |
- <b>IP hijacking detection for the Tor Network</b> |
|
1110 |
- <br> |
|
1111 |
- Likely Mentors: <i>Aaron Gibson (aagbsn)</i> |
|
1112 |
- <br><br> |
|
1113 |
- <p> |
|
1114 |
- <a href="https://en.wikipedia.org/wiki/IP_hijacking">IP hijacking</a> |
|
1115 |
- occurs when a bad actor creates false routing information to redirect |
|
1116 |
- Internet traffic to or through themselves. This activity is straightforward |
|
1117 |
- to detect, because the Internet routing tables are public information, but |
|
1118 |
- currently there are no public services that monitor the Tor network. The |
|
1119 |
- Tor Network is a dynamic set of relays, so monitoring must be Tor-aware in |
|
1120 |
- order to keep the set of monitored relays accurate. Additionally, consensus |
|
1121 |
- archives and historical Internet routing table snapshots are publicly |
|
1122 |
- available, and this analysis can be performed retroactively. |
|
1123 |
- </p> |
|
1124 |
- |
|
1125 |
- <p> |
|
1126 |
- The implications of IP hijacking are that Tor traffic can be redirected |
|
1127 |
- through a network that an attacker controls, even if the attacker does not |
|
1128 |
- normally have this capability - i.e. they are not in the network path. For |
|
1129 |
- example, an adversary could hijack the prefix of a Tor Guard relay, in |
|
1130 |
- order to learn who its clients are, or hijack a Tor Exit relay to tamper |
|
1131 |
- with requests or name resolution. |
|
1132 |
- </p> |
|
1133 |
- |
|
1134 |
- <p> |
|
1135 |
- This project comprises building a service that compares network prefixes of |
|
1136 |
- relays in the consensus with present and historic routing table snapshots |
|
1137 |
- from looking glass services such as <a |
|
1138 |
- href="http://routeviews.org">Routeviews</a>, or aggregators such as <a |
|
1139 |
- href="https://bgpstream.caida.org">Caida BGPStream</a> and then issues |
|
1140 |
- email alerts to the contact-info in the relay descriptor and a mailing |
|
1141 |
- list. Network operators are responsive to route injections, and these |
|
1142 |
- alerts can be used to notify network operators to take immediate action, as |
|
1143 |
- well as collect information about the occurrence of these type of attacks. |
|
1144 |
- </p> |
|
1145 |
- </li> |
|
1146 |
- |
|
1147 | 1107 |
<a id="ahmiaSearch"></a> |
1148 | 1108 |
<li> |
1149 | 1109 |
<b>Ahmia - Hidden Service Search</b> |
Philipp has graciously said he'd be willing to act as the backup mentor for
this.
... | ... |
@@ -904,7 +904,7 @@ ideas. |
904 | 904 |
<br> |
905 | 905 |
Language: <i>Python</i> |
906 | 906 |
<br> |
907 |
- Likely Mentors: <i>Damian Johnson (atagar)</i> |
|
907 |
+ Likely Mentors: <i>Damian Johnson (atagar), Philipp Winter (phw)</i> |
|
908 | 908 |
<p> |
909 | 909 |
<a href="https://stem.torproject.org/">Stem</a> is a Python library for working with tor. With it you can build applications on tor as well as learn information about the relay network. This project concerns this second capability. |
910 | 910 |
</p> |
Presently our site shows...
../$dir/$lang/$base.wml), but that doesn't exist.";};}:>">Tor Browser (code, bug tracker, design doc)
Guess the tor browser page was dropped or moved.
... | ... |
@@ -399,7 +399,7 @@ meetings around the world.</li> |
399 | 399 |
</p> |
400 | 400 |
|
401 | 401 |
<a id="project-torbrowser"></a> |
402 |
- <h3><a href="<page projects/torbrowser>">Tor Browser</a> (<a |
|
402 |
+ <h3>Tor Browser (<a |
|
403 | 403 |
href="https://gitweb.torproject.org/tor-browser.git">code</a>, <a |
404 | 404 |
href="https://trac.torproject.org/projects/tor/query?status=accepted&status=assigned&status=needs_review&status=new&status=reopened&component=Applications%2FTor+Browser&component=Applications%2FTorbutton&component=Applications%2FTor+Launcher&component=Applications%2FTor+bundles%2Finstallation&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=milestone&order=priority">bug |
405 | 405 |
tracker</a>, <a href="https://www.torproject.org/projects/torbrowser/design/">design doc</a>)</h3> |
Quick pass taking a peek at commit activity. Also dropping Obfsproxy from the
table since it no longer had a working link to a description below (suspect we
tried to remove it but missed the table entry).
... | ... |
@@ -139,7 +139,7 @@ meetings around the world.</li> |
139 | 139 |
<td><a href="#project-httpseverywhere">HTTPS Everywhere</a></td> |
140 | 140 |
<td>Browser Add-on</td> |
141 | 141 |
<td>Javascript</td> |
142 |
- <td>Heavy</td> |
|
142 |
+ <td>Moderate</td> |
|
143 | 143 |
<td>pde, mikeperry</td> |
144 | 144 |
</tr> |
145 | 145 |
|
... | ... |
@@ -147,7 +147,7 @@ meetings around the world.</li> |
147 | 147 |
<td><a href="#project-nyx">Nyx</a></td> |
148 | 148 |
<td>User Interface</td> |
149 | 149 |
<td>Python, Curses</td> |
150 |
- <td>Heavy</td> |
|
150 |
+ <td>Moderate</td> |
|
151 | 151 |
<td>atagar</td> |
152 | 152 |
</tr> |
153 | 153 |
|
... | ... |
@@ -199,14 +199,6 @@ meetings around the world.</li> |
199 | 199 |
<td>sukhe</td> |
200 | 200 |
</tr> |
201 | 201 |
|
202 |
- <tr> |
|
203 |
- <td><a href="#project-obfsproxy">Obfsproxy</a></td> |
|
204 |
- <td>Client Add-on</td> |
|
205 |
- <td>Python</td> |
|
206 |
- <td>None</td> |
|
207 |
- <td>asn</td> |
|
208 |
- </tr> |
|
209 |
- |
|
210 | 202 |
<tr> |
211 | 203 |
<td><a href="#project-flash-proxy">Flash Proxy</a></td> |
212 | 204 |
<td>Client Add-on</td> |
... | ... |
@@ -219,7 +211,7 @@ meetings around the world.</li> |
219 | 211 |
<td><a href="#project-shadow">Shadow</a></td> |
220 | 212 |
<td>Simulator</td> |
221 | 213 |
<td>C, Python</td> |
222 |
- <td>Heavy</td> |
|
214 |
+ <td>Moderate</td> |
|
223 | 215 |
<td>robgjansen</td> |
224 | 216 |
</tr> |
225 | 217 |
|
... | ... |
@@ -228,7 +220,7 @@ meetings around the world.</li> |
228 | 220 |
<td>Simulator</td> |
229 | 221 |
<td>Python</td> |
230 | 222 |
<td>Light</td> |
231 |
- <td>nickm</td> |
|
223 |
+ <td>teor</td> |
|
232 | 224 |
</tr> |
233 | 225 |
|
234 | 226 |
<tr> |
... | ... |
@@ -243,15 +235,23 @@ meetings around the world.</li> |
243 | 235 |
<td><a href="#project-txtorcon">Txtorcon</a></td> |
244 | 236 |
<td>Library</td> |
245 | 237 |
<td>Python, Twisted</td> |
246 |
- <td>Light</td> |
|
238 |
+ <td>Moderate</td> |
|
247 | 239 |
<td>meejah</td> |
248 | 240 |
</tr> |
249 | 241 |
|
242 |
+ <tr> |
|
243 |
+ <td><a href="#project-metrics-lib">metrics-lib</a></td> |
|
244 |
+ <td>Library</td> |
|
245 |
+ <td>Java</td> |
|
246 |
+ <td>Moderate</td> |
|
247 |
+ <td>karsten, iwakeh</td> |
|
248 |
+ </tr> |
|
249 |
+ |
|
250 | 250 |
<tr> |
251 | 251 |
<td><a href="#project-metrics">Metrics</a></td> |
252 | 252 |
<td>Client Service</td> |
253 | 253 |
<td>Java</td> |
254 |
- <td>Moderate</td> |
|
254 |
+ <td>Heavy</td> |
|
255 | 255 |
<td>karsten, iwakeh</td> |
256 | 256 |
</tr> |
257 | 257 |
|
... | ... |
@@ -259,7 +259,7 @@ meetings around the world.</li> |
259 | 259 |
<td><a href="#project-atlas">Atlas</a></td> |
260 | 260 |
<td>Client Service</td> |
261 | 261 |
<td>JavaScript</td> |
262 |
- <td>Moderate</td> |
|
262 |
+ <td>Light</td> |
|
263 | 263 |
<td>irl</td> |