Tor: Developers

Browse the Tor CVS repository: (which may not necessarily work or even compile)

• Regularly updated CVS sandbox
• ViewCVS
• Mailing list for cvs commits
• anonymous pserver access (password is guest):
  • Make a new empty directory and cd into it.
  • cvs -d :pserver:guest@cvs.seul.org:/home/or/cvsroot login
  • cvs -d :pserver:guest@cvs.seul.org:/home/or/cvsroot co tor
  • cd tor; ./autogen.sh; make; make install if you like.
  • (use "co -r tor-0_1_1_4_alpha tor" to fetch a particular version.)
  • (To check out the maintenance branch, use -r tor-0_1_0-patches)

Here's the current roadmap for the 0.1.1.x release:

• Reduce CPU load on servers.
• Continue decentralizing the directory.
  • Gather more permanent dirservers and put their keys into the code.
  • Need to solve what 'verified' means: it means the nickname is registered, but otherwise we treat servers the same.
  • A way for clients to partition the set of servers in a safe way: so they don't have to learn all of them but so they're not easily partitionable. Write it down, but probably not do it yet.
• Helper nodes (at least preliminary).
• Enclaves (at least preliminary).
• Launch the GUI contest.
• Something, anything, for sys tray on Windows.
• Get on some websites: indymedia.org. others?
• Research: scalability, keep thinking about end-to-end attacks.

The list of stuff the developers know they need to do.

The Java Anon Proxy (JAP) project has implemented the Tor client protocol in their client. More on that coming soon.