Added gsoc data from goodell.
Jacob Appelbaum commited on 2008-03-14 02:50:57
Zeige 1 geänderte Dateien mit 55 Einfügungen und 0 Löschungen.
- en/volunteer.wml 53c7e32ad..3e281bca7
| ... | ... |
@@ -864,6 +864,61 @@ href="http://anonymityanywhere.com/incognito/">Incognito LiveCD</a> |
| 864 | 864 |
easier to maintain, improve, and document? |
| 865 | 865 |
</li> |
| 866 | 866 |
|
| 867 |
+<li> |
|
| 868 |
+<b>Rework and extend Blossom</b> |
|
| 869 |
+<br /> |
|
| 870 |
+Priority: <i>Medium</i> |
|
| 871 |
+<br /> |
|
| 872 |
+Effort Level: <i>Medium to High</i> |
|
| 873 |
+<br /> |
|
| 874 |
+Skill Level: <i>Medium to High</i> |
|
| 875 |
+<br /> |
|
| 876 |
+Likely Mentors: <i>Goodell</i> |
|
| 877 |
+<br /> |
|
| 878 |
+Rework and extend Blossom (a tool for monitoring and |
|
| 879 |
+selecting appropriate Tor circuits based upon exit node requirements |
|
| 880 |
+specified by the user) to gather data in a self-contained way, with |
|
| 881 |
+parameters easily configurable by the user. Blossom is presently |
|
| 882 |
+implemented as a single Python script that interfaces with Tor using the |
|
| 883 |
+Controller interface and depends upon metadata about Tor nodes obtained |
|
| 884 |
+via external processes, such as a webpage indicating status of the nodes |
|
| 885 |
+plus publically available data from DNS, whois, etc. This project has |
|
| 886 |
+two parts: (1) Determine which additional metadata may be useful and |
|
| 887 |
+rework Blossom so that it cleanly obtains the metadata on its own rather |
|
| 888 |
+than depend upon external scripts (this may, for example, involve |
|
| 889 |
+additional threads or inter-process communication), and (2) develop a |
|
| 890 |
+means by which the user can easily configure Blossom, starting with a |
|
| 891 |
+configuration file and possibly working up to a web configuration engine. |
|
| 892 |
+</li> |
|
| 893 |
+ |
|
| 894 |
+<li> |
|
| 895 |
+<b>Improve Blossom: Allow users to qualitatively describe exit nodes they desire</b> |
|
| 896 |
+<br /> |
|
| 897 |
+Priority: <i>Low</i> |
|
| 898 |
+<br /> |
|
| 899 |
+Effort Level: <i>Medium</i> |
|
| 900 |
+<br /> |
|
| 901 |
+Skill Level: <i>Medium</i> |
|
| 902 |
+<br /> |
|
| 903 |
+Likely Mentors: <i>Goodell</i> |
|
| 904 |
+<br /> |
|
| 905 |
+Develop and implement a means of affording Blossom |
|
| 906 |
+users the ability to qualitatively describe the exit node that they |
|
| 907 |
+want. The Internet is an inconsistent place: some Tor exit nodes see |
|
| 908 |
+the world differently than others. As presently implemented, Blossom (a |
|
| 909 |
+tool for monitoring and selecting appropriate Tor circuits based upon |
|
| 910 |
+exit node requirements specified by the user) lacks a sufficiently rich |
|
| 911 |
+language to describe how the different vantage points are different. |
|
| 912 |
+For example, some exit nodes may have an upstream network that filters |
|
| 913 |
+certain kinds of traffic or certain websites. Other exit nodes may |
|
| 914 |
+provide access to special content as a result of their location, perhaps |
|
| 915 |
+as a result of discrimination on the part of the content providers |
|
| 916 |
+themselves. This project has two parts: (1) develop a language for |
|
| 917 |
+describing characteristics of networks in which exit nodes reside, and |
|
| 918 |
+(2) incorporate this language into Blossom so that users can select Tor |
|
| 919 |
+paths based upon the description. |
|
| 920 |
+</li> |
|
| 921 |
+ |
|
| 867 | 922 |
<li> |
| 868 | 923 |
<b>Bring up new ideas!</b> |
| 869 | 924 |
<br /> |
| 870 | 925 |