svn:r1304

svn:r1296

svn:r1289

world's shortest release


svn:r1281

svn:r1248

svn:r1237

svn:r1218

build properly.  Works fine on redhat 9.  YMMV.)


svn:r1199

svn:r1183

svn:r1144

svn:r1125

svn:r1107

svn:r1090

svn:r1080

svn:r1069

svn:r1031

svn:r978

svn:r975

svn:r967

the (incompatible) pre16 network


svn:r945

svn:r933

svn:r884

enforce -g on compile always. we're an alpha release after all.


svn:r878

svn:r861

svn:r850

svn:r665

setuid and setgid respectively, and die if it can't.

(If the User option is set, tor will setgid to the user's gid as well.)

This happens after the pidfile is created, so that in cases where tor
needs to be root to work with the pidfile, it will at least be able to
create it, although it won't be able to delete it.  That sucks, but
it's somewhat better than not being able to create the pidfile in the
first place.


svn:r652

svn:r631

svn:r598

  correctly based on how configure was run

- cause tor to guess the location of torrc more intelligently

- cause cause src/config/torrc and src/conf/sample-server-torrc to be
  generated with contents that are correct for the way configure was
  run

- cause "make install" to put torrc, sample-server-torrc, and
  dirservers somewhere intelligent


svn:r587

(mainly doc and log changes)


svn:r579

svn:r564

svn:r551

our log() conflicts with log(3)
distribute only the correct files from doc/ and src/config/
sometimes laptops go back in time. i guess that's ok for now.
and bump the version number because we're live.


svn:r544

svn:r520

svn:r500

svn:r480

nick: is this the right way to do the autoconf stuff? what happens when
/usr/kerberos/include/ doesn't exist?
an alternate way is to add `pkg-config --cflags openssl` to CFLAGS, but
it seems that command only works on rh9. yay portability issues.


svn:r453

Add initial interfaces and code for TLS support.  Interfaces are right; code needs work and testing.


svn:r424

svn:r389