three more from nick. we're starting to get some duplicate topics. (e6ca7fae8)

en/volunteer.wml

...	...	@@ -93,6 +93,46 @@ Farsi translations, for the many Tor users in censored areas.</li>
93	93	<h2><a class="anchor" href="#Projects">Good Coding Projects</a></h2>
94	94	<ol>
95	95
	96	+<li>
	97	+Tor needs even better censorship resistance mechanisms. There are
	98	+several mechanisms that can help. Tor should be able listen on multiple
	99	+addresses and ports, and allow clients to connect to all of them.
	100	+Tor should be able to appear like a webserver (HTTP or HTTPS) when
	101	+contacted by port-scanning tools.
	102	+</li>
	103	+
	104	+<li>
	105	+Tor should make better use of the more recent features of Niels Provos's
	106	+Libevent library. Libevent already provides HTTP and socket buffers;
	107	+Tor's code for those could be replaced. We'll need to improve libevent's
	108	+code as needed; particularly, to add good openssl support on top of
	109	+libevent's buffer abstraction.
	110	+</li>
	111	+
	112	+<li>
	113	+Tor should possibly measure bandwidth in a distributed way, as in the
	114	+<a href="http://freehaven.net/anonbib/">"A Tuneup for Tor"</a> paper
	115	+by Snader and Borisov. A student could use current testing code to
	116	+double-check this paper's findings and verify the extent to which they
	117	+dovetail with Tor in the wild, and determine good ways to incorporate them
	118	+into the Tor network without adding undesirable n^2 traffic properties
	119	+at the directory authorities.
	120	+</li>
	121	+
	122	+<li>
	123	+Tor needs to be far more tested. This is a multi-part effort. To start
	124	+with, our unit test coverage should rise substantially, especially in
	125	+the areas outside the utility functions. This will require significant
	126	+refactoring of some parts of Tor, in order to dissociate as much logic
	127	+as possible from globals.<br />
	128	+Additionally, we need to automate our performance testing. We've got
	129	+buildbot to automate our regular integration and compile testing already,
	130	+but we need to get our network simulation tests (as built in torflow)
	131	+updated for more recent versions of Tor, and designed to launch a test
	132	+network either on a single machine, or across several, so we can test
	133	+changes in performance on machines in different roles automatically.
	134	+</li>
	135	+
96	136	<li>
97	137	Reanimate one of the approaches to implement a Tor client in Java,
98	138	e.g. the <a href="http://onioncoffee.sourceforge.net/">OnionCoffee
99	139

tor-webwml.git