Roger Dingledine commited on 2005-07-01 00:56:08
Zeige 1 geänderte Dateien mit 17 Einfügungen und 18 Löschungen.
... | ... |
@@ -65,26 +65,26 @@ |
65 | 65 |
<li>Change server descriptors to declare log level.</li> |
66 | 66 |
<li>Add in support for clients to avoid servers that are too loggy based upon user configuration of acceptable log level.</li> |
67 | 67 |
<li>Separate node discovery from routing to allow neat extensions. [Goodell?]</li> |
68 |
-<li><ul> |
|
68 |
+<ul> |
|
69 | 69 |
<li>Add SetServerStatus control event to adjust verified/running status of nodes.</li> |
70 | 70 |
<li>Add NoDownload config option to prevent regular directory downloads from happening.</li> |
71 |
-</ul></li> |
|
71 |
+</ul> |
|
72 | 72 |
<li>Choosing exit node by meta-data, e.g. country.</li> |
73 | 73 |
<li>Use cpuworker for more heavy lifting.</li> |
74 |
-<li><ul> |
|
74 |
+<ul> |
|
75 | 75 |
<li>Signing (and verifying) hidserv descriptors</li> |
76 | 76 |
<li>Signing (and verifying) intro/rend requests</li> |
77 | 77 |
<li>Signing (and verifying) router descriptors</li> |
78 | 78 |
<li>Signing (and verifying) directories</li> |
79 | 79 |
<li>Doing TLS handshake (this is very hard to separate out, though)</li> |
80 |
-</ul></li> |
|
80 |
+</ul> |
|
81 | 81 |
<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> |
82 | 82 |
<li>Add alternative versions of crypto.c and tortls.c to use libnss or libgcrypt+gnutls.</li> |
83 | 83 |
<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> |
84 | 84 |
<li>Extend our NSIS-based windows installer to include FreeCap and/or Privoxy.</li> |
85 | 85 |
<li>Develop a way to handle OS X installation and uninstallation.</li> |
86 | 86 |
<li>Develop a GUI or other controller program, to do configuration, etc. See our <a href="cvs/tor/doc/control-spec.txt">control specification</a> for details, and the rudimentary demonstration <a href="cvs/tor/contrib/TorControl.py">Python control script</a>. </li> |
87 |
-<li><ul> |
|
87 |
+<ul> |
|
88 | 88 |
<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 <a href="http://www.debian.org/social_contract.html#guidelines">DFSG</a>.</li> |
89 | 89 |
<li>Periodically people running servers tells us they want to have one |
90 | 90 |
BandwidthRate during some part of the day, and a different |
... | ... |
@@ -95,7 +95,7 @@ |
95 | 95 |
until appropriate times and then do its tweak (that's probably more |
96 | 96 |
portable). Can somebody write one for us and we'll put it inside |
97 | 97 |
<a href="cvs/tor/contrib/">tor/contrib/</a>?</li> |
98 |
-</ul></li> |
|
98 |
+</ul> |
|
99 | 99 |
<li>Develop a way to become a Windows NT service. </li> |
100 | 100 |
<li>Develop a systray app for Tor under MS Windows (all versions). </li> |
101 | 101 |
<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> |
... | ... |
@@ -104,40 +104,39 @@ |
104 | 104 |
<h2>Documentation Challenges</h2> |
105 | 105 |
<ul> |
106 | 106 |
<li>Write server instructions for OSX and Windows operators.</li> |
107 |
-<li>Improve and clarify the wiki entry on port forwarding. url?</li> |
|
107 |
+<li>Improve and clarify the wiki entry on <a href="http://wiki.noreply.org/noreply/TheOnionRouter/TorFAQ#ServerForFirewalledClients">port forwarding</a>.</li> |
|
108 | 108 |
<li>Document how to do exit node caching: tie into squid or other caching web proxy.</li> |
109 | 109 |
<li>Help maintain this website; code, content, css, overall layout,</li> |
110 | 110 |
<li>Help with documentation </li> |
111 | 111 |
<li>Help consolidate documentation. We may have too much documentation. It's spread out too far and duplicates itself in places. </li> |
112 | 112 |
<li>Help translate the web page and documentation into other languages. See the <a href="translation.html">translation guidelines</a> if you want to help out. (Examples: <a href="http://membres.lycos.fr/geolemalin/anonymat_garantit.htm">French</a> , <a href="http://tor.freesuperhost.com/">Persian</a> and <a href="http://www.gamevn.com/forum/showthread.php?t=103346">Vietnamese</a>.)</li> |
113 |
+<li>If you know a question that should go on <a |
|
114 |
+href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ">the FAQ Wiki</a>, please |
|
115 |
+add it and answer it.</li> |
|
113 | 116 |
<li>If you know the answer to a <a href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ">Wiki question</a> in the "unanswered FAQs" list, please answer it. </li> |
114 | 117 |
<li>Take a look at <a |
115 | 118 |
href="http://wiki.noreply.org/wiki/TheOnionRouter/SquidProxy">Martin's |
116 | 119 |
Squid and Tor page</a>, and update it to reflect Tor's <a |
117 | 120 |
href="http://tor.eff.org/tor-manual.html">RedirectExit</a> config option. </li> |
118 | 121 |
<li>Help translate the web page and documentation into other languages. See the translation guidelines if you want to help out. (Examples: French , Persian and Vietnamese.)</li> |
119 |
-<li>If you know a question that should go on <a |
|
120 |
-href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ">the FAQ Wiki</a>, please |
|
121 |
-add it and answer it.</li> |
|
122 | 122 |
<li>Update website to include the country flags for each language into which the website has been translated.</li> |
123 |
-<li>Replace the old tor-manual.html and replace it with the new tor stable manual.</li> |
|
124 | 123 |
</ul> |
125 | 124 |
|
126 | 125 |
<h2>Testing Challenges</h2> |
127 | 126 |
<ul> |
128 | 127 |
<li>Test out why some of our tor servers have dns resolvers that resolve |
129 | 128 |
unknown addresses to 127.0.0.1.</li> |
130 |
-<li><ul> |
|
129 |
+<ul> |
|
131 | 130 |
<li>Identify the servers that experience this issue. </li> |
132 | 131 |
<li>Identify how to cause and repair the issue in BIND, DJBDNS, or |
133 | 132 |
whatever daemon the misconfigured servers use.</li> |
134 |
-</ul></li> |
|
133 |
+</ul> |
|
135 | 134 |
<li>Figure out how to setup web proxy gateways to let normal people |
136 | 135 |
browse hidden services. (This has been done a few times, but nobody has |
137 | 136 |
sent us code.)</li> |
138 | 137 |
<li>Investigate privoxy vs. freecap for win32 clients</li> |
139 | 138 |
<li>Evaluate, create, and <a href="http://wiki.noreply.org/wiki/TheOnionRouter/TorifyHOWTO">document a list of programs</a> that work with Tor. </li> |
140 |
-<li>Perform a security analysis of Tor with <a href="http://en.wikipedia.org/wiki/Fuzz_testing">fuzz</a>"fuzz"</a>. Determine if there good libraries out there for what we want. Win fame by getting credit when we put out a new release because of you!</li> |
|
139 |
+<li>Perform a security analysis of Tor with <a href="http://en.wikipedia.org/wiki/Fuzz_testing">"fuzz"</a>". Determine if there good libraries out there for what we want. Win fame by getting credit when we put out a new release because of you!</li> |
|
141 | 140 |
<li>Website volume fingerprinting attacks (<a href="http://freehaven.net/anonbib/#back01">Back et al</a>, <a href="http://freehaven.net/anonbib/#hintz02">Hintz</a>). Defenses include a large cell size, <a href="http://freehaven.net/anonbib/#timing-fc2004">defensive dropping</a>, etc. How well does each approach work?</li> |
142 | 141 |
<li>The end-to-end traffic confirmation attack. We need to study |
143 | 142 |
long-range dummies more, along with traffic shaping. How much traffic of |
... | ... |
@@ -151,14 +150,14 @@ privoxy.</li> |
151 | 150 |
<h2>Research Challenges</h2> |
152 | 151 |
<ul> |
153 | 152 |
<li>Arranging membership management for independence.</li> |
154 |
-<li><ul> |
|
153 |
+<ul> |
|
155 | 154 |
<li>Sybil defenses without having a human bottleneck.</li> |
156 | 155 |
<li>How to gather random sample of nodes.</li> |
157 | 156 |
<li>How to handle nodelist recommendations.</li> |
158 | 157 |
<li>Consider incremental switches: a p2p tor with only 50 users has |
159 | 158 |
different anonymity properties than one with 10k users, and should be |
160 | 159 |
treated differently.</li> |
161 |
-</ul></li> |
|
160 |
+</ul> |
|
162 | 161 |
<li>Incentives to relay; incentives to exit.</li> |
163 | 162 |
<li>Allowing dissidents to relay through Tor clients.</li> |
164 | 163 |
<li>Experiment with mid-latency systems. How do they impact usability, |
... | ... |
@@ -171,7 +170,7 @@ treated differently.</li> |
171 | 170 |
<li>Attacking freenet-gnunet/timing-delay-randomness-arguments.</li> |
172 | 171 |
<li>Is exiting from the middle of the circuit always a bad idea?</li> |
173 | 172 |
<li>IPv6 support (For exit addresses)</li> |
174 |
-<li><ul> |
|
173 |
+<ul> |
|
175 | 174 |
<li>Spec issue: if a resolve returns an IP4 and an IP6 address, |
176 | 175 |
which to use?</li> |
177 | 176 |
<li>Add to exit policy code</li> |
... | ... |
@@ -180,7 +179,7 @@ treated differently.</li> |
180 | 179 |
a generalize address struct.</li> |
181 | 180 |
<li>Change relay cell types to accept new addresses.</li> |
182 | 181 |
<li>Add flag to serverdescs to tell whether IPv6 is supported.</li> |
183 |
-</ul></li> |
|
182 |
+</ul> |
|
184 | 183 |
<li>patch tsocks with our current patches + gethostbyname, getpeername, |
185 | 184 |
etc.</li> |
186 | 185 |
<li>make freecap (or whichever) do what we want.</li> |
187 | 186 |