mirror repository of the tor core protocol in case of issues
Go to file
Nick Mathewson 474c60b743 Cleanup on time-relaqted constants. New conventions:
1) Surround all constants by (parens), whether we'll be using them
     in a denominator or not.
  2) Express all time periods as products (24*60*60), not as multiplied-out
     constants (86400).
  3) Comments like "(60*60) /* one hour */" are as pointless as comments
     like "c = a + b; /* set c to the sum of a and b */".  Remove them.
  4) All time periods should be #defined constants, not given inline.
  5) All time periods should have doxygen comments.
  6) All time periods, unless specified, are in seconds.  It's not necessary
     to say so.

To summarize, the old (lack of) style would allow:

  #define FOO_RETRY_INTERVAL 60*60 /* one hour (seconds) */
  next_try = now + 3600;

The new style is:

  /** How often do we reattempt foo? */
  #define FOO_RETRY_INTERVAL (60*60)

  next_try = now + RETRY_INTERVAL;


svn:r6142
2006-03-12 22:48:18 +00:00
contrib bump to 0.1.1.15-rc-cvs 2006-03-12 03:01:09 +00:00
debian Apparently passing --host to configure when not cross-compiling is evil now and 2006-03-11 19:05:06 +00:00
doc bump to 0.1.1.15-rc 2006-03-11 18:44:11 +00:00
src Cleanup on time-relaqted constants. New conventions: 2006-03-12 22:48:18 +00:00
Win32Build Adding unittests build for windows 2006-01-19 22:31:05 +00:00
.cvsignore ignore ancillary files build-stamp and patch-stamp 2006-02-26 23:05:18 +00:00
AUTHORS add jbash and weasel to the AUTHORS list 2004-02-17 05:05:34 +00:00
autogen.sh make our autogen.sh work on ksh as well as bash 2004-11-01 06:40:49 +00:00
ChangeLog bump to 0.1.1.15-rc 2006-03-11 18:44:11 +00:00
configure.in bump to 0.1.1.15-rc-cvs 2006-03-12 03:01:09 +00:00
Doxyfile Add Doxygen config file and make target, along with section in HACKING document 2004-05-07 17:03:52 +00:00
INSTALL another way for old-style bsd folks to maybe build tor if 2006-02-18 01:14:28 +00:00
LICENSE move to the copyright format that weasel likes 2006-01-03 12:37:03 +00:00
Makefile.am Fix up Makefile.am for the rpm target_cpu and target_os implementation. 2006-02-16 22:00:46 +00:00
README migrate to the new URL 2005-01-05 00:06:51 +00:00
tor.spec.in Removed doc/FAQ from document list 2006-02-21 04:45:07 +00:00

'tor' is an implementation of The Onion Routing system, as
described in a bit more detail at http://www.onion-router.net/. You
can read list archives, and subscribe to the mailing list, at
http://archives.seul.org/or/dev/.

Is your question in the FAQ? Should it be?

**************************************************************************
See the INSTALL file for a quickstart. That is all you will probably need.
**************************************************************************

**************************************************************************
You only need to look beyond this point if the quickstart in the INSTALL
doesn't work for you.
**************************************************************************

Do you want to run a tor server?

  See http://tor.eff.org/doc/tor-doc.html#server

Do you want to run a hidden service?

  See http://tor.eff.org/doc/tor-doc.html#hidden-service

Configuring tsocks:

  If you want to use Tor for protocols that can't use Privoxy, or
  with applications that are not socksified, then download tsocks
  (tsocks.sourceforge.net) and configure it to talk to localhost:9050
  as a socks4 server. My /etc/tsocks.conf simply has:
    server_port = 9050
    server = 127.0.0.1
  (I had to "cd /usr/lib; ln -s /lib/libtsocks.so" to get the tsocks
   library working after install, since my libpath didn't include /lib.)
  Then you can do "tsocks ssh arma@moria.mit.edu". But note that if
  ssh is suid root, you either need to do this as root, or cp a local
  version of ssh that isn't suid.

  (On Windows, you may want to look at the Hummingbird SOCKS client,
  or at SocksCap, instead.)