new-contribute is now valid xhtml 1.1
Andrew Lewman commited on 2005-06-14 05:55:30
Zeige 1 geänderte Dateien mit 14 Einfügungen und 15 Löschungen.
- new-contribute.html 19777e87f..4cd005e90
| ... | ... |
@@ -1,5 +1,4 @@ |
| 1 |
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" |
|
| 2 |
-"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> |
|
| 1 |
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> |
|
| 3 | 2 |
|
| 4 | 3 |
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> |
| 5 | 4 |
<head> |
| ... | ... |
@@ -69,26 +68,26 @@ |
| 69 | 68 |
<li>Change server descriptors to declare log level.</li> |
| 70 | 69 |
<li>Add in support for clients to avoid servers that are too loggy based upon user configuration of acceptable log level.</li> |
| 71 | 70 |
<li>Separate node discovery from routing to allow neat extensions. [Goodell?]</li> |
| 72 |
-<ul> |
|
| 71 |
+<li><ul> |
|
| 73 | 72 |
<li>Add SetServerStatus control event to adjust verified/running status of nodes.</li> |
| 74 | 73 |
<li>Add NoDownload config option to prevent regular directory downloads from happening.</li> |
| 75 |
-</ul> |
|
| 74 |
+</ul></li> |
|
| 76 | 75 |
<li>Choosing exit node by meta-data, e.g. country.</li> |
| 77 | 76 |
<li>Use cpuworker for more heavy lifting.</li> |
| 78 |
-<ul> |
|
| 77 |
+<li><ul> |
|
| 79 | 78 |
<li>Signing (and verifying) hidserv descriptors</li> |
| 80 | 79 |
<li>Signing (and verifying) intro/rend requests</li> |
| 81 | 80 |
<li>Signing (and verifying) router descriptors</li> |
| 82 | 81 |
<li>Signing (and verifying) directories</li> |
| 83 | 82 |
<li>Doing TLS handshake (this is very hard to separate out, though)</li> |
| 84 |
-</ul> |
|
| 83 |
+</ul></li> |
|
| 85 | 84 |
<li>Buffer size pool: allocate a maximum size for all buffers, not a maximum size for each buffer. So we don't have to give up as quickly (and kill the thickpipe!) when there's congestion.</li> |
| 86 | 85 |
<li>Add alternative versions of crypto.c and tortls.c to use libnss or libgcrypt+gnutls.</li> |
| 87 | 86 |
<li>Implement a way to stop falling back to forbidden ports when FascistFirewall blocks all good dirservers, if there is already a good, cached directory locally.</li> |
| 88 | 87 |
<li>Extend our NSIS-based windows installer to include FreeCap and/or Privoxy.</li> |
| 89 | 88 |
<li>Develop a way to handle OS X installation and uninstallation.</li> |
| 90 | 89 |
<li>Develop a GUI or other controller program, to do configuration, etc. See our control specification for details, and the rudimentary demonstration Python control script. </li> |
| 91 |
-<ul> |
|
| 90 |
+<li><ul> |
|
| 92 | 91 |
<li>Design an interface for the control program. You can use any license you want, but we'd recommend 3-clause BSD or maybe GPL; and we can only help out if your license conforms to the DFSG.</li> |
| 93 | 92 |
<li>Periodically people running servers tells us they want to have one |
| 94 | 93 |
BandwidthRate during some part of the day, and a different |
| ... | ... |
@@ -99,7 +98,7 @@ |
| 99 | 98 |
until appropriate times and then do its tweak (that's probably more |
| 100 | 99 |
portable). Can somebody write one for us and we'll put it inside |
| 101 | 100 |
tor/contrib/?</li> |
| 102 |
-</ul> |
|
| 101 |
+</ul></li> |
|
| 103 | 102 |
<li>Develop a way to become a Windows NT service. </li> |
| 104 | 103 |
<li>Develop a systray app for Tor under MS Windows (all versions). </li> |
| 105 | 104 |
<li>Integrate a good (portable, fast, clean, BSD-free) asynchronous DNS library so we don't have to keep forking DNS worker threads to do gethostbyname.</li> |
| ... | ... |
@@ -128,11 +127,11 @@ |
| 128 | 127 |
<ul> |
| 129 | 128 |
<li>Test out why some of our tor servers have dns resolvers that resolve |
| 130 | 129 |
unknown addresses to 127.0.0.1.</li> |
| 131 |
-<ul> |
|
| 130 |
+<li><ul> |
|
| 132 | 131 |
<li>Identify the servers that experience this issue. </li> |
| 133 | 132 |
<li>Identify how to cause and repair the issue in BIND, DJBDNS, or |
| 134 | 133 |
whatever daemon the misconfigured servers use.</li> |
| 135 |
-</ul> |
|
| 134 |
+</ul></li> |
|
| 136 | 135 |
<li>Figure out how to setup web proxy gateways to let normal people |
| 137 | 136 |
browse hidden services. (This has been done a few times, but nobody has |
| 138 | 137 |
sent us code.)</li> |
| ... | ... |
@@ -160,14 +159,14 @@ privoxy.</li> |
| 160 | 159 |
**hard** |
| 161 | 160 |
<ul> |
| 162 | 161 |
<li>Arranging membership management for independence.</li> |
| 163 |
-<ul> |
|
| 162 |
+<li><ul> |
|
| 164 | 163 |
<li>Sybil defenses without having a human bottleneck.</li> |
| 165 | 164 |
<li>How to gather random sample of nodes.</li> |
| 166 | 165 |
<li>How to handle nodelist recommendations.</li> |
| 167 | 166 |
<li>Consider incremental switches: a p2p tor with only 50 users has |
| 168 | 167 |
different anonymity properties than one with 10k users, and should be |
| 169 | 168 |
treated differently.</li> |
| 170 |
-</ul> |
|
| 169 |
+</ul></li> |
|
| 171 | 170 |
<li>Incentives to relay; incentives to exit.</li> |
| 172 | 171 |
<li>Allowing dissidents to relay through Tor clients.</li> |
| 173 | 172 |
<li>Experiment with mid-latency systems. How do they impact usability, |
| ... | ... |
@@ -180,7 +179,7 @@ treated differently.</li> |
| 180 | 179 |
<li>Attacking freenet-gnunet/timing-delay-randomness-arguments.</li> |
| 181 | 180 |
<li>Is exiting from the middle of the circuit always a bad idea?</li> |
| 182 | 181 |
<li>IPv6 support (For exit addresses)</li> |
| 183 |
-<ul> |
|
| 182 |
+<li><ul> |
|
| 184 | 183 |
<li>Spec issue: if a resolve returns an IP4 and an IP6 address, |
| 185 | 184 |
which to use?</li> |
| 186 | 185 |
<li>Add to exit policy code</li> |
| ... | ... |
@@ -189,7 +188,7 @@ treated differently.</li> |
| 189 | 188 |
a generalize address struct.</li> |
| 190 | 189 |
<li>Change relay cell types to accept new addresses.</li> |
| 191 | 190 |
<li>Add flag to serverdescs to tell whether IPv6 is supported.</li> |
| 192 |
-</ul> |
|
| 191 |
+</ul></li> |
|
| 193 | 192 |
<li>patch tsocks with our current patches + gethostbyname, getpeername, |
| 194 | 193 |
etc.</li> |
| 195 | 194 |
<li>make freecap (or whichever) do what we want.</li> |
| ... | ... |
@@ -235,10 +234,10 @@ interface for handling pseudonymous profiles in Tor. See this post and |
| 235 | 234 |
followup for details.</li> |
| 236 | 235 |
<li>Congestion control. Is our current design sufficient once we have |
| 237 | 236 |
heavy use? Need to measure and tweak, or maybe overhaul.</li> |
| 237 |
+</ul> |
|
| 238 | 238 |
|
| 239 | 239 |
Drop by the #tor IRC channel at irc.oftc.net or email tor-volunteer@freehaven.net if you want to help out! |
| 240 | 240 |
|
| 241 |
-</pre> |
|
| 242 | 241 |
</div><!-- #main --> |
| 243 | 242 |
</div> |
| 244 | 243 |
<div class="bottom" id="bottom"> |
| 245 | 244 |