Running Tor

Getting up to speed on Tor's past, present, and future

  1. First, read the overview page to get a basic idea of how Tor works, what it's for, and who uses it.
  2. Install the Tor bundle and try it out. Make sure you've got Firefox installed first, and be sure to read the list of warnings about ways you can screw up your anonymity.
  3. Our FAQ covers all sorts of topics, including questions about setting up a client or relay, concerns about anonymity attacks, why we didn't build Tor in other ways, etc. There's a separate Abuse FAQ to answer common questions from or for relay operators. The Tor Legal FAQ is written by EFF lawyers, and aims to give you an overview of some of the legal issues that arise from the Tor project in the US.
  4. The manual lists all the possible entries you can put in your torrc file. We also provide a manual for the development version of Tor.
  5. If you have questions, we have an IRC channel (for users, relay operators, and developers) at #tor on irc.oftc.net. If you have a bug, especially a crash bug, read how to report a Tor bug first and then tell us as much information about it as you can in our bugtracker. (If your bug is with Polipo, your browser, or some other application, please don't put it in our bugtracker.) The or-talk mailing list can also be useful.
  6. Tor has a blog now. We try to keep it updated every week or two with the latest news.
  7. Download and watch Roger's overview talk from What The Hack (video, slides, abstract). This talk was given in July 2005, back when we were funded by EFF and back when the network was quite small, but it still provides good background on how Tor works and what it's for.
  8. Look through our Design Documents. Notice that we have RFC-style specs to tell you exactly how Tor is built.
  9. There's a skeletal list of items we'd like to tackle in the future. Alas, many of those items need to be fleshed out more before they'll make sense to people who aren't Tor developers, but you can still get a general sense of what issues need to be resolved next.
  10. Download and watch Nick's "Technical changes since 2004" talk from Defcon in July 2007 (video, slides), Roger's "blocking-resistance and circumvention" talk from 23C3 in December 2006 (video, slides, abstract, design paper), and Roger's "Current events in 2007" talk from 24C3 in December 2007 (video, slides, abstract). We also have the What The Hack tutorial on hidden services (video, slides).
  11. See Mike's "Securing the Tor network" talk from Defcon in July 2007 (video, slides). It describes common ways to attack networks like Tor and how we try to defend against them, and it introduces the Torflow script collection.
  12. Learn about the Tor proposal process for changing our design, and look over the existing proposals.
  13. Our developer TODO file starts with a timeline for external promises — things our sponsors have paid to see done. It also lists many other tasks and topics we'd like to tackle next.
  14. Once you're up to speed, things will continue to change surprisingly fast. The or-dev mailing list is where the complex discussion happens, and the #tor IRC channel is where the less complex discussion happens.

Mailing List Information

Design Documents

Neat Links

For Developers

Browse the Tor source repository:

"Tor" and the "Onion Logo" are registered trademarks of The Tor Project, Inc.
Content on this site is licensed under a Creative Commons Attribution 3.0 United States License, unless otherwise noted.

This page is also available in the following languages: Deutsch, español, suomi, français, Italiano, 日本語 (Nihongo), Nederlands, norsk, polski, Português, Русский (Russkij), svenska, 中文(简) (Simplified Chinese).
How to set the default document language.

Contact Us - Last modified: Sun Apr 25 15:20:17 2010 - Last compiled: Wed Apr 28 07:57:22 2010