Update to 0.1.2.19:

Tor 0.1.2.19 fixes a huge memory leak on exit relays, makes the default
exit policy a little bit more conservative so it's safer to run an exit
relay on a home system, and fixes a variety of smaller issues.

https://www.torproject.org/download.html

Changes in version 0.1.2.19 - 2008-01-17
  o Security fixes:
    - Exit policies now reject connections that are addressed to a
      relay's public (external) IP address too, unless
      ExitPolicyRejectPrivate is turned off. We do this because too
      many relays are running nearby to services that trust them based
      on network address.

  o Major bugfixes:
    - When the clock jumps forward a lot, do not allow the bandwidth
      buckets to become negative. Fixes bug 544.
    - Fix a memory leak on exit relays; we were leaking a cached_resolve_t
      on every successful resolve. Reported by Mike Perry.
    - Purge old entries from the "rephist" database and the hidden
      service descriptor database even when DirPort is zero.
    - Stop thinking that 0.1.2.x directory servers can handle "begin_dir"
      requests. Should ease bugs 406 and 419 where 0.1.2.x relays are
      crashing or mis-answering these requests.
    - When we decide to send a 503 response to a request for servers, do
      not then also send the server descriptors: this defeats the whole
      purpose. Fixes bug 539.

  o Minor bugfixes:
    - Changing the ExitPolicyRejectPrivate setting should cause us to
      rebuild our server descriptor.
    - Fix handling of hex nicknames when answering controller requests for
      networkstatus by name, or when deciding whether to warn about
      unknown routers in a config option. (Patch from mwenge.)
    - Fix a couple of hard-to-trigger autoconf problems that could result
      in really weird results on platforms whose sys/types.h files define
      nonstandard integer types.
    - Don't try to create the datadir when running --verify-config or
      --hash-password. Resolves bug 540.
    - If we were having problems getting a particular descriptor from the
      directory caches, and then we learned about a new descriptor for
      that router, we weren't resetting our failure count. Reported
      by lodger.
    - Although we fixed bug 539 (where servers would send HTTP status 503
      responses _and_ send a body too), there are still servers out there
      that haven't upgraded. Therefore, make clients parse such bodies
      when they receive them.
    - Run correctly on systems where rlim_t is larger than unsigned long.
      This includes some 64-bit systems.
    - Run correctly on platforms (like some versions of OS X 10.5) where
      the real limit for number of open files is OPEN_FILES, not rlim_max
      from getrlimit(RLIMIT_NOFILES).
    - Avoid a spurious free on base64 failure.
    - Avoid segfaults on certain complex invocations of
      router_get_by_hexdigest().
    - Fix rare bug on REDIRECTSTREAM control command when called with no
      port set: it could erroneously report an error when none had
      happened.

3 files changed, 20 insertions, 19 deletions

diff --git a/net/tor/Makefile b/net/tor/Makefile
index ff1f6ba50bb..8006b16b9ee 100644
--- a/net/tor/Makefile
+++ b/net/tor/Makefile
@@ -1,8 +1,7 @@
-# $NetBSD: Makefile,v 1.50 2008/01/18 05:08:50 tnn Exp $
+# $NetBSD: Makefile,v 1.51 2008/01/20 20:11:09 jschauma Exp $
 #
 
-DISTNAME=		tor-0.1.2.18
-PKGREVISION=		1
+DISTNAME=		tor-0.1.2.19
 CATEGORIES=		net security
 MASTER_SITES=		http://www.torproject.org/dist/
 
diff --git a/net/tor/distinfo b/net/tor/distinfo
index 3df1e15a305..e7cf5eb3fd2 100644
--- a/net/tor/distinfo
+++ b/net/tor/distinfo
@@ -1,8 +1,8 @@
-$NetBSD: distinfo,v 1.26 2007/11/16 05:30:13 bjs Exp $
+$NetBSD: distinfo,v 1.27 2008/01/20 20:11:09 jschauma Exp $
 
-SHA1 (tor-0.1.2.18.tar.gz) = ff2160d30cfcb8cd7b735236dcb641b4bcb3fbeb
-RMD160 (tor-0.1.2.18.tar.gz) = e0ccd51288f7b41b5c4a21e49ce712066ce66a58
-Size (tor-0.1.2.18.tar.gz) = 1257011 bytes
+SHA1 (tor-0.1.2.19.tar.gz) = 5022dab0de2499e2c6638e1a2e9eee6c79fb707c
+RMD160 (tor-0.1.2.19.tar.gz) = 4f1b5474a4bbad2e3c82ef0fce2dd838907e48d5
+Size (tor-0.1.2.19.tar.gz) = 1264275 bytes
 SHA1 (patch-ac) = adcc070e4d522143c4d882bd13436cd2b71f289b
 SHA1 (patch-ad) = 72a68cbd00a5febdff82ba9268bdad2b47ea8159
-SHA1 (patch-ae) = 82977c38f18942de883a17d285ad9addd95e02f7
+SHA1 (patch-ae) = ad06a6adc8dbf9dce3945b3896d98cb62dc2b7f2
diff --git a/net/tor/patches/patch-ae b/net/tor/patches/patch-ae
index 5f08603149b..3c1eb9b3753 100644
--- a/net/tor/patches/patch-ae
+++ b/net/tor/patches/patch-ae
@@ -1,21 +1,23 @@
-$NetBSD: patch-ae,v 1.4 2007/09/11 15:53:58 obache Exp $
+$NetBSD: patch-ae,v 1.5 2008/01/20 20:11:09 jschauma Exp $
 
---- configure.orig	2007-08-30 21:01:38.000000000 +0000
-+++ configure
-@@ -5356,6 +5356,8 @@ done
+--- configure.orig	2008-01-20 12:04:44.000000000 -0800
++++ configure	2008-01-20 12:05:23.000000000 -0800
+@@ -5356,7 +5356,8 @@
  
  fi
  
+-
 +# these checks don't work, assume types are present
 +if false; then
  
- { echo "$as_me:$LINENO: checking for u_int64_t" >&5
- echo $ECHO_N "checking for u_int64_t... $ECHO_C" >&6; }
-@@ -5609,6 +5611,7 @@ _ACEOF
- 
+ for ac_header in sys/types.h
+ do
+@@ -5610,6 +5611,8 @@
+ 	ac_cv_type_u_int32_t=no
  fi
  
 +fi
- 
- { echo "$as_me:$LINENO: checking for libevent directory" >&5
- echo $ECHO_N "checking for libevent directory... $ECHO_C" >&6; }
++
+ rm -f core conftest.err conftest.$ac_objext conftest.$ac_ext
+ fi
+ { echo "$as_me:$LINENO: result: $ac_cv_type_u_int32_t" >&5