(text that it spits out immediately upon connect)


svn:r124

svn:r123

svn:r122

svn:r121

prkey is only fetched when it's needed
tor nodes who aren't dirservers now fetch directories and autoconnect
  to new nodes listed in the directory
default role is a non-dirserver node


svn:r120

tor can now interface directly with mozilla, as a socks 4 host.
but note that mozilla does the dns resolution itself, so you're leaking
anonymity.


svn:r119

svn:r118

svn:r117

svn:r116

svn:r115

svn:r114

if connecting to a dirserver fails, remove it from the router array


svn:r113

proxies now periodically pull down an hourly-updated directory,
and replace their router list with it if it parses correctly.


svn:r112

should be more reliable now (?)


svn:r111

revamped the router reading section

reference counting for crypto pk env's (so we can dup them)

we now read and write pem pk keys from string rather than from FILE*,
  in anticipation of fetching directories over a socket
  (so now on startup we slurp in the whole file, then parse it as a string)

fixed a bug in the proxy side, where you could get some circuits
  wedged if they showed up while the connection was being made


svn:r110

svn:r109

svn:r108

httpap is obsolete; we support privoxy directly now!

smtpap is obsolete; need to find a good socks4a-enabled smtp proxy/client

I dub thee 0.0.1.


svn:r107

svn:r106

svn:r105

svn:r104

see http://archives.seul.org/or/dev/Sep-2002/msg00018.html


svn:r103

svn:r102

(hey nick, does this break the os x build?)

you still need to add some stuff to the ./configure commandline...
anybody know a better solution?


svn:r101

(it seemed to work anyway, but...)


svn:r100

use 2**16+1 rather than 2**16 + 2**(-1)


svn:r99

svn:r98

svn:r97

svn:r96

svn:r95

the implementation is sort of a kludge..you're welcome to fix it up


svn:r94

the package is tor, the binary is or.

and i added our project plan to the todo file.


svn:r93

svn:r92

svn:r91

svn:r90

svn:r89

svn:r88

svn:r87

svn:r86

svn:r85