Andrew Lewman commited on 2010-11-09 16:35:28
Zeige 3 geänderte Dateien mit 34 Einfügungen und 29 Löschungen.
... | ... |
@@ -17,7 +17,7 @@ |
17 | 17 |
Systems; such as OS X 10.2, OS X 10.3, Windows XP, Windows 7, IRIX, |
18 | 18 |
Redhat, CentOS, Fedora, Debian, etc. A number of service providers |
19 | 19 |
have an abundance of bandwidth capacity, but need hardware in order |
20 |
- donate it to us.</p> |
|
20 |
+ to donate it to us.</p> |
|
21 | 21 |
|
22 | 22 |
<p>By donating hardware, you're joining our many <a href="<page |
23 | 23 |
about/sponsors>">sponsors</a> in providing online privacy and anonymity. If |
... | ... |
@@ -49,16 +49,19 @@ |
49 | 49 |
<a id="Advocacy"></a> |
50 | 50 |
<h2><a class="anchor" href="#Advocacy">Advocacy</a></h2> |
51 | 51 |
<ol> |
52 |
- <li>Create a <a href="https://trac.torproject.org/projects/tor/wiki/CommunityLogos">community logo</a> under a Creative Commons license that all can use and modify</li> |
|
53 |
- <li>Create a presentation that can be used for various user group meetings around the world</li> |
|
52 |
+ <li>Create a <a |
|
53 |
+href="https://trac.torproject.org/projects/tor/wiki/CommunityLogos">community |
|
54 |
+logo</a> under a Creative Commons license that all can use and modify.</li> |
|
55 |
+ <li>Create a presentation that can be used for various user group |
|
56 |
+meetings around the world.</li> |
|
54 | 57 |
<li>Create a video about the positive uses of Tor, what Tor is, |
55 | 58 |
or how to use it. Some have already started on <a |
56 | 59 |
href="http://media.torproject.org/video/">Tor's Media server</a>, |
57 | 60 |
<a |
58 | 61 |
href="http://www.howcast.com/videos/90601-How-To-Circumvent-an-Internet-Proxy">Howcast</a>, |
59 |
- and <a href="http://www.youtube.com/thetorproject">Youtube</a>.</li> |
|
62 |
+ and <a href="http://www.youtube.com/thetorproject">YouTube</a>.</li> |
|
60 | 63 |
<li>Create a poster, or a set of posters, around a theme, |
61 |
- such as "Tor for Freedom!"</li> |
|
64 |
+ such as "Tor for Freedom!".</li> |
|
62 | 65 |
</ol> |
63 | 66 |
|
64 | 67 |
<a id="Coding"></a> |
... | ... |
@@ -101,7 +104,7 @@ |
101 | 104 |
using a Tor Browser Bundle on Windows, Mac OS X, or Linux. Developing |
102 | 105 |
ways to stop, counter, or remove these traces is a final step.</p> |
103 | 106 |
<p>Students should be familiar with operating system analysis, |
104 |
- application development on one or preferably Windows, Linux, |
|
107 |
+ application development on one or preferably all of Windows, Linux, |
|
105 | 108 |
and Mac OS X, and be comfortable with C/C++ and shell scripting.</p> |
106 | 109 |
<p>If you would like to help extend or do security auditing for |
107 | 110 |
TBB, please contact Erinn.</p> |
... | ... |
@@ -151,7 +154,7 @@ |
151 | 154 |
But Tor still needs better mechanisms for some parts of its |
152 | 155 |
anti-censorship design.</p> |
153 | 156 |
<p>One huge category of work is adding features to our <a |
154 |
- href="http://gitweb.torproject.org//bridgedb.git?a=tree">bridgedb</a> |
|
157 |
+ href="http://gitweb.torproject.org/bridgedb.git?a=tree">BridgeDB</a> |
|
155 | 158 |
service (Python). Tor aims to give out <a href="<page docs/bridges>">bridge |
156 | 159 |
relay addresses</a> to users that can't reach the Tor network |
157 | 160 |
directly, but there's an arms race between algorithms for distributing |
... | ... |
@@ -189,14 +192,15 @@ |
189 | 192 |
to be informed. For example, if the user is trying to set up his Tor as a |
190 | 193 |
relay and Tor decides that its ports are not reachable from outside |
191 | 194 |
the user's network, we should alert the user. Currently, all the user |
192 |
- gets is a couple log messages in Vidalia's 'message log' window, which they |
|
195 |
+ gets is a couple of log messages in Vidalia's 'message log' window, which they |
|
193 | 196 |
likely never see since they don't receive a notification that something |
194 | 197 |
has gone wrong. Even if the user does actually look at the message log, |
195 | 198 |
most of the messages make little sense to the novice user.</p> |
196 |
- <p>Tor has the ability to inform Vidalia of many such status changes, and |
|
197 |
- we recently implemented support for a couple of these events. Still, |
|
198 |
- there are many more status events the user should be informed of and we |
|
199 |
- need a better UI for actually displaying them to the user.</p> |
|
199 |
+ <p>Tor has the ability to inform Vidalia of many such status |
|
200 |
+ changes, and we recently implemented support for a couple of these |
|
201 |
+ events. Still, there are many more status events which the user should |
|
202 |
+ be informed of, and we need a better UI for actually displaying them |
|
203 |
+ to the user.</p> |
|
200 | 204 |
<p>The goal of this project then is to design and implement a UI for |
201 | 205 |
displaying Tor status events to the user. For example, we might put a |
202 | 206 |
little badge on Vidalia's tray icon that alerts the user to new status |
... | ... |
@@ -206,7 +210,7 @@ |
206 | 210 |
the user. Of course, this is just an example and one is free to |
207 | 211 |
suggest another approach.</p> |
208 | 212 |
<p>A person undertaking this project should have good UI design and layout |
209 |
- and some C++ development experience. Previous experience with Qt and |
|
213 |
+ skills and some C++ development experience. Previous experience with Qt and |
|
210 | 214 |
Qt's Designer will be very helpful, but are not required. Some |
211 | 215 |
English writing ability will also be useful, since this project will |
212 | 216 |
likely involve writing small amounts of help documentation that should |
... | ... |
@@ -224,11 +228,12 @@ |
224 | 228 |
Skill Level: <i>Medium</i> |
225 | 229 |
<br> |
226 | 230 |
Likely Mentors: <i>Nick, Erinn</i> |
227 |
- <p>Tor needs to be far more tested. This is a multi-part effort. To start |
|
228 |
- with, our unit test coverage should rise substantially, especially in |
|
229 |
- the areas outside the utility functions. This will require significant |
|
230 |
- refactoring of some parts of Tor, in order to dissociate as much logic |
|
231 |
- as possible from globals.</p> |
|
231 |
+ <p>Tor needs to be tested far more thoroughly. This is a |
|
232 |
+ multi-part effort. To start with, our unit test coverage should |
|
233 |
+ rise substantially, especially in the areas outside the utility |
|
234 |
+ functions. This will require significant refactoring of some parts |
|
235 |
+ of Tor, in order to dissociate as much logic as possible from |
|
236 |
+ globals.</p> |
|
232 | 237 |
<p>Additionally, we need to automate our performance testing. We've got |
233 | 238 |
buildbot to automate our regular integration and compile testing already |
234 | 239 |
(though we need somebody to set it up on Windows), |
... | ... |
@@ -253,8 +258,8 @@ |
253 | 258 |
environments. The first step is to get a handle on the current state of |
254 | 259 |
the project in which you are interested in helping; <a |
255 | 260 |
href="http://github.com/brl/JTor">Tor for Java</a>, |
256 |
- <a href="https://svn.torproject.org/svn/projects/android/trunk/">Android/Orbot</a> |
|
257 |
- , or <a href="<page docs/N900>">Tor for Maemo</a>. Check out the |
|
261 |
+ <a href="https://svn.torproject.org/svn/projects/android/trunk/">Android/Orbot</a>, |
|
262 |
+ or <a href="<page docs/N900>">Tor for Maemo</a>. Check out the |
|
258 | 263 |
repository and familiarize yourself |
259 | 264 |
with the source code. Further, support for requesting or even providing |
260 | 265 |
Tor hidden services would be neat, but not required.</p> |
... | ... |
@@ -282,16 +287,16 @@ |
282 | 287 |
connected, quality of connection and so on. The "Tether Wifi" |
283 | 288 |
Android application is a good model to follow in how it shows |
284 | 289 |
a realtime count of bytes transferred as well as notifications |
285 |
- when wifi client connect. In addition, better display/handling |
|
290 |
+ when wifi clients connect. In addition, better display/handling |
|
286 | 291 |
of Tor system/error messages would also be very helpful. Finally, |
287 | 292 |
the addition of a wizard or tutorial walkthrough for novice |
288 |
- users to explain to them exactly what or what is not anonymized |
|
293 |
+ users to explain to them exactly what is and what is not anonymized |
|
289 | 294 |
or protected would greatly improve the likelihood they will use |
290 | 295 |
Orbot correctly.</p> |
291 | 296 |
|
292 | 297 |
<p><b>Android Java OS/Core app work:</b> Better system-wide |
293 |
- indicator either via the notification bar, "Toast" pop-up dialogs |
|
294 |
- or some other indicator that an application's traffic is indeed |
|
298 |
+ indication, either via the notification bar, "Toast" pop-up dialogs |
|
299 |
+ or some other indicator, that an application's traffic is indeed |
|
295 | 300 |
moving through Orbot/Tor. For instance, right now you need to |
296 | 301 |
first go to a torcheck web service to ensure your browser is |
297 | 302 |
routing via Tor. Orbot should be able to notify you that circuits |
... | ... |
@@ -300,8 +305,8 @@ |
300 | 305 |
|
301 | 306 |
<p><b>Android Java Library/Community Outreach work:</b> We need |
302 | 307 |
to package a simple library for use with third-party application |
303 |
- to easily enable them to support "Torification" on non-root |
|
304 |
- devices (aka w/o transparent proxying). This library should |
|
308 |
+ to easily enable them to support "Torification" on non-rooted |
|
309 |
+ devices (i.e. w/o transparent proxying). This library should |
|
305 | 310 |
include a wrapper for the Apache HTTPClient library, a utility |
306 | 311 |
class for detecting the state of Orbot connectivity, and other |
307 | 312 |
relevant/useful things an Android app might need to anonymize |
... | ... |
@@ -316,7 +321,7 @@ |
316 | 321 |
Android hardware, or on mobile networks. It should be noted, |
317 | 322 |
that even without optimization, Tor is handling the mobile |
318 | 323 |
network environment very well, automatically detecting change |
319 |
- in IP addresses, reconnecting circuits, etc across switching |
|
324 |
+ in IP addresses, reconnecting circuits, etc. across switching |
|
320 | 325 |
from 2G to 3G to Wifi, and so forth.</p> |
321 | 326 |
</li> |
322 | 327 |
|
... | ... |
@@ -583,7 +588,7 @@ |
583 | 588 |
<li>Tor 0.1.1.x and later include support for hardware crypto |
584 | 589 |
accelerators via OpenSSL. It has been lightly tested and is |
585 | 590 |
possibly very buggy. We're looking for more rigorous testing, |
586 |
- performance analysis, and optimally, code fixes to openssl and |
|
591 |
+ performance analysis, and optimally, code fixes to OpenSSL and |
|
587 | 592 |
Tor if needed.</li> |
588 | 593 |
|
589 | 594 |
<li>Perform a security analysis of Tor with <a |
... | ... |
@@ -47,7 +47,7 @@ Tor's resource utilization and state.</p> |
47 | 47 |
<div class="name"><a href="<wiki>projects/TorBulkExitlist">TorBEL</a></div> |
48 | 48 |
<p>The Tor Bulk Exitlist is a service others can |
49 | 49 |
query to determine if an IP is a tor exit node or not, |
50 |
-and if so, on which tcp ports it allows traffic.</p> |
|
50 |
+and if so, on which TCP ports it allows traffic.</p> |
|
51 | 51 |
</td> |
52 | 52 |
<td> |
53 | 53 |
<div class="name"><a href="<wiki>projects/TorCheck">Tor Check</a></div> |
54 | 54 |