Remove the old-contribute.html page we never use anymore.
Andrew Lewman commited on 2006-04-13 23:09:23
Zeige 1 geänderte Dateien mit 0 Einfügungen und 209 Löschungen.
- old-contribute.html 5b06d96de..000000000
| ... | ... |
@@ -1,209 +0,0 @@ |
| 1 |
-<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" |
|
| 2 |
-"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> |
|
| 3 |
- |
|
| 4 |
-<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en"> |
|
| 5 |
-<head> |
|
| 6 |
- <title>Tor: Contribute</title> |
|
| 7 |
- <meta name="Author" content="Roger Dingledine" /> |
|
| 8 |
- <meta http-equiv="content-type" content="text/html; charset=ISO-8859-1" /> |
|
| 9 |
- <link rel="stylesheet" type="text/css" href="stylesheet.css" /> |
|
| 10 |
- <link rel="shortcut icon" type="image/x-icon" href="/favicon.ico" /> |
|
| 11 |
-</head> |
|
| 12 |
-<body> |
|
| 13 |
- |
|
| 14 |
-<!-- TITLE BAR & NAVIGATION --> |
|
| 15 |
- |
|
| 16 |
-<table class="banner" border="0" cellpadding="0" cellspacing="0"> |
|
| 17 |
- <tr> |
|
| 18 |
- <td class="banner-left"></td> |
|
| 19 |
- <td class="banner-middle"> |
|
| 20 |
- <a href="index.html">Home</a> |
|
| 21 |
- | <a href="overview.html">Overview</a> |
|
| 22 |
- | <a href="download.html">Download</a> |
|
| 23 |
- | <a href="documentation.html">Docs</a> |
|
| 24 |
- | <a href="support.html">Support</a> |
|
| 25 |
- | <a href="faq.html">FAQs</a> |
|
| 26 |
- | <a class="current">Contribute</a> |
|
| 27 |
- | <a href="developers.html">Developers</a> |
|
| 28 |
- | <a href="research.html">Research</a> |
|
| 29 |
- | <a href="people.html">People</a> |
|
| 30 |
- </td> |
|
| 31 |
- <td class="banner-right"></td> |
|
| 32 |
- </tr> |
|
| 33 |
-</table> |
|
| 34 |
- |
|
| 35 |
-<!-- END TITLE BAR & NAVIGATION --> |
|
| 36 |
- |
|
| 37 |
-<div class="center"> |
|
| 38 |
- |
|
| 39 |
-<div class="main-column"> |
|
| 40 |
- |
|
| 41 |
-<!-- PUT CONTENT AFTER THIS TAG --> |
|
| 42 |
- |
|
| 43 |
-<h2>Tor: Contribute</h2> |
|
| 44 |
-<hr /> |
|
| 45 |
- |
|
| 46 |
-<p>Ongoing needs:</p> |
|
| 47 |
-<ul> |
|
| 48 |
-<li>We need users like you to try Tor out, and let the Tor developers |
|
| 49 |
-know about bugs you find or features you don't find.</li> |
|
| 50 |
-<li>Please consider <a |
|
| 51 |
-href="/cvs/tor/doc/tor-doc.html#server">running a |
|
| 52 |
-server</a> to help the Tor network grow.</li> |
|
| 53 |
-<li>We especially need people with Windows programming skills |
|
| 54 |
-to run an exit server on Windows, to help us debug.</li> |
|
| 55 |
-<li>Run a <a href="/cvs/tor/doc/tor-doc.html#hidden-service">Tor hidden |
|
| 56 |
-service</a> and put interesting content on it.</li> |
|
| 57 |
-<li>Tell your friends! Get them to run servers. Get them to run hidden |
|
| 58 |
-services. Get them to tell <i>their</i> friends.</li> |
|
| 59 |
-<li>What else needs to be documented? What is mis-documented?</li> |
|
| 60 |
-<li>Consider joining the <a href="http://secure.eff.org/tor">Electronic |
|
| 61 |
-Frontier Foundation</a>. More EFF donations means more freedom in the world, |
|
| 62 |
-including more Tor development.</li> |
|
| 63 |
-</ul> |
|
| 64 |
- |
|
| 65 |
-<p>We also have many project-lets: short-term or self-contained tasks |
|
| 66 |
-that would be really helpful for somebody to tackle so we can keep |
|
| 67 |
-focusing on Tor.</p> |
|
| 68 |
- |
|
| 69 |
-<p>Writing project-lets:</p> |
|
| 70 |
-<ul> |
|
| 71 |
-<li>Does somebody want to help maintain this website, or help with |
|
| 72 |
-documentation, or help with managing our TODO and handling bug reports?</li> |
|
| 73 |
-<li>We may have too <i>much</i> documentation. It's spread out too far |
|
| 74 |
-and duplicates itself in places. Can you help us consolidate?</li> |
|
| 75 |
-<li>Please help translate the web page and documentation |
|
| 76 |
-into other languages. See the <a href="translation.html">translation guidelines</a> |
|
| 77 |
-if you want to help out. (Examples: |
|
| 78 |
-<a href="http://membres.lycos.fr/geolemalin/anonymat_garantit.htm">French</a> |
|
| 79 |
-, <a href="http://tor.freesuperhost.com/">Persian</a> and |
|
| 80 |
-<a href="http://www.gamevn.com/forum/showthread.php?t=103346">Vietnamese</a>.)</li> |
|
| 81 |
-<li>Please fix up <a |
|
| 82 |
-href="http://wiki.noreply.org/wiki/TheOnionRouter/TorFAQ">the FAQ Wiki</a>, |
|
| 83 |
-and if you know the answer to a question in the "unanswered FAQs" list, |
|
| 84 |
-please answer it.</li> |
|
| 85 |
-</ul> |
|
| 86 |
- |
|
| 87 |
-<p>Packaging project-lets:</p> |
|
| 88 |
-<ul> |
|
| 89 |
-<li>We're always looking for better Windows installers. Specifically, |
|
| 90 |
-it would be great if somebody were to extend our NSIS-based windows |
|
| 91 |
-installer to include FreeCap and Privoxy.</li> |
|
| 92 |
-<li>Our OS X installer can't be uninstalled. Are there non-sucky OS X |
|
| 93 |
-packagers that have uninstall capabilities? This is becoming an |
|
| 94 |
-increasing bother.</li> |
|
| 95 |
-</ul> |
|
| 96 |
- |
|
| 97 |
-<p>Organizational and application testing project-lets:</p> |
|
| 98 |
-<ul> |
|
| 99 |
-<li>We've got a list of potentially useful programs you might |
|
| 100 |
-run with Tor <a href="users.html">here</a>. We also have the <a |
|
| 101 |
-href="http://wiki.noreply.org/wiki/TheOnionRouter/TorifyHOWTO">Torify |
|
| 102 |
-howto</a>. Can somebody try them out, simplify the explanations, expand |
|
| 103 |
-them where they need it, document them better, and make them all-around |
|
| 104 |
-more useful?</li> |
|
| 105 |
-</ul> |
|
| 106 |
- |
|
| 107 |
-<p>Programmer and developer project-lets:</p> |
|
| 108 |
-<ul> |
|
| 109 |
-<li>We need somebody to code up a GUI or other |
|
| 110 |
-controller program, to do configuration, etc. See our <a |
|
| 111 |
-href="/cvs/tor/doc/control-spec.txt">control specification</a> for details, |
|
| 112 |
-and the <a href="/cvs/tor/contrib/TorControl.py">rudimentary demonstration |
|
| 113 |
-Python control script</a>. No, we don't know what the interface should look |
|
| 114 |
-like. You can use any license you want, but we'd recommend 3-clause BSD or |
|
| 115 |
-maybe GPL; and we can only help out if your license conforms to the |
|
| 116 |
-<a href="http://www.debian.org/social_contract.html#guidelines">DFSG</a>.</li> |
|
| 117 |
-<li>Periodically people running servers tells us they want to have one |
|
| 118 |
-BandwidthRate during some part of the day, and a different BandwidthRate |
|
| 119 |
-at other parts of the day. Rather than coding this inside Tor, we should |
|
| 120 |
-have a little script that speaks via the Tor Controller Interface, and does |
|
| 121 |
-a setconf to change the bandwidth rate. Perhaps it would run out of cron, |
|
| 122 |
-or perhaps it would sleep until appropriate times and then do its tweak |
|
| 123 |
-(that's probably more portable). Can somebody write one for us and we'll |
|
| 124 |
-put it inside <a href="/cvs/tor/contrib/">tor/contrib/</a>?</li> |
|
| 125 |
-<li>Does somebody want to do up a patch so we can be an NT service? Or |
|
| 126 |
-so we can go in the system tray?</li> |
|
| 127 |
-<li>A good (portable, fast, clean, BSD-free) asynchronous DNS library |
|
| 128 |
-would be really handy, so we don't have to keep forking DNS worker |
|
| 129 |
-threads to do gethostbyname.</li> |
|
| 130 |
-<li>Can somebody take a look at Martin's <a |
|
| 131 |
-href="http://wiki.noreply.org/wiki/TheOnionRouter/SquidProxy">Squid |
|
| 132 |
-and Tor</a> page, and update it to reflect Tor's |
|
| 133 |
-<a href="http://tor.eff.org/tor-manual.html">RedirectExit</a> config |
|
| 134 |
-option?</li> |
|
| 135 |
-<li>See the <a href="/cvs/tor/doc/TODO">TODO</a> and |
|
| 136 |
-<a href="/cvs/tor/doc/HACKING">HACKING</a> files in the Tor distribution |
|
| 137 |
-for more ideas.</li> |
|
| 138 |
-</ul> |
|
| 139 |
- |
|
| 140 |
-<p>Security project-lets: We need people to attack the implementation |
|
| 141 |
-and clean it up, and also to attack the design and experiment with |
|
| 142 |
-defenses.</p> |
|
| 143 |
-<ul> |
|
| 144 |
-<li>We need somebody to <a |
|
| 145 |
-href="http://en.wikipedia.org/wiki/Fuzz_testing">fuzz</a> Tor. Are there |
|
| 146 |
-good libraries out there for what we want? What are the first steps? Win |
|
| 147 |
-fame by getting credit when we put out a new release because of you!</li> |
|
| 148 |
-<li>Website volume fingerprinting attacks (<a |
|
| 149 |
-href="http://freehaven.net/anonbib/#back01">Back et al</a>, <a |
|
| 150 |
-href="http://freehaven.net/anonbib/#hintz02">Hintz</a>). |
|
| 151 |
-Defenses include a large cell size, <a |
|
| 152 |
-href="http://freehaven.net/anonbib/#timing-fc2004">defensive dropping</a>, |
|
| 153 |
-etc. How well does each approach work?</li> |
|
| 154 |
-<li>The end-to-end traffic confirmation attack. We need to study |
|
| 155 |
-long-range dummies more, along with traffic shaping. How much traffic |
|
| 156 |
-of what sort of distribution is needed before the adversary is confident |
|
| 157 |
-he has won?</li> |
|
| 158 |
-<li>It's not that hard to DoS Tor servers or dirservers. Are puzzles |
|
| 159 |
-the right answer? What other practical approaches are there?</li> |
|
| 160 |
-<li>What sensitive info squeaks by privoxy? Are other html scrubbers |
|
| 161 |
-better?</li> |
|
| 162 |
-</ul> |
|
| 163 |
- |
|
| 164 |
-<p>Designer project-lets:</p> |
|
| 165 |
-<ul> |
|
| 166 |
-<li>Server CPU load is high because clients keep asking to make new |
|
| 167 |
-circuits, which uses public key crypto. Possible defenses include: |
|
| 168 |
-using helper nodes (fixed entry nodes); rate limiting the number of |
|
| 169 |
-create cells handled per second; having clients retry failed extensions |
|
| 170 |
-a few times; implementing ssl sessions; and using hardware crypto when |
|
| 171 |
-available.</li> |
|
| 172 |
-<li>We fear we might not work very well when servers have asymmetric |
|
| 173 |
-bandwidth. Because Tor has separate TCP connections between each hop, |
|
| 174 |
-if the incoming bytes are arriving just fine and the outgoing bytes |
|
| 175 |
-are all getting dropped on the floor, the TCP push-back mechanisms |
|
| 176 |
-don't really transmit this information back to the incoming streams. |
|
| 177 |
-Perhaps Tor should detect when it's dropping a lot of outgoing packets, |
|
| 178 |
-and rate-limit incoming streams to regulate this itself? We need somebody |
|
| 179 |
-who's good with networks to simulate this and help design solutions.</li> |
|
| 180 |
-<li>Right now the hidden service descriptors are being stored on the |
|
| 181 |
-dirservers, but any reliable distributed storage system would do (for |
|
| 182 |
-example, a DHT that allows authenticated updates). Can somebody figure |
|
| 183 |
-out our best options and decide if they're good enough?</li> |
|
| 184 |
-<li>How hard is it to patch bind or a DNS proxy to redirect requests |
|
| 185 |
-to Tor via our tor-resolve socks extension? What about to convert UDP |
|
| 186 |
-DNS requests to TCP requests and send them through Tor?</li> |
|
| 187 |
-<li>Tor provides anonymous connections, but if you want to keep multiple |
|
| 188 |
-pseudonyms in practice (say, in case you frequently go to two websites |
|
| 189 |
-and if anybody knew about both of them they would conclude it's you), |
|
| 190 |
-we don't support that well yet. We should find a good approach and |
|
| 191 |
-interface for handling pseudonymous profiles in Tor. See <a |
|
| 192 |
-href="http://archives.seul.org/or/talk/Dec-2004/msg00086.html">this |
|
| 193 |
-post</a> and <a |
|
| 194 |
-href="http://archives.seul.org/or/talk/Jan-2005/msg00007.html">followup</a> |
|
| 195 |
-for details.</li> |
|
| 196 |
-</ul> |
|
| 197 |
- |
|
| 198 |
-<p>Drop by <a href="irc://irc.oftc.net/tor">the #tor IRC channel at irc.oftc.net</a> or |
|
| 199 |
-<a href="mailto:tor-volunteer@freehaven.net">email |
|
| 200 |
-tor-volunteer@freehaven.net</a> if you want to help out!</p> |
|
| 201 |
- |
|
| 202 |
-</div><!-- #main --> |
|
| 203 |
-</div> |
|
| 204 |
- <div class="bottom" id="bottom"> |
|
| 205 |
- <i><a href="mailto:tor-webmaster@freehaven.net" class="smalllink">Webmaster</a></i> - |
|
| 206 |
- $Id$ |
|
| 207 |
- </div> |
|
| 208 |
-</body> |
|
| 209 |
-</html> |
|
| 210 | 0 |